Viewing 15 posts - 57,721 through 57,735 (of 59,067 total)
Take a look at the COLUMNS_UPDATED feature of a trigger and make your Audit table look something like this...
AuditID ModDate ModBy TableName ColumnName NewValue (OldValue)
... I put OldValue in...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2006 at 6:24 pm
VERY nicely done... VERY easy to read and the comments are just right... What do the contents of the tblRefTimeZone look like and where do folks get that info...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2006 at 5:28 pm
Actually, you'll need quite a few other scripts if there are indexes, foreign keys, and triggers. That's why I use EM to take care of it... it "automagically" does all...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2006 at 12:31 pm
Nope... couldn't do that because the first underscore will interfere with finding the second underscore.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2006 at 12:28 pm
I can't tell if you want "High/Low" returned as a literal or a boolean... this will do the boolean thing... let us know what you really need.
DECLARE @MyCase INT
... do...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2006 at 6:01 am
Yep... use OSQL to run the query from a CMD prompt (or using xp_CmdShell w/ trusted connection) with a redirect (the -o option) to a text file.
See "Books Online" for...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2006 at 5:53 am
Mark,
Remi and I got a bit carried away on a sidebar... are you all set or do you need additional help?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2006 at 4:51 am
Roger that... thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2006 at 4:49 am
Alright... I've been looking for a while, now... how the heck do you submit a QOD on this forum?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 11:10 pm
p.s. Forgot to mention that the 812006 in the file names can change...
I just assumed that the "Watch" prefix could change, as...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 9:53 pm
Outstanding, Ray... that was the next thing I was going to ask... who changed what? You beat me to it. And, thank you very much for the feedback... you'd be...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 9:46 pm
First, you must realize that SQL is NOT SQL... most books on SQL I've seen rely on supposed advanced techniques using ANSI SQL. Others are based more on what Oracle...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 9:35 pm
Was it ever able to see D?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 8:31 pm
Vladimir,
The best way to do this is to collect all the data from the user first even if it's for 4 or 5 levels, as you claim. Then, do a...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 8:28 pm
Might as well bite the bullet while you're small...
Lock down the production database. Remove SA, DBO, and DDL ADMIN privs from all developers and users. Insist on code reviews and unit/itegration...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 8:22 pm
Viewing 15 posts - 57,721 through 57,735 (of 59,067 total)