When you say "somewhat changed" what exactly?

Have you updated statistics or, better still, rebuilt your indexes in recent memory?

Congrats again then.

And a WOO HOO to go with it.

:w00t:

Oh yes, Profiler and Perfmon. They can do more for you than almost any third party tool.

Set up Profiler to run by script (look up sp_trace_create & sp_trace_setevent among others)...

Another vote for Visual Studio. Hook it into source control and then you get versions of your scripts too. Very handy when one of them suddenly breaks for no apparent...

In addition to what Matt Miller is suggesting, you might verify that the data types of the parameters is the same as the data types of the columns. If you're...

You have to understand, BOL is my best friend because I'm too darned stupid to remember stuff.

Oh, that's likely to be a bit tougher then. I'm not sure how you'd do this in 7.0 (haven't touched it in years and years).

Just note, it's 'sys.databases' not 'sysdatabases'. You need to get in the habit of looking at the catalog views, not the 2000 system tables.

You can use parameters within sp_executesql. Those parameters can be output parameters. You can set those values within the ad hoc query and output them from there and then set...

Probably a completely inadequate solution... but I wanted a little experiment this morning:

CREATE TABLE #DBList(DBName NVARCHAR(100))

DECLARE @Tablename NVARCHAR(100)

DECLARE @Tsql NVARCHAR(MAX)

DECLARE @DBName NVARCHAR(100)

DECLARE Cur CURSOR FOR

SELECT NAME

FROM [sys].databases;

SET @Tablename =...

I got them, but both were tagged as potential spam by our filter. Maybe that's where yours are?

AND, can't believe I forgot this, you need to look at the selectivity of the data in those columns to be sure an index will work well.

First question I'd ask is, what are the additional search criteria? That will affect the index. Also, do you have clustered indexes already on these tables? If so, what columns?...

From BOL:

Avoid using float or real columns in WHERE clause search conditions, especially the = and <> operators. It is best to limit float and real columns to > or...

The problem with floats is that they are imprecise, by definition.

Sorry about the bit of misdirection. I used it against a decimal several times with no issue. Works well in...