Viewing 15 posts - 51,016 through 51,030 (of 59,102 total)
mailsar (4/21/2008)
GSquared,U really made me think. Yep i do agree with you on storing the entire record in XML is a good idea.
Think a bit more... if...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2008 at 7:00 pm
Then, you need to trace the source to the root cause.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2008 at 6:49 pm
GSquared (4/22/2008)
I would definitely avoid that "speed at all cost" methodology.
Heh... then why have you posted so much on this thread about speed? 😉 The real answer is that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2008 at 6:41 pm
Yes, you can include the last ELSE with a function. I wanted you to post the CREATE TABLE statement so I could build something to it to show you...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2008 at 6:41 am
DB2 date/times are much different than SQL Server (if memory serves me)... I believe they're based on something like the number of seconds since midnight 1970-01-01. You will need...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2008 at 6:55 pm
It's really a PITA when folks double post... have a little forum courtesy, please.
http://www.sqlservercentral.com/Forums/Topic487503-338-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2008 at 6:41 pm
mailsar (4/21/2008)
Yep i do agree with you on storing the entire record in XML is a good idea
Gooed! Hope you don't mind your audit table being 16 times the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2008 at 6:39 pm
Sure... post the CREATE TABLE command where you want the calculated column.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2008 at 6:18 pm
Perfect... thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2008 at 6:15 pm
Calculated column would take care of it nicely...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2008 at 6:06 pm
...if you do it right, one follows the other.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2008 at 6:03 pm
Heh... I understand that COALESCE is more portable than ISNULL... that's one of the fortunate functions... I just wanted to make sure that someone didn't actually believe they could write...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2008 at 5:53 pm
What's in the TEXT column?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2008 at 5:49 am
Heh... no... I always try to use the method with the best performance instead of documenting why performance can suffer... it's part of my 3 rules of a DBA.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2008 at 5:43 am
Andrew Shaw (4/21/2008)
I need this value writing up...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2008 at 5:39 am
Viewing 15 posts - 51,016 through 51,030 (of 59,102 total)