Perhaps you could have a stored procedure that runs continuously (loop back to start) with a WAIT DELAY '000:00:20'.  That would solve the problem of trying to schedule a job...

Karen,

Bob and I both made the same boo-boo... in the code where the fields get added up, you must include all of that addition in parentheses or you'll get the...

There's many ways to do this but most will involve a loop or a (yeeeeech!) Cursor (Haaaaaack... Patooooooiiiii!), a temp table, or maybe some extra columns added to your existing...

Beryl,

Borrowing on Kathi's idea, this may run a bit faster because it does no string manipulation or conversion and only has one comparson operator (=).  And it could easily be...

I agree that dependencies related tables are (more or less) unreliable but the SYSOBJECTS and SYSCOMMENTS tables are always up to date with the latest code for any given object.  The...

You may want to avoid using the guest account for several reasons... here's what the MSDN link that yoav provided warns of...

"Avoid using the guest account; all logins without their...

>Colleague put a trigger on the table that was causing the error.

Paully21,

There may be a much larger problem lurking in the shadows of that trigger you found... many folks write...

This code also works... Like the code that Kenneth posted, you should be made aware that if the, say, stored procedure is longer the 8k bytes and the table name...

You bet, Gazley... BOL tells you EVERYTHING and sometimes it's much more than you need (although, I always start there) or can be difficult to draw a conclusion from.  It...

John,

SCOPE_IDENTITY() does require the use of parentheses like GETDATE() does.  I didn't see them in the code you posted and I'm hoping that was the only problem you had.

Gazley,

The reason I said that using @@IDENTITY in the presence of triggers is "Death by SQL" is because of the way @@IDENTITY works... it (basically) returns the IDENTITY of the...

Like I said, Joe... all of your explanations are spot on and I agree with telling folks of the dangers that lurk out there... but there's two ways to tell...

Dang, Joe... lighten up!  All of your suggestions are spot on but you have to remember that, sometimes, it's a third party database that these folks have to deal with...

Then you already know that using @@IDENTITY in the presence of triggers is "death by SQL" and that the use of "it" is hardly ever the "best way"   (as Ken was...

Thanks nskr72... I missed that.