SQL Server database programming

Hi,   We have a tough situation when we migrated one of the view from SQL Server 2000 to SQL Server 2005, we have seen CPU hogging around 100% when we access this particulat view. It works fine in SQL 2000 but has CPU hogging in SQL ...

We are finally migrating from 2000 to 2005 and in our jobs, we run one T-SQL procedure as our only step. exec ourprocedure 1, [JOBID] and then look up our own custom info about that job when "ourprocedure" runs. This now gets errors at run-time. We have 2005 SP2. I have been reading ...

Hi, Is there a way in either SQL server 2000/2005 that would allow me to create a stored proc from the output of a query? Eg. To demonstrate my question lets say I have a script to create a table ...