|
One could get the opinion that you don't like triggers spit
"The ones who care enough to do it right care too much to compromise."
Matthew Faithfull
|
|
|
|
|
One of my earliest sql jobs was to track down a bug, it was in a trigger spit and it took me ages to find the bloody thing, that was over 25 years ago and I have not forgiven them their sins!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I don't like them either, I'm considering triggers and distinct as a sign that there is something wrong in the design and query respectively. Cannot always be without them, but I try hard.
"The ones who care enough to do it right care too much to compromise."
Matthew Faithfull
|
|
|
|
|
Friends,,
Atlast what is the exact solution? Everybody posting ur concerns, but I want answer
|
|
|
|
|
Create a stored procedure.
Pass the update information into the stored procedure via parameters then update the relevant tables via the stored procedure.
I would tend to agree with Mycroft spit that triggers can hide things from you when you are trying to debug a problem later on.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
One could get the impression that you don't like Mycroft.
"The ones who care enough to do it right care too much to compromise."
Matthew Faithfull
|
|
|
|
|
Hi all,
DECLARE @DocsList nvarchar(max);
SELECT @DocsList = STUFF(
(SELECT ', ' + quotename(Particulars)
FROM [101_SalaryParticulars]
GROUP BY Particulars
ORDER BY Particulars
FOR XML PATH(''))
, 1, 2, '');
I wants to change the above query dynamically. My table name will vary like '[102_SalaryParticulars]','[103_SalaryParticulars]' Etc.,
Software Engineer
AcSys IT Software Solution
|
|
|
|
|
kasimmohamed wrote: '[102_SalaryParticulars]','[103_SalaryParticulars]'
Then you deserve all the horror you are going to get with such a terrible design. You should have 1 table with different key for 102 and 103!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: You should have 1 table with different key for 102 and 103
I agree with your point, but it is not uncommon to see such design in OLAP databases.
|
|
|
|
|
It's also common to vary the query from code, and not try and do this in the database-server.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
And if he is mucking around with OLAP databases and can't work out how to concatenate a string then they have bigger problems!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Hi Everyone,
I'm writing a report and there is a requirement to have repeating fields appearing inline. So rather than a table displaying say, user names, the final report should look like this:
Static text Static text Static text:
Person Name 1, Person Name 2, Person Name 3
I've had a long look, I've tried changing the properties of the table, I've tried playing with expressions.
Does anyone have any ideas?
Many thanks,
Larry
|
|
|
|
|
|
Thanks I'll have a look.
I actually got round the problem by writing a stored procedure and putting my output into a string.
|
|
|
|
|
Friends,
Iam using Persisted Primary key constraint for one column in a table.
while creating another table using of the above table column as reference constraint getting the following error.
"There are no primary or candidate keys in the referenced table that match the referencing column list in the foreign key."
How could I resolve this issue?
|
|
|
|
|
What database are you using, candidate key does not sound familiar.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
|
H JJ wrote: How could I resolve this issue?
Have a look here[^].
A persisted column, that'd be a computed/calculated field? Are you sure that's a good idea to use as a primary key?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Eddy Vluggen wrote: A persisted column, that'd be a computed/calculated field? Are you sure that's a
good idea to use as a primary key?
It shouldn't even be allowed in my opinion
"The ones who care enough to do it right care too much to compromise."
Matthew Faithfull
|
|
|
|
|
Hi guys,
I want to plot a graph that shows weekly data for total year of total number of issues and solved issues.
So yearly will have 52 weeks. My financial year will start every year October to next year September end.
EX my Financial year 2012-13 Start date will be 01/10/2012 end date will be 30/09/2013.
Any help will be appreciated.
Thanks and regards
Vishwa
|
|
|
|
|
Look into DATEPART that will give you the week number of the date within the year. Count the issues and group by the week datepart
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Sum up want ever you want and make group by with datepart.
|
|
|
|
|
Thank you guys i solved the issue, thank you for your support
|
|
|
|
|
|
SELECT DATEPART(YEAR,trans_date) AS 'Year',DATEPART(wk,trans_date) AS 'Week #',MIN(DATEADD(wk, DATEDIFF(wk,0,trans_date), 0)) AS 'Week date', SUM(COALESCE(debit,0)) AS 'Debits', SUM(COALESCE(credit,0)) AS 'Credits' FROM trans GROUP BY DATEPART(YEAR,trans_date),DATEPART(wk,trans_date)ORDER BY 1,2;
|
|
|
|