You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
I updated from 1.9.1 to 2.0.2 and then ran ssc pull, and ssc seems to get stuck after this error appears:
✖ RequestError: The SELECT permission was denied on the object 'sysjobsteps', database 'msdb', schema 'dbo'.
I reviewed the CHANGELOG and can see that SQL job info is now being stored by SSC. However, I'm using SQL Server on AWS RDS, and I suspect this is why my user doesn't have permission to access the jobs (AWS RDS handles backups and other things typically done in jobs).
I tried to figure out how to skip jobs during the processing, but failed. I thought maybe this would work in my json config file, but it didn't:
{
"output": {
"jobs": false
}
}
Any recommendations?
The text was updated successfully, but these errors were encountered:
winzig
changed the title
✖ RequestError: The SELECT permission was denied on the object 'sysjobsteps', database 'msdb', schema 'dbo'.
RequestError: The SELECT permission was denied on the object 'sysjobsteps', database 'msdb', schema 'dbo'.
Jan 22, 2019
Describe the Issue
I updated from 1.9.1 to 2.0.2 and then ran
ssc pull
, and ssc seems to get stuck after this error appears:I reviewed the CHANGELOG and can see that SQL job info is now being stored by SSC. However, I'm using SQL Server on AWS RDS, and I suspect this is why my user doesn't have permission to access the jobs (AWS RDS handles backups and other things typically done in jobs).
I tried to figure out how to skip jobs during the processing, but failed. I thought maybe this would work in my json config file, but it didn't:
Any recommendations?
The text was updated successfully, but these errors were encountered: