Check the "Close connection on Completion" option in the Workflow Properties of the ExecuteSQL task.

Maybe the scan is being produced by another T-SQL statement.

Best way to isolate this is to run the statement in Query Analyzer with "Show Execution Plan" turned on.

When you alias a table you need to use the alias instead of the table name.

Change "UPDATE Store_Table" to "UPDATE s"

I would also suggest you get into the habit of...

Ahhh ... the actual info on recovery interval is,

" SQL Server estimates how many data modifications it can roll forward in the recovery time interval. SQL Server typically issues...

I think this is more a case of the purpose and use of the report needs to be revisited and maybe the selection criteria adjusted to provide a smaller list...

The apology isn't necessary, but I'll accept it anyway

Given the recent rash of next to useless posts by Hemasunder, I'd say they're just trying to increase their post count.

Yes, so by that logic it should print 'Length = 0' ( which it does for me )

Vladmir's problem is that it's printing 'Length > 0'

Hema, I think what Rafter posted is the Execution plan.

Rafter, simple question, are you sure you have the right plan for the right...

Check the Execution plan on each server. This will verify if the same indexes are being used and if any statistics are missing or out-of-date.

Hmmm ... works fine for me.

Are you sure you're passing in the correct input?

Put a print statement to show the @i_name variable before the If .

Hema, A Backup and Restore won't be of any use in this situation because the data will still reside on the original server. That being the case you might as...

You could setup your report on a schedule then check the command text of the SQL Agent job that is created.

Just use the same command text in a trigger or other...

Take a look at the following.

http://www.sqldts.com/default.aspx?297

I have not had the problem myself, but there are many posts about email problems with SQL and Outlook.

My suggestion would be to avoid the problem and use DTS SMTP...