This might work:

SELECT

* FROM X

INNER JOIN

DECLARE

@cmd VARCHAR(max)

SET @cmd = ''

SELECT @cmd

ROW_NUMBER is a good way to deal with this type of problem.  This is guaranteed to return 1 email per candidate, even if you have more than one flagged as...

You could set up the Excel destination with the "First row has column names" box unchecked.  Then you need to add a row with the variable column names first, followed...

You could write a data source script component that created a standard collection of output columns and took care of mapping the stored procedure variable column names to the standard...

Go back to the Tools|Options menu in Query Analyzer and get a little more creative.  Change "Result file extension:" to .xls on the General tab, then go to the Results...

There is no trick that will make your problem go away, you simply can't remove the identity property from a table.  You can do what Enterprise Manager is trying to...

The table scan could caused by using a VARCHAR variable to store the cutoff date instead of a datetime.

The DELETE may be creating a range lock on the Expired index for all values...

The script I get look like this:

SET

ANSI_WARNINGS OFF

SET NOCOUNT ON

SELECT CAST(

Did you switch to text mode before running it?  Grid mode screws up the line breaks.

We moved from SQL2000 32-bit to SQL2005 64-bit and have not had any major issues.  We don't have any custom external stored procedures, and we don't link to Oracle or...

Here's another one in color.  Why search the table once for every column?

USE

Northwind

DECLARE @schema sysname, @table

You can use NULLIF to change the '00000000' values back to NULL, but then you have to use ISNULL to replace the result with something > 1 if you want...