I have to fix a giant mess now. Not that I'm complaining, this keeps hte paychecks coming in. But still - I guess I'm complaining a little.

Client wants all their numbered procedures changed to a new style, to be determined. They apparently ignored the writing on the wall until upgrading recently to SQL 2005 and now that the feature is deprecated and scheduled for removal, it's got to be fixed.

They suggested changing dbo.ProcedureName;N to dbo.ProcedureName_N which will be easy for them to adapt. I'm not sure why this style of coding wouldn't have been used from the outset? The only reason I could think of would be using real names instead so you can look at your database and understand what it does.

Anybody else run into this?

Yeah, I did...

But mostly, it was that the job was taken backward at first.
IE: first programming, then the analyze, and it resulted in a lot of copy/paste.
Or at least, it's how it seemed.