I try not to cry on fridays.. it's almost the happiest day of the week. So I try to keep it that way.

Not to mention that you always have to know the keytype when you write the queries... try changing the key type once the project is one year old. Can...

It's always silly once we find it... the job really is FINDING IT.

One last thing that might have saved you some time : There's a stored proc debugger that can...

No beer for me... Trying to become a Pro in Billiards (9 ball). But I got a verrrry long way to go... Maybe you guys will see me on...

Nice variant and one less step to it. But I wouldn't expect a big performance boost since the (SELECT MAX(identityCol) FROM TableA) in the first example will be...

I would get those books... but I got a life outside of work and I'd like to keep it that way... There's so much more to learn outside of IT.

That's the problem in our society. We all want more for less work... We can't have it both ways. But I see how that is a big problems...

Yes truncate is faster... but the problem here is that he doesn't want to delete data that has been inserted after he transfered the data to history.

BTW, no offence to Michael, I know he's a great helper on this message board.

That's what I thaught... I've seen cases where the same solution is reposted when the thread is huge... or posted at the same time. But posting the same...

Ya I wasn't too sure that it could be the case in this situation... But I thaught: what else can be causing the server to fail/succeed when using the same...

We'll be hijaking it together...

For the tsql you'll have to stay around because I pretty much learned everything here. I mean, I knew of to do basic stuff out...

I don't think you can cover 100% in this case.. there's always be something else that can screw up.

First of all bravo for this thread. Second of all WOW for that line : "If you want everyone to be just like you, then their thought is going...

Tx for the tip.