Recently, I was working at a client's site where SQL Server 2000 was still in use. They wanted to upgrade to SQL Server 2005. The only reason they were looking at the Enterprise Edition was for data-driven subscriptions in Reporting Services. The CEO certainly wasn't interested in paying the sort of dollars required for that, just to be able to automatically email out a set of monthly reports to about 30 or so folk within the company.
A quick bit of research led me to Jason L. Selburg's article at Code Project on how he achieved this by modifying the subscription details in the ReportServer database. You'll find his original post here: http://www.codeproject.com/KB/database/DataDrivenSubscriptions.aspx
I wanted to tackle a more complete version than Jason provided. There were a couple of key limitations:
1. You'd have to modify the stored procedure every time your parameter list changed. (and potentially have different stored procedures for different reports).
2. He used commands for manipulating the ntext columns that were deprecated. I wanted to avoid these.
3. The code didn't deal with concurrent usage.
Below, you'll find an alternate version of the proc. The concept is still the same. You create a subscription to a report, using tokens for parameters, set the subscription to happen in the past and then execute it using this proc in a scheduled Agent job. The different approach I've taken is:
1. I've provided the ability to deal with a parameter list rather than a single parameter.
2. I found that the ntext columns actually only contained simple xml. While I could have used XQuery to modify it, it's easier to directly manipulate it as varchar data (could have used nvarchar), given all we're doing is replacement of tokens with values. Either way, this avoids the use of UPDATETEXT etc.
3. I've used more of my style of naming conventions..
4. I've used a global temporary table as a flag to limit concurrent use. (Without this, the scheme could fail).
Hope you find it useful.
/*
ExecuteSubscribedReport
PROCEDURE DESCRIPTION:
Creates the effect of a data driven subscription by replacing the fields in
an existing subscription with the supplied values, executing the report
and then replacing the original values.
INPUT:
@ScheduleID The Job Name in SQL Server
@EmailTo The TO address of the email
@EmailCC The Carbon Copy address of the email
@EmailBCC The Blind Copy address of the email
@EmailReplyTo The Reply TO address of the email
@EmailBody Any text that you want in the email body
@ParameterList The parameters for the report in the format 'Parameter1Token,Parameter1Value,Parameter2Token,Parameter2Value...'
Example: '|StartDate|,20071231,|Salesperson|,GE,|Region|,NW'
OUTPUT:
None
WRITTEN BY:
Greg Low based on a concept from Jason L. Selburg at CodeProject.com
LIMITATIONS:
ParameterTokens and ParameterValues are limited to 1000 characters
EmailBody is limited to 8000 characters
ParameterList is limited to 8000 characters total
*/
CREATE PROCEDURE dbo.ExecuteSubscribedReport
( @ScheduleID uniqueidentifier,
@EmailTo varchar (1000) = NULL,
@EmailCC varchar (1000) = NULL,
@EmailBCC varchar (1000) = NULL,
@EmailReplyTo varchar (1000) = NULL,
@EmailBody varchar (8000) = NULL,
@ParameterList varchar (8000) = NULL
)
AS BEGIN
DECLARE @extensionSettingsPointer binary(16),
@parametersPointer binary(16),
@tokenPosition int,
@tokenLength int,
@subscriptionID uniqueidentifier,
@parameterToken varchar(1000),
@parameterValue varchar(1000),
@parameterPosition int,
@numberOfParameters int,
@parameterCounter int,
@character varchar(1),
@parseStatus varchar(1), -- 0 ready for another token, 1 in a token, 2 in a value
@originalExtensionSettings varchar(8000),
@originalParameters varchar(8000),
@newExtensionSettings varchar(8000),
@newParameters varchar(8000);
DECLARE @parameters TABLE (ParameterID int IDENTITY(1,1),
ParameterToken varchar(1000),
ParameterValue varchar(1000));
-- first we need to unpack the parameter list
IF @ParameterList IS NOT NULL BEGIN
SET @parameterPosition = 1;
SET @parseStatus = 0;
SET @parameterToken = '';
SET @parameterValue = '';
SET @numberOfParameters = 0;
WHILE @parameterPosition <= LEN(@ParameterList) BEGIN
SET @character = SUBSTRING(@ParameterList,@parameterPosition,1);
IF @character = ',' BEGIN
IF @parseStatus = 0 BEGIN -- we had two commas in a row or the first character was a comma
PRINT 'ParameterList has incorrect format';
RETURN 1;
END
ELSE IF @parseStatus = 1 BEGIN -- we are at the end of the token
SET @parseStatus = 2;
SET @parameterValue = '';
END
ELSE BEGIN -- we are at the end of a value
INSERT @parameters (ParameterToken,ParameterValue)
VALUES (@ParameterToken,@ParameterValue);
SET @numberOfParameters = @numberOfParameters + 1;
SET @parseStatus = 0;
SET @parameterToken = '';
END;
END ELSE BEGIN
IF @parseStatus = 0 BEGIN -- we have the first character of a token
SET @parseStatus = 1;
SET @parameterToken = @parameterToken + @character;
END
ELSE IF @parseStatus = 1 BEGIN -- we have another character in a token
SET @parameterToken = @parameterToken + @character;
END
ELSE BEGIN -- we have another character in a value
SET @parameterValue = @parameterValue + @character;
END;
END;
SET @parameterPosition = @parameterPosition + 1;
END;
IF @parseStatus = 2 BEGIN-- we were still collecting a value
INSERT @parameters (ParameterToken,ParameterValue)
VALUES (@ParameterToken,@ParameterValue);
SET @numberOfParameters = @numberOfParameters + 1;
END;
END;
-- we need to wait for our turn at using the subscription system
WHILE EXISTS(SELECT 1 FROM tempdb.sys.