August 5, 2008 at 9:53 am
I've created a big integration services package which I've deployed to our main server and set to run overnight by using a sql agent job. Only problem is that sometimes we need to run it in the daytime too. I want my involvement to finish here now and give the responsibility of running these tasks on request to my support team however, I've just noticed...they don't have SQL Server Management Studio! Yes, I know...I should have checked this first, but too late now!
The old version of my program which is now obsolete, used to run from the scheduled tasks screens. They had access to this. Is there any way I can set something up so that they can run such a job without SSMS e.g. can I write a batch file to run it as a set of commands or something like that? Complication with the package is that it runs from a configuration file as well.
August 5, 2008 at 11:39 am
If it's a job, they only need to be able to run sp_startjob in the msdb database. You could create a batch file that runs SQLCMD/osql to make this work.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
August 6, 2008 at 2:32 am
Cool! I'll look that up to see how to run it.
September 8, 2008 at 6:41 am
Forgot to add that I got this to work nicely. I used the sqlcmd command in the end. The syntax was as follows in the bat file (items in violet being what you substitute in):
sqlcmd -S servername\sqlinstance -E -i sql script -b -o log file
September 8, 2008 at 6:42 am
Oops! Doesn't look like my colour tags worked on this!!!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply