Unfortunately you cannot use top with a variable in SQL 2000.  Most of the time, people either use set ROWCOUNT, dynamic SQL OR...  You could insert the data into a...

Try running from your client app and use some form of execute with no records option (I know that ADO can do this - I assume ADO.NET can also do...

Certain features in SQL, such as linked servers and indexed views, as well as indices on computed columns, require certain SET options to be set a particular wasy.  This is...

Are you sure it is the insert statement?  By the sounds of it, you have other statements in the proc as well apart from the insert given.  Change your code...

Both of your subqueries are correlated, which is often a problem, but with the 1st query, SQL probably has to do a lot more evaluation and reading rows to determine...

Elegant solution (I too like the trick to get the correct day regardless of datefirst!  Clever!).  BUT...  recursion in SQL is limited to 32 calls (XMAS holidays in schools, for...

I consider it a best practice thing to ALWAYS name your result columns and use column names to refer to the columns in your client-side code.

EG.  You could have

select @@rowcount...

I too am from a Crystal background and would say that you could have a long query that reporting services runs, or have it call a stored proc.  You could...

Strange amount of GB on Itanium system..  Spose 3GB could also be seen as a strange amount on a 4GB system too

Thanks for...

Are you sure that is the entire proc?  Why are you declaring a variable called @result?

With regards to your SP, are you after

a) The resultset the SP returns

b) The value of an output param

c) The return value of the SP

?

This sounds bizarre...

Your report must be working in one of the following ways...

1.

It is a typical report - users set their parameters, the report generates a simple select statement (or...

I can only assume because bitwise operators are non SARGable - effectively SQL cannot use an index when you are working with such operations.  Thus SQL cannot, based on the...

You should have indices on the fields on either side of the join to increase its performance - having a FK defined doesn't define an index for you..

BTW... output is

yr          total       grp         
----------- ----------- ----------- 
1990        15          1-20
1990        70          21-55
1995        60          1-20
1995        40          21-55