Comments
Sort by recent activity
Hi, Peter
Sorry for the long delay in reply as my browser was pulling from a cache or something and I didn't realize there was a reply for me. @ERROR would be equal to 0 and you wouldn't catch that there was an error. Since the error isn't caught, there would be no 'ROLLBACK' and no rows inserted into #tmpErrors. (Or at least that is how I read the script.) @ERROR check but because of the
SET XACT_ABORT ON
GO
that is at the beginning of the script. I've never used SET XACT_ABORT ON; so I'm unsure of how that effects everything. I was testing it last night and I'll test it some more tonight. / comments
Hi, Peter
Sorry for the long delay in reply as my browser was pulling from a cache or something and I didn't realize there was a reply for me.@ERROR would be equal to 0 and you wouldn't catch that ...
:shock:
There's two links?
:oops:
Well, so there is.
Anyway, the second link wasn't visible when I was trying to link the second db and I wasn't familiar enough with the interface to recognize the missing second link. I e-mailed some screenshots to Stephanie so show how it looks with SSMS sized at about half my screen and stretched out large enough to see the second link. Now I can get on with my testing. / comments
:shock:
There's two links?
:oops:
Well, so there is.
Anyway, the second link wasn't visible when I was trying to link the second db and I wasn't familiar enough with the interface to recognize the ...