Already been voted about 5 times... now we just need to go to supreme court with this and then we should be able to move on!

I already agreed with you 3 times.  What do you need??????????

And yes I'll keep dropping 'em because my mammooth won't get scared by a cold fly

Please post only once.  We monitor all boards equally.

Finish the thread here :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=65&messageid=324355

Please post only once.  We monitor all boards equally.

Finish the thread here :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=65&messageid=324355

Impossible... please post the queries you are using!

Distinct and group by are used for different things, but certainly not on that matter.

PS

Did you get this error with ssms when opening the job history or is this the error message you got IN THE HISTORY >> major difference here

I can't imagine this being faster.  You have to make it work both for 2000 and 2005 at the same time...  Maybe as fast but certainly not faster.  I mean...

How about set it at the column level.  Then again it might be the problem.

What is the problem exactly?

Sure, you can quote me on this .

Ya but also how long was the server and databases left alone wihtout maintenance and checking for basic stuff like free space.  I agree he's partly responsible of this... but...

Because of the way the error message was cut.  It seems like the error could have originated because of a forbidden character in the job name.

So the conclusion still stands.  There's a hit on explicitly dropping temp tables but about as much as a fly sneezing on a mamooth from 10 feet away

Maybe I can fill in the gaps... What exactly is the need that you need to fulfill with data auditing?

Congrats on the 600 Lowell... you got there at the same time as I hit [7]900 .

To complete your post, the 2nd run is...

You could find that out using profiler... or by auditing all the tables.  Search this site for "auditing tables" and you'll find plenty of information.