Comments
Sort by recent activity
The account 'CORP\sqlsrv' runs the SQL Backup service, the SQL Server service, and the SQL Agent service.
So I signed onto the server as 'CORP\sqlsrv'.
And then execute the code posted previously from query analyzer.
In each case I start in the master database.
By changing the line 'USE [<database name>] ' to each of the databases on the server in turn the script runs ok, except for two databases.
sp_who2 shows the process as runnable. There is no blocking at all on the server. / comments
The account 'CORP\sqlsrv' runs the SQL Backup service, the SQL Server service, and the SQL Agent service.
So I signed onto the server as 'CORP\sqlsrv'.
And then execute the code posted previously f...
If the "USE [Database]" statement is removed (line 17?) the code will execute correctly.
What is interesting is that the sode below the IF statement is being executed when it shouldn't.
If you run "DECLARE @hasrights integer
SELECT @hasrights = IS_SRVROLEMEMBER('sysadmin', 'CORP\SQLSRV')
PRINT @hasrights -- I added this to see what the result is"
You get 1 as the result of the PRINT. On that basis the "IF (@hasrights = 0) OR (@hasrights IS NULL)" should not be exeuted. However it is.
I am logged on to the server as 'CORP\sqlsrv'. So even though that account is a sysadmin it is not being recognised as such. / comments
If the "USE [Database]" statement is removed (line 17?) the code will execute correctly.
What is interesting is that the sode below the IF statement is being executed when it shouldn't.
If you run ...
Nudge. / comments
Nudge.
The only collation problem I could see was http://www.red-gate.com/support/kb/KB200707000071.htm, however we are running a version higher.
Is there any further logging that I can do do provide more information?
The backups do work when the same script is run from query analyzer. / comments
The only collation problem I could see was http://www.red-gate.com/support/kb/KB200707000071.htm, however we are running a version higher.
Is there any further logging that I can do do provide more...
I changed the database to master, and fully qualified the stored procedure that calls SQLBackup. Works fine for one db, but not the other. / comments
I changed the database to master, and fully qualified the stored procedure that calls SQLBackup. Works fine for one db, but not the other.
Hi Brian,
I did see those other posts and did wonder if my fault was related, however since it didn't contain any messages containing 'could not get information about user...' I wasn't sure.
The server that SQlBackup is running is in the CORP domain.
If it is timing out because of network topology am I wrong in pursuing the collation difference theory? I would have expected for an AD related the failure to be consistant for any backup, not just against any database with a different collation to the server. If I create other databases for testing this all that have a collation the same as the server succeed, all that have different collation fail. / comments
Hi Brian,
I did see those other posts and did wonder if my fault was related, however since it didn't contain any messages containing 'could not get information about user...' I wasn't sure.
The se...
Hi Brian,
It has recorded the backup and the error message in the GUI. It shows the correct account attempting the backup 'CORP\sqlsrv', which is the service account that SQL Backup uses.
Regards
Stephen / comments
Hi Brian,
It has recorded the backup and the error message in the GUI. It shows the correct account attempting the backup 'CORP\sqlsrv', which is the service account that SQL Backup uses.
Regards
S...
that I have not been able to resolve this, and wonder whether there is a configuration change I need to make? / comments
that I have not been able to resolve this, and wonder whether there is a configuration change I need to make?
Hi Brian,
The account that is used by the SQL Backup service, the SQL Agent service, and the SQL Server service is the same one (in our case 'CORP\sqlsrv'). It has system administrator server role permissions to all databases by default.
I have tried getting the SQL Backup Agent to log in using SQL Server authentication by using:
sp_addextendedproc sqbsetlogin, 'xp_sqlbackup.dll'
GO
sqbsetlogin 'sa', 'sqbpassword'
GO
sp_dropextendedproc sqbsetlogin
GO
This did not resolve the issue.
I tried this:
I create two databases. One called SQLBackpTest, and another SQLBackpTest2.
SQLBackpTest has a collation of SQL_Latin1_General_CP1_CI_AS
SQLBackpTest2 has a collation of Latin1_General_CI_AS.
The server collation is Latin1_General_CI_AS.
A scheduled backup of SQLBackpTest fails with Error 880: BACKUP DATABASE permission denied. A scheduled backup of SQLBackpTest2 succeeds.
Regards
Stephen / comments
Hi Brian,
The account that is used by the SQL Backup service, the SQL Agent service, and the SQL Server service is the same one (in our case 'CORP\sqlsrv'). It has system administrator server role ...