FarmboyEsq
Programmer
Hi,
Any nifty ideas on how I can hold up a report's data driven subscription until the data source (a SQL Server Database) is restored? My data driven subscription (DDS) is blowing up if it runs while the DB is still restoring.
The DDS reads a separate database, invoking a stored procedure that watching msdb.dbo.restorehistory waiting for this mornings restore to finish. It basically does a WAITFOR DELAY loop until its ready. I was hoping this would give me sufficient isolation from the DB being restored. (The DB being restored is the one that holds the data read by the report.)
But the DDS blows up whenever I test my approach with a restore running.
I would rather not move to SQL Server Agent job scheduling for these reports. But, am open to any and all ideas.
Thanks!
Any nifty ideas on how I can hold up a report's data driven subscription until the data source (a SQL Server Database) is restored? My data driven subscription (DDS) is blowing up if it runs while the DB is still restoring.
The DDS reads a separate database, invoking a stored procedure that watching msdb.dbo.restorehistory waiting for this mornings restore to finish. It basically does a WAITFOR DELAY loop until its ready. I was hoping this would give me sufficient isolation from the DB being restored. (The DB being restored is the one that holds the data read by the report.)
But the DDS blows up whenever I test my approach with a restore running.
I would rather not move to SQL Server Agent job scheduling for these reports. But, am open to any and all ideas.
Thanks!