Showing posts with label fail. Show all posts
Showing posts with label fail. Show all posts

Thursday, March 8, 2012

Backups to network share fail

I am having an odd failure when backing up my SQL 2000 SP3 server to a
network share. I receive the following error:
BackupDiskFile::CreateMedia: Backup device '\\server\share\master.BAK'
failed to create. Operating system error = 5(Access is denied.).
However, the following T-SQL command does run and create the appropriate
file in the same network folder:
EXEC xp_cmdshell 'dir \\server\share > \\server\share\test.txt'
Both the SQL Server and SQL Server Agent is running under a domain user
account which has the required permissions to this share. Other SQL Servers
(SP3 and SP4) which also run under the same domain user account are backing
up to the same share without any errors.
Any insight into resolving this issue would be appreciated.HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?kbid=555128
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Richard Cote" <RichardCote@.discussions.microsoft.com> wrote in message
news:3BA4F72D-E6E3-434A-BDE1-95BC990A3B66@.microsoft.com...
>I am having an odd failure when backing up my SQL 2000 SP3 server to a
> network share. I receive the following error:
> BackupDiskFile::CreateMedia: Backup device '\\server\share\master.BAK'
> failed to create. Operating system error = 5(Access is denied.).
> However, the following T-SQL command does run and create the appropriate
> file in the same network folder:
> EXEC xp_cmdshell 'dir \\server\share > \\server\share\test.txt'
> Both the SQL Server and SQL Server Agent is running under a domain user
> account which has the required permissions to this share. Other SQL
> Servers
> (SP3 and SP4) which also run under the same domain user account are
> backing
> up to the same share without any errors.
> Any insight into resolving this issue would be appreciated.
>|||The maintenance plan is properly configured to backup to the UNC name - in
the exact same manner as all the other servers that are working properly.
"Geoff N. Hiten" wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?kbid=555128
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Richard Cote" <RichardCote@.discussions.microsoft.com> wrote in message
> news:3BA4F72D-E6E3-434A-BDE1-95BC990A3B66@.microsoft.com...
> >I am having an odd failure when backing up my SQL 2000 SP3 server to a
> > network share. I receive the following error:
> >
> > BackupDiskFile::CreateMedia: Backup device '\\server\share\master.BAK'
> > failed to create. Operating system error = 5(Access is denied.).
> >
> > However, the following T-SQL command does run and create the appropriate
> > file in the same network folder:
> >
> > EXEC xp_cmdshell 'dir \\server\share > \\server\share\test.txt'
> >
> > Both the SQL Server and SQL Server Agent is running under a domain user
> > account which has the required permissions to this share. Other SQL
> > Servers
> > (SP3 and SP4) which also run under the same domain user account are
> > backing
> > up to the same share without any errors.
> >
> > Any insight into resolving this issue would be appreciated.
> >
>|||I have found in those cases that it is usually either a name resolution
issue or a permissions issue.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Richard Cote" <RichardCote@.discussions.microsoft.com> wrote in message
news:53C105CD-2656-4A02-A708-4E6C43F4077F@.microsoft.com...
> The maintenance plan is properly configured to backup to the UNC name - in
> the exact same manner as all the other servers that are working properly.
> "Geoff N. Hiten" wrote:
>> HowTo: Backup to UNC name using Database Maintenance Wizard
>> http://support.microsoft.com/?kbid=555128
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>> "Richard Cote" <RichardCote@.discussions.microsoft.com> wrote in message
>> news:3BA4F72D-E6E3-434A-BDE1-95BC990A3B66@.microsoft.com...
>> >I am having an odd failure when backing up my SQL 2000 SP3 server to a
>> > network share. I receive the following error:
>> >
>> > BackupDiskFile::CreateMedia: Backup device '\\server\share\master.BAK'
>> > failed to create. Operating system error = 5(Access is denied.).
>> >
>> > However, the following T-SQL command does run and create the
>> > appropriate
>> > file in the same network folder:
>> >
>> > EXEC xp_cmdshell 'dir \\server\share > \\server\share\test.txt'
>> >
>> > Both the SQL Server and SQL Server Agent is running under a domain user
>> > account which has the required permissions to this share. Other SQL
>> > Servers
>> > (SP3 and SP4) which also run under the same domain user account are
>> > backing
>> > up to the same share without any errors.
>> >
>> > Any insight into resolving this issue would be appreciated.
>> >
>>|||Login using the SQLAgent Login and Try the same "EXEC xp_cmdshell 'dir
\\server\share > \\server\share\test.txt' "
On Apr 10, 4:16 pm, Richard Cote
<RichardC...@.discussions.microsoft.com> wrote:
> The maintenance plan is properly configured to backup to the UNC name - in
> the exact same manner as all the other servers that are working properly.
>
> "Geoff N. Hiten" wrote:
> > HowTo: Backup to UNC name using Database Maintenance Wizard
> >http://support.microsoft.com/?kbid=555128
> > --
> > Geoff N. Hiten
> > Senior Database Administrator
> > Microsoft SQL Server MVP
> > "Richard Cote" <RichardC...@.discussions.microsoft.com> wrote in message
> >news:3BA4F72D-E6E3-434A-BDE1-95BC990A3B66@.microsoft.com...
> > >I am having an odd failure when backing up my SQL 2000 SP3 server to a
> > > network share. I receive the following error:
> > > BackupDiskFile::CreateMedia: Backup device '\\server\share\master.BAK'
> > > failed to create. Operating system error = 5(Access is denied.).
> > > However, the following T-SQL command does run and create the appropriate
> > > file in the same network folder:
> > > EXEC xp_cmdshell 'dir \\server\share > \\server\share\test.txt'
> > > Both the SQL Server and SQL Server Agent is running under a domain user
> > > account which has the required permissions to this share. Other SQL
> > > Servers
> > > (SP3 and SP4) which also run under the same domain user account are
> > > backing
> > > up to the same share without any errors.
> > > Any insight into resolving this issue would be appreciated.- Hide quoted text -
> - Show quoted text -|||The xp_cmdshell command works for any sysadmin user and the SQL Server and
SQL Server Agent logins. However, backups still fail to the same network
share.
This problem seems to be isolated to this one server, and is very
perplexing. Turning on auditing on the file share does not reveal any audit
failures. Choosing a different share with full file and share permissions
granted to Everyone also results in the same access denied error.
"schal" wrote:
> Login using the SQLAgent Login and Try the same "EXEC xp_cmdshell 'dir
> \\server\share > \\server\share\test.txt' "
>
> On Apr 10, 4:16 pm, Richard Cote
> <RichardC...@.discussions.microsoft.com> wrote:
> > The maintenance plan is properly configured to backup to the UNC name - in
> > the exact same manner as all the other servers that are working properly.
> >
> >
> >
> > "Geoff N. Hiten" wrote:
> > > HowTo: Backup to UNC name using Database Maintenance Wizard
> > >http://support.microsoft.com/?kbid=555128
> >
> > > --
> > > Geoff N. Hiten
> > > Senior Database Administrator
> > > Microsoft SQL Server MVP
> >
> > > "Richard Cote" <RichardC...@.discussions.microsoft.com> wrote in message
> > >news:3BA4F72D-E6E3-434A-BDE1-95BC990A3B66@.microsoft.com...
> > > >I am having an odd failure when backing up my SQL 2000 SP3 server to a
> > > > network share. I receive the following error:
> >
> > > > BackupDiskFile::CreateMedia: Backup device '\\server\share\master.BAK'
> > > > failed to create. Operating system error = 5(Access is denied.).
> >
> > > > However, the following T-SQL command does run and create the appropriate
> > > > file in the same network folder:
> >
> > > > EXEC xp_cmdshell 'dir \\server\share > \\server\share\test.txt'
> >
> > > > Both the SQL Server and SQL Server Agent is running under a domain user
> > > > account which has the required permissions to this share. Other SQL
> > > > Servers
> > > > (SP3 and SP4) which also run under the same domain user account are
> > > > backing
> > > > up to the same share without any errors.
> >
> > > > Any insight into resolving this issue would be appreciated.- Hide quoted text -
> >
> > - Show quoted text -
>
>

Backups to network share fail

I am having an odd failure when backing up my SQL 2000 SP3 server to a
network share. I receive the following error:
BackupDiskFile::CreateMedia: Backup device '\\server\share\master.BAK'
failed to create. Operating system error = 5(Access is denied.).
However, the following T-SQL command does run and create the appropriate
file in the same network folder:
EXEC xp_cmdshell 'dir \\server\share > \\server\share\test.txt'
Both the SQL Server and SQL Server Agent is running under a domain user
account which has the required permissions to this share. Other SQL Servers
(SP3 and SP4) which also run under the same domain user account are backing
up to the same share without any errors.
Any insight into resolving this issue would be appreciated.
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?kbid=555128
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Richard Cote" <RichardCote@.discussions.microsoft.com> wrote in message
news:3BA4F72D-E6E3-434A-BDE1-95BC990A3B66@.microsoft.com...
>I am having an odd failure when backing up my SQL 2000 SP3 server to a
> network share. I receive the following error:
> BackupDiskFile::CreateMedia: Backup device '\\server\share\master.BAK'
> failed to create. Operating system error = 5(Access is denied.).
> However, the following T-SQL command does run and create the appropriate
> file in the same network folder:
> EXEC xp_cmdshell 'dir \\server\share > \\server\share\test.txt'
> Both the SQL Server and SQL Server Agent is running under a domain user
> account which has the required permissions to this share. Other SQL
> Servers
> (SP3 and SP4) which also run under the same domain user account are
> backing
> up to the same share without any errors.
> Any insight into resolving this issue would be appreciated.
>
|||The maintenance plan is properly configured to backup to the UNC name - in
the exact same manner as all the other servers that are working properly.
"Geoff N. Hiten" wrote:

> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?kbid=555128
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Richard Cote" <RichardCote@.discussions.microsoft.com> wrote in message
> news:3BA4F72D-E6E3-434A-BDE1-95BC990A3B66@.microsoft.com...
>
|||I have found in those cases that it is usually either a name resolution
issue or a permissions issue.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Richard Cote" <RichardCote@.discussions.microsoft.com> wrote in message
news:53C105CD-2656-4A02-A708-4E6C43F4077F@.microsoft.com...[vbcol=seagreen]
> The maintenance plan is properly configured to backup to the UNC name - in
> the exact same manner as all the other servers that are working properly.
> "Geoff N. Hiten" wrote:
|||Login using the SQLAgent Login and Try the same "EXEC xp_cmdshell 'dir
\\server\share > \\server\share\test.txt' "
On Apr 10, 4:16 pm, Richard Cote
<RichardC...@.discussions.microsoft.com> wrote:
> The maintenance plan is properly configured to backup to the UNC name - in
> the exact same manner as all the other servers that are working properly.
>
> "Geoff N. Hiten" wrote:
>
>
>
>
> - Show quoted text -
|||The xp_cmdshell command works for any sysadmin user and the SQL Server and
SQL Server Agent logins. However, backups still fail to the same network
share.
This problem seems to be isolated to this one server, and is very
perplexing. Turning on auditing on the file share does not reveal any audit
failures. Choosing a different share with full file and share permissions
granted to Everyone also results in the same access denied error.
"schal" wrote:

> Login using the SQLAgent Login and Try the same "EXEC xp_cmdshell 'dir
> \\server\share > \\server\share\test.txt' "
>
> On Apr 10, 4:16 pm, Richard Cote
> <RichardC...@.discussions.microsoft.com> wrote:
>
>

Backups to network share fail

I am having an odd failure when backing up my SQL 2000 SP3 server to a
network share. I receive the following error:
BackupDiskFile::CreateMedia: Backup device '\\server\share\master.BAK'
failed to create. Operating system error = 5(Access is denied.).
However, the following T-SQL command does run and create the appropriate
file in the same network folder:
EXEC xp_cmdshell 'dir \\server\share > \\server\share\test.txt'
Both the SQL Server and SQL Server Agent is running under a domain user
account which has the required permissions to this share. Other SQL Servers
(SP3 and SP4) which also run under the same domain user account are backing
up to the same share without any errors.
Any insight into resolving this issue would be appreciated.HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?kbid=555128
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Richard Cote" <RichardCote@.discussions.microsoft.com> wrote in message
news:3BA4F72D-E6E3-434A-BDE1-95BC990A3B66@.microsoft.com...
>I am having an odd failure when backing up my SQL 2000 SP3 server to a
> network share. I receive the following error:
> BackupDiskFile::CreateMedia: Backup device '\\server\share\master.BAK'
> failed to create. Operating system error = 5(Access is denied.).
> However, the following T-SQL command does run and create the appropriate
> file in the same network folder:
> EXEC xp_cmdshell 'dir \\server\share > \\server\share\test.txt'
> Both the SQL Server and SQL Server Agent is running under a domain user
> account which has the required permissions to this share. Other SQL
> Servers
> (SP3 and SP4) which also run under the same domain user account are
> backing
> up to the same share without any errors.
> Any insight into resolving this issue would be appreciated.
>|||The maintenance plan is properly configured to backup to the UNC name - in
the exact same manner as all the other servers that are working properly.
"Geoff N. Hiten" wrote:

> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?kbid=555128
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Richard Cote" <RichardCote@.discussions.microsoft.com> wrote in message
> news:3BA4F72D-E6E3-434A-BDE1-95BC990A3B66@.microsoft.com...
>|||I have found in those cases that it is usually either a name resolution
issue or a permissions issue.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Richard Cote" <RichardCote@.discussions.microsoft.com> wrote in message
news:53C105CD-2656-4A02-A708-4E6C43F4077F@.microsoft.com...[vbcol=seagreen]
> The maintenance plan is properly configured to backup to the UNC name - in
> the exact same manner as all the other servers that are working properly.
> "Geoff N. Hiten" wrote:
>|||Login using the SQLAgent Login and Try the same "EXEC xp_cmdshell 'dir
\\server\share > \\server\share\test.txt' "
On Apr 10, 4:16 pm, Richard Cote
<RichardC...@.discussions.microsoft.com> wrote:
> The maintenance plan is properly configured to backup to the UNC name - in
> the exact same manner as all the other servers that are working properly.
>
> "Geoff N. Hiten" wrote:
>
>
>
>
>
>
>
> - Show quoted text -|||The xp_cmdshell command works for any sysadmin user and the SQL Server and
SQL Server Agent logins. However, backups still fail to the same network
share.
This problem seems to be isolated to this one server, and is very
perplexing. Turning on auditing on the file share does not reveal any audit
failures. Choosing a different share with full file and share permissions
granted to Everyone also results in the same access denied error.
"schal" wrote:

> Login using the SQLAgent Login and Try the same "EXEC xp_cmdshell 'dir
> \\server\share > \\server\share\test.txt' "
>
> On Apr 10, 4:16 pm, Richard Cote
> <RichardC...@.discussions.microsoft.com> wrote:
>
>

Wednesday, March 7, 2012

Backups keep failing?

I used the database maintenance wizard and choose most of the defaults.
Every night my backups fail because of the step to check data indexes and
repair any minor problems. The error I receive is [Microsoft][ODBC SQL
Server Driver][SQL Server]Repair statement not processed. Database needs to
be in single user mode. Does anyone know why this happeneds?
Thanks,
DanSee this page -
http://support.microsoft.com/default.aspx?scid=kb;en-us;290622
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Dan Marth" <danmarth@.earthlink.net> wrote in message
news:ux0ir6v2DHA.2408@.tk2msftngp13.phx.gbl...
> I used the database maintenance wizard and choose most of the defaults.
> Every night my backups fail because of the step to check data indexes and
> repair any minor problems. The error I receive is [Microsoft][ODBC SQL
> Server Driver][SQL Server]Repair statement not processed. Database needs
to
> be in single user mode. Does anyone know why this happeneds?
> Thanks,
> Dan
>|||Thanks, that seemed to clear things up!
"Ray Higdon" <sqlhigdon@.nospam.yahoo.com> wrote in message
news:OTvHYUw2DHA.3196@.TK2MSFTNGP11.phx.gbl...
> See this page -
> http://support.microsoft.com/default.aspx?scid=kb;en-us;290622
> HTH
> --
> Ray Higdon MCSE, MCDBA, CCNA
> --
> "Dan Marth" <danmarth@.earthlink.net> wrote in message
> news:ux0ir6v2DHA.2408@.tk2msftngp13.phx.gbl...
> > I used the database maintenance wizard and choose most of the defaults.
> > Every night my backups fail because of the step to check data indexes
and
> > repair any minor problems. The error I receive is [Microsoft][ODBC SQL
> > Server Driver][SQL Server]Repair statement not processed. Database needs
> to
> > be in single user mode. Does anyone know why this happeneds?
> >
> > Thanks,
> > Dan
> >
> >
>

Backups keep failing?

I used the database maintenance wizard and choose most of the defaults.
Every night my backups fail because of the step to check data indexes and
repair any minor problems. The error I receive is [Microsoft][ODBC SQL
Server Driver][SQL Server]Repair statement not processed. Database needs to
be in single user mode. Does anyone know why this happeneds?
Thanks,
DanSee this page -
http://support.microsoft.com/defaul...kb;en-us;290622
HTH
Ray Higdon MCSE, MCDBA, CCNA
--
"Dan Marth" <danmarth@.earthlink.net> wrote in message
news:ux0ir6v2DHA.2408@.tk2msftngp13.phx.gbl...
quote:

> I used the database maintenance wizard and choose most of the defaults.
> Every night my backups fail because of the step to check data indexes and
> repair any minor problems. The error I receive is [Microsoft][ODBC SQL
> Server Driver][SQL Server]Repair statement not processed. Database needs

to
quote:

> be in single user mode. Does anyone know why this happeneds?
> Thanks,
> Dan
>
|||Thanks, that seemed to clear things up!
"Ray Higdon" <sqlhigdon@.nospam.yahoo.com> wrote in message
news:OTvHYUw2DHA.3196@.TK2MSFTNGP11.phx.gbl...
quote:

> See this page -
> http://support.microsoft.com/defaul...kb;en-us;290622
> HTH
> --
> Ray Higdon MCSE, MCDBA, CCNA
> --
> "Dan Marth" <danmarth@.earthlink.net> wrote in message
> news:ux0ir6v2DHA.2408@.tk2msftngp13.phx.gbl...
and[QUOTE]
> to
>

Sunday, February 12, 2012

backup transaction log fail

'QDB Backup Maintenace'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070:
[Microsoft][ODBC SQL Server Driver][SQL Server]Database
state cannot be changed while other users are using the
database 'QDB'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER
DATABASE statement failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption
command failed.
[1] Database QDB: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919:
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not processed. Database needs to be in single
user mode.
I can do complete backup and integrity success in the plan
but the transaciton log backup and check data and index
link keep failing. Please help
Thanks
Steve
If you had not guessed/determined the problem, this error points to the =
issue:
Database state cannot be changed while other users are using the =
database 'QDB'
Are you using a maintenance plan to do whatever it is that you are =
trying to do? Maintenance plans can help, but they are also a pain =
because you have to know what each checkbox does and how all the options =
work together. It has been my experience that maintenance plans do not =
always work as expected. Because of this I use jobs that I create and =
schedule as needed. =20
Are you backing up your transaction log during the day, or only at night =
as part of the maintenance plan? If you are only backing it up during =
the night (when avtivity is low) and not during the day (when =
transaction activity is high) you are not really protecting yourself =
from a failure. You should look into a "proper" backup plan ASAP! =20
I would recommend performing the transaction log backup(s) as often as =
necessary within a separate job that you can schedule to run as often as =
you want during the day.
You can then put some DBCC statements (such as CHECKDB, CHECKCATALOG, =
UPDATEUSAGE) into a separate job that you can schedule for some time =
when activity on the server is low.
--=20
Keith
"Steve C." <anonymous@.discussions.microsoft.com> wrote in message =
news:22d501c44fd1$cf818e70$3501280a@.phx.gbl...
> 'QDB Backup Maintenace'=20
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070:=20
> [Microsoft][ODBC SQL Server Driver][SQL Server]Database=20
> state cannot be changed while other users are using the=20
> database 'QDB'
> [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER=20
> DATABASE statement failed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption=20
> command failed.
> [1] Database QDB: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919:=20
> [Microsoft][ODBC SQL Server Driver][SQL Server]Repair=20
> statement not processed. Database needs to be in single=20
> user mode.
>=20
> I can do complete backup and integrity success in the plan=20
> but the transaciton log backup and check data and index=20
> link keep failing. Please help=20
>=20
> Thanks
>=20
> Steve

backup transaction log fail

'QDB Backup Maintenace'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070:
[Microsoft][ODBC SQL Server Driver][SQL Server]Database
state cannot be changed while other users are using the
database 'QDB'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER
DATABASE statement failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption
command failed.
[1] Database QDB: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919:
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not processed. Database needs to be in single
user mode.
I can do complete backup and integrity success in the plan
but the transaciton log backup and check data and index
link keep failing. Please help
Thanks
SteveIf you had not guessed/determined the problem, this error points to the =
issue:
Database state cannot be changed while other users are using the =
database 'QDB'
Are you using a maintenance plan to do whatever it is that you are =
trying to do? Maintenance plans can help, but they are also a pain =
because you have to know what each checkbox does and how all the options =
work together. It has been my experience that maintenance plans do not =
always work as expected. Because of this I use jobs that I create and =
schedule as needed. =20
Are you backing up your transaction log during the day, or only at night =
as part of the maintenance plan? If you are only backing it up during =
the night (when avtivity is low) and not during the day (when =
transaction activity is high) you are not really protecting yourself =
from a failure. You should look into a "proper" backup plan ASAP! =20
I would recommend performing the transaction log backup(s) as often as =
necessary within a separate job that you can schedule to run as often as =
you want during the day.
You can then put some DBCC statements (such as CHECKDB, CHECKCATALOG, =
UPDATEUSAGE) into a separate job that you can schedule for some time =
when activity on the server is low.
--=20
Keith
"Steve C." <anonymous@.discussions.microsoft.com> wrote in message =
news:22d501c44fd1$cf818e70$3501280a@.phx.gbl...
> 'QDB Backup Maintenace'=20
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070:=20
> [Microsoft][ODBC SQL Server Driver][SQL Server]Database=20
> state cannot be changed while other users are using the=20
> database 'QDB'
> [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER=20
> DATABASE statement failed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption=20
> command failed.
> [1] Database QDB: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919:=20
> [Microsoft][ODBC SQL Server Driver][SQL Server]Repair=20
> statement not processed. Database needs to be in single=20
> user mode.
>=20
> I can do complete backup and integrity success in the plan=20
> but the transaciton log backup and check data and index=20
> link keep failing. Please help=20
>=20
> Thanks
>=20
> Steve

backup transaction log fail

'QDB Backup Maintenace'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070:
[Microsoft][ODBC SQL Server Driver][SQL Server]Database
state cannot be changed while other users are using the
database 'QDB'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER
DATABASE statement failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption
command failed.
[1] Database QDB: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919:
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not processed. Database needs to be in single
user mode.
I can do complete backup and integrity success in the plan
but the transaciton log backup and check data and index
link keep failing. Please help
Thanks
SteveIf you had not guessed/determined the problem, this error points to the =issue:
Database state cannot be changed while other users are using the =database 'QDB'
Are you using a maintenance plan to do whatever it is that you are =trying to do? Maintenance plans can help, but they are also a pain =because you have to know what each checkbox does and how all the options =work together. It has been my experience that maintenance plans do not =always work as expected. Because of this I use jobs that I create and =schedule as needed.
Are you backing up your transaction log during the day, or only at night =as part of the maintenance plan? If you are only backing it up during =the night (when avtivity is low) and not during the day (when =transaction activity is high) you are not really protecting yourself =from a failure. You should look into a "proper" backup plan ASAP!
I would recommend performing the transaction log backup(s) as often as =necessary within a separate job that you can schedule to run as often as =you want during the day.
You can then put some DBCC statements (such as CHECKDB, CHECKCATALOG, =UPDATEUSAGE) into a separate job that you can schedule for some time =when activity on the server is low.
-- Keith
"Steve C." <anonymous@.discussions.microsoft.com> wrote in message =news:22d501c44fd1$cf818e70$3501280a@.phx.gbl...
> 'QDB Backup Maintenace' > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070: > [Microsoft][ODBC SQL Server Driver][SQL Server]Database > state cannot be changed while other users are using the > database 'QDB'
> [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER > DATABASE statement failed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption > command failed.
> [1] Database QDB: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: > [Microsoft][ODBC SQL Server Driver][SQL Server]Repair > statement not processed. Database needs to be in single > user mode.
> > I can do complete backup and integrity success in the plan > but the transaciton log backup and check data and index > link keep failing. Please help > > Thanks
> > Steve