November 13, 2008 at 4:59 pm
We have a maint plan that backs up a database.
The database MUST be backed up before this user performs a certain mass update task.
I want the user to be able to initiate the backup maint plan on demand.
(So I don't have to get a call from them to do it allowing them to do their work outside of normal business hours)
I was thinking of two appraches:
1. Make a webpage (ASP.NET) that calls a sproc that executes the backup and returns the results as complete or fail
2. Setup a batch file they can execute that would execute the TSQL to kick off the maint plan. Though I think they would need access to TSQL command line for this.
Thoughts?
November 14, 2008 at 3:06 am
You should definetely use a stored procedure because like that you can contril the permission necessary. Normal users don't have enough permissions to make backups. By ussing the EXECUTE AS clause in a stored procedure you can work around that without giving you users extra permisssions.
How they kick off the stored procedure is more a question about what's easiest for you and your users. In past I once implemented a similar scenario using email. Users send a mail to SQL Server, there a job checked every minute for new mails. If the mail was in the correct format a backup was made and a reply mail send to the users with the outcome.
[font="Verdana"]Markus Bohse[/font]
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply