Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
solart
Posting Yak Master
148 Posts |
 Posted - 2002-04-15 : 11:46:22
|
| I had a number of jobs which were backing up system and user databases under SQL 7 using SQL ServerAgent. Over the weekend I upgraded SQL 7 to SQL 2K. All backups work except for one, which gets the following error message: Executed as user: SANDIEGO\SvcSQLServer. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.As best as I know SQLSTATE 42000 is an ODBC message indicating a syntax violation or an access violation. I have recreated the maintenance plan in an attempt to rule out a syntax violation. During the upgrade process I did not change the account under which SQL Server Agent runs, so it seems like it should not be an access violation.Any ideas would be appreciated!!!andrews_gary_w@solarturbines.com |
|
|
solart
Posting Yak Master
148 Posts |
Posted - 2002-04-16 : 10:43:38
|
| A maintenance plan had the option selected to perform a repair for minor DB problems. Under SQL 2000, in order to perform a repair the DB must be in single user mode, which it is not when the backup is performed. When I deleted the "repair" option from the maintenance plan, the backup worked as expected. So this is obviously a change from SQL 7. Let me point out that the DB being backed up was in good health. So I think the option to perform minor repairs was detected at run time and treated as a syntax error (There was nothing wrong with the DB). |
 |
|
|
|
|
|
One backup quits working after upgrade to SQL 2K