March 15, 2007 at 10:06 am
I have developers managing SQL Scheduled jobs on the developent box, but have some problems with SQL Security. It seems that a user needs SYSADMIN access just to modify the job to write out a text file !! That seems crazy. But I gave one access for now. Even still, after the job ran, she can't view the text file, the "view" button is greyed out. She can log on the server itself and view it through Windows, just not through SQL. Any thoughts on this problem and SQL security for developers & jobs in general ??
March 14, 2008 at 12:36 pm
I'm not sure exactly what rights are required to write out to a text file, but I do know from experience that MS only left the view button in SSMS to support SQL 2000. If you register a SQL 2000 server in SSMS, the view button works as you'd expect.
I have no idea why MS eliminated this very useful capability with 2005. What MS wants us to do now for SQL 2005 is copy the path to the output file into the clipboard, open notepad or some other editor, paste the path into the file/open dialog, replace the drive letter colon with UNC path to the server, then open the file.
March 14, 2008 at 2:18 pm
Two problems here ...
1) You don't need sysadmin to modify jobs, there are new roles with in the MSDB database you can apply to users. Check out BOL for the SQLAgent roles.
2) The user can't view the file on disk, because he/she does not have access to the file system where the file is stored.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply