Video Screencast Help

Compliance accelerator SA rights on SQL Server

Created: 07 Jun 2006 • Updated: 17 Nov 2010 | 5 comments
This issue has been solved. See solution.

The compliance team tried to schedule a job through the web app and it failed on a permissions issue. Support says login needs to have 'sa' rights on the SQL Server server. Company policy does not allow Application accounts to have these privileges. Has anybody else dealt with this problem?

Comments 5 CommentsJump to latest comment

Micah Wyenn 2's picture

That's shouldn't need any additional rights to the SQL db's (other then dbcreator for the VSA) to submit jobs.


TonySterling's picture

Support is correct...

From the install and configure guide:

Setting permissions on SQL databases
Search schedules in Compliance Accelerator use SQL jobs in
SQLSERVERAGENT. To enable Compliance Accelerator to create and modify
these jobs, the Vault Service account must be a SQL System Administrator on
the SQL Server.Message was edited by:
Tony Sterling

TonySterling's picture

A work around would be to give the account sa rights, create your schedules and get everything in place and then remove the sa rights. A bit of a pain, but right now that is the way it is.

I have read in SQL 2005 MSFT is splitting that task out of the SA role and adding some new roles like SQL Agent reader role and SQL Agent Operator Role that will be able to control jobs they own. So in the future it can be changed, but right now w/ sql 2000 it is what it is.

SymcMarj's picture

You actually do need SA rights to submit jobs to the scheduler. You dont need SA privs to complete other actions.

Logan Sutterfield's picture

OK, let's close the loop on this one.

SA is needed for SQL jobs created by the scheduler only. Although there may be futures that will allow a seperate role; the current is SA if you want to run scheduled searches.

If you need to get around this, dedicate a SQL server or create an instance.