Must SQL Backup use a domain account or can it leverage NTSERVICE\SQLAgent$instance?
johnctn
Posts: 1
in SQL Backup
This previous post relating to SQL 2008 and an earlier version of SQL Backup Pro basically says that in order for the SQL Backup Agent service to perform backups it must have a specifically defined SQL Server Login rather than leveraging the NTSERVICE\SQLAgent$instance virtual account that SQL Server Agent uses to access the server.
https://forum.red-gate.com/discussion/8542/installing-on-sql-2008
The response given was that Microsoft requires a SQL Server Login for the service account to be created and the account had to be given sysadmin rights (and the other rights/permissions, of course). Even though once you configure SQL Server Agent to use a domain service account, the virtual account handles SQL Server Agent's access.
Our admin would prefer not to create logins on the servers for the domain accounts because it pretty much invalidates the whole purpose of the virtual account.
So, two questions arise:
1)Can you confirm that this is still a requirement for SQL Backup Pro 9? (I haven't been able to get it work without the specific login.)
2)Is this still a MS requirement for the VDI library? One would think that by now MS would have found a way to allow vendors to leverage the virtual accounts, but it wouldn't surprise me if they haven't.
Thanks!
--John
https://forum.red-gate.com/discussion/8542/installing-on-sql-2008
The response given was that Microsoft requires a SQL Server Login for the service account to be created and the account had to be given sysadmin rights (and the other rights/permissions, of course). Even though once you configure SQL Server Agent to use a domain service account, the virtual account handles SQL Server Agent's access.
Our admin would prefer not to create logins on the servers for the domain accounts because it pretty much invalidates the whole purpose of the virtual account.
So, two questions arise:
1)Can you confirm that this is still a requirement for SQL Backup Pro 9? (I haven't been able to get it work without the specific login.)
2)Is this still a MS requirement for the VDI library? One would think that by now MS would have found a way to allow vendors to leverage the virtual accounts, but it wouldn't surprise me if they haven't.
Thanks!
--John