Marks's approach reduces your number of where clauses from 125+ to 25+. Since each of those where clauses probably results in a Scan, this will lower your scan count...

And the funny things is, what I always liked the most about SQL was how easy it was. IMHO, it is a lot easier than any 3GL/OO language that...

Heh, don't suppose I'm getting my two points, eh?

Never mind, I'll take them from these replies. Besides, I wouldn't want any more "enlightened" posters accusing me of point-mongering.

Here it is:http://www.sqlservercentral.com/Forums/Topic512477-338-1.aspx

I do this a lot also, and it has been my experience that you have to put TRY..CATCH in both the calling proc and the called proc.

There was a discussion...

Do you have multiple Instances on the same Server? And what SP are you at?

There is nothing wrong with what you have showed us, but I don't think that you have showed us everything. The IF..Select.. will perform fine if you have an...

Please supply CREATE Table statements and sample data as Raja has requested, or read this article on how to get better results from these forums: http://www.sqlservercentral.com/articles/Best+Practices/61537/.

Try this link: http://blogs.msdn.com/khen1234/archive/2005/06/02/424228.aspx

Two Words: "Service Broker"

Very true. And sadly not even Microsoft is immune to this as some of thier most important flagship products show clear signs that their databases were designed and implemented...

The real difference between these languages isn't the hair-splitting technical differences, nor is it the religious-based flame-wars over what are simply style differences and personal preferences.

No, the Real...

This article is OK. Though he gets a lot of the details wrong, he gets the big issues right: which one is "better" is largely a matter of...

This article is nigh-useless. First of all, it's 4 to 6 years out of date. For that time-frame it does get most of the explicit facts that it...

Sorry, Sergio, but this just isn't true. "Professional" and "clearer"...