@@error

Question

@@error

stephenhai

Mr or Mrs. 500

Points: 553
More actions
January 15, 2010 at 1:06 pm

#229161

My company is going to upgrade from 2000 to 2008.
Do I need to change all the @@error logic to Try...Catch logic
Thanks

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Ray K SSC-Dedicated Points: 31148 More actions · Answer 1

stephenhai (1/15/2010)
My company is going to upgrade from 2000 to 2008.
Do I need to change all the @@error logic to Try...Catch logic

No, you should still be able to use @@error, although Try...Catch is a pretty good structure. If it was me, I'd move my code over and take my time with changing to Try...Catch.

+--------------------------------------------------------------------------------------+
Check out my blog at https://pianorayk.wordpress.com/

stephenhai Mr or Mrs. 500 Points: 553 More actions · Answer 2

Thanks...

Anythings need to pay attention when upgrade from 2000 to 2008

Jeff Moden SSC Guru Points: 1003921 More actions · Answer 3

stephenhai (1/15/2010)
Thanks...
Anythings need to pay attention when upgrade from 2000 to 2008

When you say "upgrade", I think "in place upgrade" and I wouldn't do it that way. I'd have both a 2k and 2k8 box running in parallel for a while until I fixed all the things that will (yep, I mean "will") break in the "upgrade".

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

stephenhai (1/15/2010)
Anythings need to pay attention when upgrade from 2000 to 2008

Lots.

Run the upgrade advisor. Fix everything it complains about.

Set up a test server running SQL 2008. Test your apps end to end on that. Fix all issues that you find.

Then consider upgrading the real database.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass