Please Help : SQLServerAgent cannot start

Hi, All,
We got power failure at last midnight, SQL server 7.0
rebooted after that but "SQLServerAgent cannot start
because the msdb database is not available for normal
access." I can see and access the MSDB database, also
DBCC CHECKDB is ok. Form the log file, I know when the
SQL server was rebooted but it cannot tell when we got
power failure. It may be the time during Jobs to run to
backup the database and failed because of power failure.
I try to reboot server this morning and got same error
message.
Here is part of the info in the log file at the first
reboot after power failure.
******
195 transactions rolled forward in database 'msdb' (4).
0 transactions rolled back in database 'msdb' (4).
Recovery complete.
*******
So, What should I do to fix it? Any suggestions?
Thanks and have a good one
ahwak
Hi,
Could you please check whethere the UserAccess for MSDB is set to
RESTRICTED_USER.
sp_helpdb msdb
see the status colun of the output. If it is RESTRICTED_USER then use the
below command
ALTER DATABASE msdb set MULTI_USER
After that try restarting SQLAGENT service
Thanks
Hari
MCDBA
"ahwak" <abchawk@.hotmail.com> wrote in message
news:6edd01c4839c$c72f9e20$a401280a@.phx.gbl...
> Hi, All,
> We got power failure at last midnight, SQL server 7.0
> rebooted after that but "SQLServerAgent cannot start
> because the msdb database is not available for normal
> access." I can see and access the MSDB database, also
> DBCC CHECKDB is ok. Form the log file, I know when the
> SQL server was rebooted but it cannot tell when we got
> power failure. It may be the time during Jobs to run to
> backup the database and failed because of power failure.
> I try to reboot server this morning and got same error
> message.
> Here is part of the info in the log file at the first
> reboot after power failure.
> ******
> 195 transactions rolled forward in database 'msdb' (4).
> 0 transactions rolled back in database 'msdb' (4).
> Recovery complete.
> *******
> So, What should I do to fix it? Any suggestions?
> Thanks and have a good one
> ahwak
|||Hi,Hari
Our SQL server is 7.0 sp3 on Win2000 server. when i run
sp_helpdb msdb, I get status output is 'trunc. log on
chkpt., dbo use only' and when I try to run 'ALTER
DATABASE msdb set MULTI_USER', I get a syntax error.
should I use sp_dboption to change the status?
Thanks
ahawk

>--Original Message--
>Hi,
>Could you please check whethere the UserAccess for MSDB
is set to
>RESTRICTED_USER.
>sp_helpdb msdb
>see the status colun of the output. If it is
RESTRICTED_USER then use the
>below command
>ALTER DATABASE msdb set MULTI_USER
>After that try restarting SQLAGENT service
>Thanks
>Hari
>MCDBA
>
|||Is it possible that the SQL Server Agent startup account has lost it
permissions to the MSdB database?
As a test set SQL Server Agnet to start using the SQL Server service
account and see if that resolves the problem. You can also try the SYSTEM
account as well.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Hi,
ALTER database command is not supported in SQL 7.
The error is because the access is set to DBO user only... Run the below to
statment to make the access to normal mode for MSDB.
sp_dboption 'msdb','dbo use only',false
After execution , Start the SQL agent service
Thanks
Hari
MCDBA
"ahawk" <anonymous@.discussions.microsoft.com> wrote in message
news:6a2a01c483a3$f6e90230$a301280a@.phx.gbl...
> Hi,Hari
> Our SQL server is 7.0 sp3 on Win2000 server. when i run
> sp_helpdb msdb, I get status output is 'trunc. log on
> chkpt., dbo use only' and when I try to run 'ALTER
> DATABASE msdb set MULTI_USER', I get a syntax error.
> should I use sp_dboption to change the status?
> Thanks
> ahawk
> is set to
> RESTRICTED_USER then use the
>
|||Thanks, Hari,
After I remove 'DBO use only', I restart SQL agent, i got
new error message 'Password verification of
the 'SQLAgentCmdExec' proxy account failed (reason: A
required privilege is not held by the client). but good
news is SQL agent restarted!
I use the domain admin as logon info for both SQL server
and agent. also, domain admin has the dbo right. I don't
know why it works after i changed it (it worked fine
before). even it get the error message, at least sql
agent is restart now.
thanks alot and best wishes
ahawk

>--Original Message--
>Hi,
>ALTER database command is not supported in SQL 7.
>The error is because the access is set to DBO user
only... Run the below to
>statment to make the access to normal mode for MSDB.
>sp_dboption 'msdb','dbo use only',false
>After execution , Start the SQL agent service
>Thanks
>Hari
>MCDBA
>
>

Please Help : SQLServerAgent cannot start

Hi, All,
We got power failure at last midnight, SQL server 7.0
rebooted after that but "SQLServerAgent cannot start
because the msdb database is not available for normal
access." I can see and access the MSDB database, also
DBCC CHECKDB is ok. Form the log file, I know when the
SQL server was rebooted but it cannot tell when we got
power failure. It may be the time during Jobs to run to
backup the database and failed because of power failure.
I try to reboot server this morning and got same error
message.
Here is part of the info in the log file at the first
reboot after power failure.
******
195 transactions rolled forward in database 'msdb' (4).
0 transactions rolled back in database 'msdb' (4).
Recovery complete.
*******
So, What should I do to fix it? Any suggestions?
Thanks and have a good one
ahwakHi,
Could you please check whethere the UserAccess for MSDB is set to
RESTRICTED_USER.
sp_helpdb msdb
see the status colun of the output. If it is RESTRICTED_USER then use the
below command
ALTER DATABASE msdb set MULTI_USER
After that try restarting SQLAGENT service
Thanks
Hari
MCDBA
"ahwak" <abchawk@.hotmail.com> wrote in message
news:6edd01c4839c$c72f9e20$a401280a@.phx.gbl...
> Hi, All,
> We got power failure at last midnight, SQL server 7.0
> rebooted after that but "SQLServerAgent cannot start
> because the msdb database is not available for normal
> access." I can see and access the MSDB database, also
> DBCC CHECKDB is ok. Form the log file, I know when the
> SQL server was rebooted but it cannot tell when we got
> power failure. It may be the time during Jobs to run to
> backup the database and failed because of power failure.
> I try to reboot server this morning and got same error
> message.
> Here is part of the info in the log file at the first
> reboot after power failure.
> ******
> 195 transactions rolled forward in database 'msdb' (4).
> 0 transactions rolled back in database 'msdb' (4).
> Recovery complete.
> *******
> So, What should I do to fix it? Any suggestions?
> Thanks and have a good one
> ahwak|||Hi,Hari
Our SQL server is 7.0 sp3 on Win2000 server. when i run
sp_helpdb msdb, I get status output is 'trunc. log on
chkpt., dbo use only' and when I try to run 'ALTER
DATABASE msdb set MULTI_USER', I get a syntax error.
should I use sp_dboption to change the status?
Thanks
ahawk
>--Original Message--
>Hi,
>Could you please check whethere the UserAccess for MSDB
is set to
>RESTRICTED_USER.
>sp_helpdb msdb
>see the status colun of the output. If it is
RESTRICTED_USER then use the
>below command
>ALTER DATABASE msdb set MULTI_USER
>After that try restarting SQLAGENT service
>Thanks
>Hari
>MCDBA
>|||Is it possible that the SQL Server Agent startup account has lost it
permissions to the MSdB database?
As a test set SQL Server Agnet to start using the SQL Server service
account and see if that resolves the problem. You can also try the SYSTEM
account as well.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hi,
ALTER database command is not supported in SQL 7.
The error is because the access is set to DBO user only... Run the below to
statment to make the access to normal mode for MSDB.
sp_dboption 'msdb','dbo use only',false
After execution , Start the SQL agent service
Thanks
Hari
MCDBA
"ahawk" <anonymous@.discussions.microsoft.com> wrote in message
news:6a2a01c483a3$f6e90230$a301280a@.phx.gbl...
> Hi,Hari
> Our SQL server is 7.0 sp3 on Win2000 server. when i run
> sp_helpdb msdb, I get status output is 'trunc. log on
> chkpt., dbo use only' and when I try to run 'ALTER
> DATABASE msdb set MULTI_USER', I get a syntax error.
> should I use sp_dboption to change the status?
> Thanks
> ahawk
> >--Original Message--
> >Hi,
> >
> >Could you please check whethere the UserAccess for MSDB
> is set to
> >RESTRICTED_USER.
> >
> >sp_helpdb msdb
> >
> >see the status colun of the output. If it is
> RESTRICTED_USER then use the
> >below command
> >
> >ALTER DATABASE msdb set MULTI_USER
> >
> >After that try restarting SQLAGENT service
> >
> >Thanks
> >Hari
> >MCDBA
> >
>|||Thanks, Hari,
After I remove 'DBO use only', I restart SQL agent, i got
new error message 'Password verification of
the 'SQLAgentCmdExec' proxy account failed (reason: A
required privilege is not held by the client). but good
news is SQL agent restarted!
I use the domain admin as logon info for both SQL server
and agent. also, domain admin has the dbo right. I don't
know why it works after i changed it (it worked fine
before). even it get the error message, at least sql
agent is restart now.
thanks alot and best wishes
ahawk
>--Original Message--
>Hi,
>ALTER database command is not supported in SQL 7.
>The error is because the access is set to DBO user
only... Run the below to
>statment to make the access to normal mode for MSDB.
>sp_dboption 'msdb','dbo use only',false
>After execution , Start the SQL agent service
>Thanks
>Hari
>MCDBA
>
>

Please Help : SQLServerAgent cannot start

Hi, All,
We got power failure at last midnight, SQL server 7.0
rebooted after that but "SQLServerAgent cannot start
because the msdb database is not available for normal
access." I can see and access the MSDB database, also
DBCC CHECKDB is ok. Form the log file, I know when the
SQL server was rebooted but it cannot tell when we got
power failure. It may be the time during Jobs to run to
backup the database and failed because of power failure.
I try to reboot server this morning and got same error
message.
Here is part of the info in the log file at the first
reboot after power failure.
******
195 transactions rolled forward in database 'msdb' (4).
0 transactions rolled back in database 'msdb' (4).
Recovery complete.
*******
So, What should I do to fix it? Any suggestions?
Thanks and have a good one
ahwakHi,
Could you please check whethere the UserAccess for MSDB is set to
RESTRICTED_USER.
sp_helpdb msdb
see the status colun of the output. If it is RESTRICTED_USER then use the
below command
ALTER DATABASE msdb set MULTI_USER
After that try restarting SQLAGENT service
Thanks
Hari
MCDBA
"ahwak" <abchawk@.hotmail.com> wrote in message
news:6edd01c4839c$c72f9e20$a401280a@.phx.gbl...
> Hi, All,
> We got power failure at last midnight, SQL server 7.0
> rebooted after that but "SQLServerAgent cannot start
> because the msdb database is not available for normal
> access." I can see and access the MSDB database, also
> DBCC CHECKDB is ok. Form the log file, I know when the
> SQL server was rebooted but it cannot tell when we got
> power failure. It may be the time during Jobs to run to
> backup the database and failed because of power failure.
> I try to reboot server this morning and got same error
> message.
> Here is part of the info in the log file at the first
> reboot after power failure.
> ******
> 195 transactions rolled forward in database 'msdb' (4).
> 0 transactions rolled back in database 'msdb' (4).
> Recovery complete.
> *******
> So, What should I do to fix it? Any suggestions?
> Thanks and have a good one
> ahwak|||Hi,Hari
Our SQL server is 7.0 sp3 on Win2000 server. when i run
sp_helpdb msdb, I get status output is 'trunc. log on
chkpt., dbo use only' and when I try to run 'ALTER
DATABASE msdb set MULTI_USER', I get a syntax error.
should I use sp_dboption to change the status?
Thanks
ahawk

>--Original Message--
>Hi,
>Could you please check whethere the UserAccess for MSDB
is set to
>RESTRICTED_USER.
>sp_helpdb msdb
>see the status colun of the output. If it is
RESTRICTED_USER then use the
>below command
>ALTER DATABASE msdb set MULTI_USER
>After that try restarting SQLAGENT service
>Thanks
>Hari
>MCDBA
>|||Is it possible that the SQL Server Agent startup account has lost it
permissions to the MSdB database?
As a test set SQL Server Agnet to start using the SQL Server service
account and see if that resolves the problem. You can also try the SYSTEM
account as well.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hi,
ALTER database command is not supported in SQL 7.
The error is because the access is set to DBO user only... Run the below to
statment to make the access to normal mode for MSDB.
sp_dboption 'msdb','dbo use only',false
After execution , Start the SQL agent service
Thanks
Hari
MCDBA
"ahawk" <anonymous@.discussions.microsoft.com> wrote in message
news:6a2a01c483a3$f6e90230$a301280a@.phx.gbl...
> Hi,Hari
> Our SQL server is 7.0 sp3 on Win2000 server. when i run
> sp_helpdb msdb, I get status output is 'trunc. log on
> chkpt., dbo use only' and when I try to run 'ALTER
> DATABASE msdb set MULTI_USER', I get a syntax error.
> should I use sp_dboption to change the status?
> Thanks
> ahawk
>
> is set to
> RESTRICTED_USER then use the
>|||Thanks, Hari,
After I remove 'DBO use only', I restart SQL agent, i got
new error message 'Password verification of
the 'SQLAgentCmdExec' proxy account failed (reason: A
required privilege is not held by the client). but good
news is SQL agent restarted!
I use the domain admin as logon info for both SQL server
and agent. also, domain admin has the dbo right. I don't
know why it works after i changed it (it worked fine
before). even it get the error message, at least sql
agent is restart now.
thanks alot and best wishes
ahawk

>--Original Message--
>Hi,
>ALTER database command is not supported in SQL 7.
>The error is because the access is set to DBO user
only... Run the below to
>statment to make the access to normal mode for MSDB.
>sp_dboption 'msdb','dbo use only',false
>After execution , Start the SQL agent service
>Thanks
>Hari
>MCDBA
>
>

Please advise re. restoring master/msdb on different server

I'm sure restoring master/msdb on the same server should
be no issue. But restoring on separate hardware might
have these issues (if you know others please tell me):
1: File path (drive letter, file path) different for the
location of the database on the replacement server;
2: Security issues. The separate Windows installation is
sure to have different SID, and since SQL Server security
is tightly integrated with Windows security, what might be
broken, what will the restore take care of, and what needs
to be manually fixed up-and how? (BTW, our installation
uses mixed mode security)
Regarding issue 1: I have experienced that restoring over
an existing database causes the file locations to be
automatically fixed up by the restore, taking the file
locations from the database being overwritten rather than
the locations saved in the backup. Will this work for
master/msdb?
I don't know what to expect regarding issue #2.
Any help appreciated! Thanks!Hi
Try the following:
http://support.microsoft.com/defaul...kb;EN-US;224071
John
"Scott" <anonymous@.discussions.microsoft.com> wrote in message
news:094d01c3fd71$ab484d80$a601280a@.phx.gbl...
> I'm sure restoring master/msdb on the same server should
> be no issue. But restoring on separate hardware might
> have these issues (if you know others please tell me):
> 1: File path (drive letter, file path) different for the
> location of the database on the replacement server;
> 2: Security issues. The separate Windows installation is
> sure to have different SID, and since SQL Server security
> is tightly integrated with Windows security, what might be
> broken, what will the restore take care of, and what needs
> to be manually fixed up-and how? (BTW, our installation
> uses mixed mode security)
> Regarding issue 1: I have experienced that restoring over
> an existing database causes the file locations to be
> automatically fixed up by the restore, taking the file
> locations from the database being overwritten rather than
> the locations saved in the backup. Will this work for
> master/msdb?
> I don't know what to expect regarding issue #2.
> Any help appreciated! Thanks!
>|||OK, thank you, these seem to indicate my concerns were
right.
However, all the documentation you pointed me at seems to
assume the original databases are operational; they are
read, or even modified, by these procedures, and
transferred as operational databases.
I need procedures for FAILED systems, i.e., only the
backups are available, not the databases themselves.
Any more help, anyone?
Thanks!

>--Original Message--
>Hi
>Try the following:
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;224071
>John
>"Scott" <anonymous@.discussions.microsoft.com> wrote in
message
>news:094d01c3fd71$ab484d80$a601280a@.phx.gbl...
the
is
security
be
needs
over
than
>
>.
>|||Hi
I have never tried it, but if you can restore the database into another
database then you can get the files, so you can then follow the procedure.
John
<anonymous@.discussions.microsoft.com> wrote in message
news:357a01c3fd86$69962b40$a001280a@.phx.gbl...
> OK, thank you, these seem to indicate my concerns were
> right.
> However, all the documentation you pointed me at seems to
> assume the original databases are operational; they are
> read, or even modified, by these procedures, and
> transferred as operational databases.
> I need procedures for FAILED systems, i.e., only the
> backups are available, not the databases themselves.
> Any more help, anyone?
> Thanks!
>
>
> US;224071
> message
> the
> is
> security
> be
> needs
> over
> than|||!!!
Yeah, that sound right. Ahh, Friday. Sorry for my fuzzy
head. And THANKS for your response.
Don't know the real state of our failed server, so I don't
know if we'll really have to do this. If we DO, I'll
respond and let you know.
Thanks again!
--Scott

>--Original Message--
>Hi
>I have never tried it, but if you can restore the
database into another
>database then you can get the files, so you can then
follow the procedure.
>John
><anonymous@.discussions.microsoft.com> wrote in message
>news:357a01c3fd86$69962b40$a001280a@.phx.gbl...
to
should
might
me):
installation
might
installation
file
for
>
>.
>

Please advise re. restoring master/msdb on different server

I'm sure restoring master/msdb on the same server should
be no issue. But restoring on separate hardware might
have these issues (if you know others please tell me):
1: File path (drive letter, file path) different for the
location of the database on the replacement server;
2: Security issues. The separate Windows installation is
sure to have different SID, and since SQL Server security
is tightly integrated with Windows security, what might be
broken, what will the restore take care of, and what needs
to be manually fixed up-and how? (BTW, our installation
uses mixed mode security)
Regarding issue 1: I have experienced that restoring over
an existing database causes the file locations to be
automatically fixed up by the restore, taking the file
locations from the database being overwritten rather than
the locations saved in the backup. Will this work for
master/msdb?
I don't know what to expect regarding issue #2.
Any help appreciated! Thanks!Hi
Try the following:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;224071
John
"Scott" <anonymous@.discussions.microsoft.com> wrote in message
news:094d01c3fd71$ab484d80$a601280a@.phx.gbl...
> I'm sure restoring master/msdb on the same server should
> be no issue. But restoring on separate hardware might
> have these issues (if you know others please tell me):
> 1: File path (drive letter, file path) different for the
> location of the database on the replacement server;
> 2: Security issues. The separate Windows installation is
> sure to have different SID, and since SQL Server security
> is tightly integrated with Windows security, what might be
> broken, what will the restore take care of, and what needs
> to be manually fixed up-and how? (BTW, our installation
> uses mixed mode security)
> Regarding issue 1: I have experienced that restoring over
> an existing database causes the file locations to be
> automatically fixed up by the restore, taking the file
> locations from the database being overwritten rather than
> the locations saved in the backup. Will this work for
> master/msdb?
> I don't know what to expect regarding issue #2.
> Any help appreciated! Thanks!
>|||OK, thank you, these seem to indicate my concerns were
right.
However, all the documentation you pointed me at seems to
assume the original databases are operational; they are
read, or even modified, by these procedures, and
transferred as operational databases.
I need procedures for FAILED systems, i.e., only the
backups are available, not the databases themselves.
Any more help, anyone?
Thanks!
>--Original Message--
>Hi
>Try the following:
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;224071
>John
>"Scott" <anonymous@.discussions.microsoft.com> wrote in
message
>news:094d01c3fd71$ab484d80$a601280a@.phx.gbl...
>> I'm sure restoring master/msdb on the same server should
>> be no issue. But restoring on separate hardware might
>> have these issues (if you know others please tell me):
>> 1: File path (drive letter, file path) different for
the
>> location of the database on the replacement server;
>> 2: Security issues. The separate Windows installation
is
>> sure to have different SID, and since SQL Server
security
>> is tightly integrated with Windows security, what might
be
>> broken, what will the restore take care of, and what
needs
>> to be manually fixed up-and how? (BTW, our installation
>> uses mixed mode security)
>> Regarding issue 1: I have experienced that restoring
over
>> an existing database causes the file locations to be
>> automatically fixed up by the restore, taking the file
>> locations from the database being overwritten rather
than
>> the locations saved in the backup. Will this work for
>> master/msdb?
>> I don't know what to expect regarding issue #2.
>> Any help appreciated! Thanks!
>
>.
>|||Hi
I have never tried it, but if you can restore the database into another
database then you can get the files, so you can then follow the procedure.
John
<anonymous@.discussions.microsoft.com> wrote in message
news:357a01c3fd86$69962b40$a001280a@.phx.gbl...
> OK, thank you, these seem to indicate my concerns were
> right.
> However, all the documentation you pointed me at seems to
> assume the original databases are operational; they are
> read, or even modified, by these procedures, and
> transferred as operational databases.
> I need procedures for FAILED systems, i.e., only the
> backups are available, not the databases themselves.
> Any more help, anyone?
> Thanks!
>
> >--Original Message--
> >Hi
> >
> >Try the following:
> >http://support.microsoft.com/default.aspx?scid=kb;EN-
> US;224071
> >
> >John
> >
> >"Scott" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:094d01c3fd71$ab484d80$a601280a@.phx.gbl...
> >> I'm sure restoring master/msdb on the same server should
> >> be no issue. But restoring on separate hardware might
> >> have these issues (if you know others please tell me):
> >>
> >> 1: File path (drive letter, file path) different for
> the
> >> location of the database on the replacement server;
> >>
> >> 2: Security issues. The separate Windows installation
> is
> >> sure to have different SID, and since SQL Server
> security
> >> is tightly integrated with Windows security, what might
> be
> >> broken, what will the restore take care of, and what
> needs
> >> to be manually fixed up-and how? (BTW, our installation
> >> uses mixed mode security)
> >>
> >> Regarding issue 1: I have experienced that restoring
> over
> >> an existing database causes the file locations to be
> >> automatically fixed up by the restore, taking the file
> >> locations from the database being overwritten rather
> than
> >> the locations saved in the backup. Will this work for
> >> master/msdb?
> >>
> >> I don't know what to expect regarding issue #2.
> >>
> >> Any help appreciated! Thanks!
> >>
> >
> >
> >.
> >|||!!!
Yeah, that sound right. Ahh, Friday. Sorry for my fuzzy
head. And THANKS for your response.
Don't know the real state of our failed server, so I don't
know if we'll really have to do this. If we DO, I'll
respond and let you know.
Thanks again!
--Scott
>--Original Message--
>Hi
>I have never tried it, but if you can restore the
database into another
>database then you can get the files, so you can then
follow the procedure.
>John
><anonymous@.discussions.microsoft.com> wrote in message
>news:357a01c3fd86$69962b40$a001280a@.phx.gbl...
>> OK, thank you, these seem to indicate my concerns were
>> right.
>> However, all the documentation you pointed me at seems
to
>> assume the original databases are operational; they are
>> read, or even modified, by these procedures, and
>> transferred as operational databases.
>> I need procedures for FAILED systems, i.e., only the
>> backups are available, not the databases themselves.
>> Any more help, anyone?
>> Thanks!
>>
>> >--Original Message--
>> >Hi
>> >
>> >Try the following:
>> >http://support.microsoft.com/default.aspx?scid=kb;EN-
>> US;224071
>> >
>> >John
>> >
>> >"Scott" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> >news:094d01c3fd71$ab484d80$a601280a@.phx.gbl...
>> >> I'm sure restoring master/msdb on the same server
should
>> >> be no issue. But restoring on separate hardware
might
>> >> have these issues (if you know others please tell
me):
>> >>
>> >> 1: File path (drive letter, file path) different for
>> the
>> >> location of the database on the replacement server;
>> >>
>> >> 2: Security issues. The separate Windows
installation
>> is
>> >> sure to have different SID, and since SQL Server
>> security
>> >> is tightly integrated with Windows security, what
might
>> be
>> >> broken, what will the restore take care of, and what
>> needs
>> >> to be manually fixed up-and how? (BTW, our
installation
>> >> uses mixed mode security)
>> >>
>> >> Regarding issue 1: I have experienced that restoring
>> over
>> >> an existing database causes the file locations to be
>> >> automatically fixed up by the restore, taking the
file
>> >> locations from the database being overwritten rather
>> than
>> >> the locations saved in the backup. Will this work
for
>> >> master/msdb?
>> >>
>> >> I don't know what to expect regarding issue #2.
>> >>
>> >> Any help appreciated! Thanks!
>> >>
>> >
>> >
>> >.
>> >
>
>.
>

plan for box upgrade

sql2k sp3
Im going to be moving sql from one box to a newer one
with better hardware today. This is my plan:
Restore a backup of Master and MSDB onto the new box.
Detach and attach the user db's.
Ive used detach and attach but never in this scenario.
Does anyone see a problem with this?
TIA, ChrisYour plan is perfect, only thing is that the restored
master database will still have entries for user
databases, even if they don't exist on new server yet. I
believe you can get rid of them by issuing drop database
command.
Then start attachig user databases, and then msdb.
hth.
>--Original Message--
>sql2k sp3
>Im going to be moving sql from one box to a newer one
>with better hardware today. This is my plan:
>Restore a backup of Master and MSDB onto the new box.
>Detach and attach the user db's.
>Ive used detach and attach but never in this scenario.
>Does anyone see a problem with this?
>TIA, Chris
>
>.
>|||My plan wasnt to detach and attach msdb at all. It was to
backup/ restore it. Will this still work?
>--Original Message--
>Your plan is perfect, only thing is that the restored
>master database will still have entries for user
>databases, even if they don't exist on new server yet. I
>believe you can get rid of them by issuing drop database
>command.
>Then start attachig user databases, and then msdb.
>
>hth.
>>--Original Message--
>>sql2k sp3
>>Im going to be moving sql from one box to a newer one
>>with better hardware today. This is my plan:
>>Restore a backup of Master and MSDB onto the new box.
>>Detach and attach the user db's.
>>Ive used detach and attach but never in this scenario.
>>Does anyone see a problem with this?
>>TIA, Chris
>>
>>.
>.
>|||you can backup/restore or attach/detach msdb database. or
just rename new mdf and ldf files for msdb on new server
(just for backup) and then copy original mdf/ldf files in
their place when the sql server is not running.
You can do same for master database as well, if you don't
want to use backup/restore.
hth.
>--Original Message--
>My plan wasnt to detach and attach msdb at all. It was to
>backup/ restore it. Will this still work?
>
>>--Original Message--
>>Your plan is perfect, only thing is that the restored
>>master database will still have entries for user
>>databases, even if they don't exist on new server yet. I
>>believe you can get rid of them by issuing drop database
>>command.
>>Then start attachig user databases, and then msdb.
>>
>>hth.
>>--Original Message--
>>sql2k sp3
>>Im going to be moving sql from one box to a newer one
>>with better hardware today. This is my plan:
>>Restore a backup of Master and MSDB onto the new box.
>>Detach and attach the user db's.
>>Ive used detach and attach but never in this scenario.
>>Does anyone see a problem with this?
>>TIA, Chris
>>
>>.
>>.
>.
>