Is it possible to recover master database from problematic master.mdf and/or
problematic mastlog.ldf? No backups exist. The error that appeared in event
log is
Error:9003, Severity:20, State 1. and right after that: "Cannot recover
master database.Exiting" . The reason I am posting this is that I know there
is something starnge going on because there was no hard disk failure and the
problem appeared after power loss of the server. But scan disk did not report
any problem when the server rebooted after the power loss. So maybe the file
is "not so corrupted" or maybe it is a fixable problem. Thank you in advance.Hi
9003: The LSN %S_LSN passed to log scan in database '%.*ls' is invalid.
You have corruption. SQL server might have been in the middle of writing to
the DB when the power outage occured. This can corrupt the DB.
Without a backup of Master, you are high and dry. Your only option is the
run the Rebuild Wizard (Rebuildm.exe), but you loose all your user logins.
Look up the topic in BOL.
Regards
Mike
"Radis Bill" wrote:
> Is it possible to recover master database from problematic master.mdf and/or
> problematic mastlog.ldf? No backups exist. The error that appeared in event
> log is
> Error:9003, Severity:20, State 1. and right after that: "Cannot recover
> master database.Exiting" . The reason I am posting this is that I know there
> is something starnge going on because there was no hard disk failure and the
> problem appeared after power loss of the server. But scan disk did not report
> any problem when the server rebooted after the power loss. So maybe the file
> is "not so corrupted" or maybe it is a fixable problem. Thank you in advance.|||From the console, you might be able to start sqlservr with the -T3607
option. The recovers non of the databases, system nor users. This may
allow you to export the configuration contexts from the system tables from
within the master database. If you do this, then there is a chance that you
would have all the information necessary to replace the content on a rebuilt
master. However, THIS IS A COMPLICATED SITUATION. CALL MS PSS FOR
ASSISTANCE.
Sincerely,
Anthony Thomas
"Radis Bill" <Radis Bill@.discussions.microsoft.com> wrote in message
news:63EFB560-DFC7-4D36-B331-62846758B058@.microsoft.com...
Is it possible to recover master database from problematic master.mdf and/or
problematic mastlog.ldf? No backups exist. The error that appeared in event
log is
Error:9003, Severity:20, State 1. and right after that: "Cannot recover
master database.Exiting" . The reason I am posting this is that I know there
is something starnge going on because there was no hard disk failure and the
problem appeared after power loss of the server. But scan disk did not
report
any problem when the server rebooted after the power loss. So maybe the file
is "not so corrupted" or maybe it is a fixable problem. Thank you in
advance.
Showing posts with label recovery. Show all posts
Showing posts with label recovery. Show all posts
Monday, February 20, 2012
master.mdf recovery
Is it possible to recover master database from problematic master.mdf and/or
problematic mastlog.ldf? No backups exist. The error that appeared in event
log is
Error:9003, Severity:20, State 1. and right after that: "Cannot recover
master database.Exiting" . The reason I am posting this is that I know there
is something starnge going on because there was no hard disk failure and the
problem appeared after power loss of the server. But scan disk did not report
any problem when the server rebooted after the power loss. So maybe the file
is "not so corrupted" or maybe it is a fixable problem. Thank you in advance.
Hi
9003: The LSN %S_LSN passed to log scan in database '%.*ls' is invalid.
You have corruption. SQL server might have been in the middle of writing to
the DB when the power outage occured. This can corrupt the DB.
Without a backup of Master, you are high and dry. Your only option is the
run the Rebuild Wizard (Rebuildm.exe), but you loose all your user logins.
Look up the topic in BOL.
Regards
Mike
"Radis Bill" wrote:
> Is it possible to recover master database from problematic master.mdf and/or
> problematic mastlog.ldf? No backups exist. The error that appeared in event
> log is
> Error:9003, Severity:20, State 1. and right after that: "Cannot recover
> master database.Exiting" . The reason I am posting this is that I know there
> is something starnge going on because there was no hard disk failure and the
> problem appeared after power loss of the server. But scan disk did not report
> any problem when the server rebooted after the power loss. So maybe the file
> is "not so corrupted" or maybe it is a fixable problem. Thank you in advance.
|||From the console, you might be able to start sqlservr with the -T3607
option. The recovers non of the databases, system nor users. This may
allow you to export the configuration contexts from the system tables from
within the master database. If you do this, then there is a chance that you
would have all the information necessary to replace the content on a rebuilt
master. However, THIS IS A COMPLICATED SITUATION. CALL MS PSS FOR
ASSISTANCE.
Sincerely,
Anthony Thomas
"Radis Bill" <Radis Bill@.discussions.microsoft.com> wrote in message
news:63EFB560-DFC7-4D36-B331-62846758B058@.microsoft.com...
Is it possible to recover master database from problematic master.mdf and/or
problematic mastlog.ldf? No backups exist. The error that appeared in event
log is
Error:9003, Severity:20, State 1. and right after that: "Cannot recover
master database.Exiting" . The reason I am posting this is that I know there
is something starnge going on because there was no hard disk failure and the
problem appeared after power loss of the server. But scan disk did not
report
any problem when the server rebooted after the power loss. So maybe the file
is "not so corrupted" or maybe it is a fixable problem. Thank you in
advance.
problematic mastlog.ldf? No backups exist. The error that appeared in event
log is
Error:9003, Severity:20, State 1. and right after that: "Cannot recover
master database.Exiting" . The reason I am posting this is that I know there
is something starnge going on because there was no hard disk failure and the
problem appeared after power loss of the server. But scan disk did not report
any problem when the server rebooted after the power loss. So maybe the file
is "not so corrupted" or maybe it is a fixable problem. Thank you in advance.
Hi
9003: The LSN %S_LSN passed to log scan in database '%.*ls' is invalid.
You have corruption. SQL server might have been in the middle of writing to
the DB when the power outage occured. This can corrupt the DB.
Without a backup of Master, you are high and dry. Your only option is the
run the Rebuild Wizard (Rebuildm.exe), but you loose all your user logins.
Look up the topic in BOL.
Regards
Mike
"Radis Bill" wrote:
> Is it possible to recover master database from problematic master.mdf and/or
> problematic mastlog.ldf? No backups exist. The error that appeared in event
> log is
> Error:9003, Severity:20, State 1. and right after that: "Cannot recover
> master database.Exiting" . The reason I am posting this is that I know there
> is something starnge going on because there was no hard disk failure and the
> problem appeared after power loss of the server. But scan disk did not report
> any problem when the server rebooted after the power loss. So maybe the file
> is "not so corrupted" or maybe it is a fixable problem. Thank you in advance.
|||From the console, you might be able to start sqlservr with the -T3607
option. The recovers non of the databases, system nor users. This may
allow you to export the configuration contexts from the system tables from
within the master database. If you do this, then there is a chance that you
would have all the information necessary to replace the content on a rebuilt
master. However, THIS IS A COMPLICATED SITUATION. CALL MS PSS FOR
ASSISTANCE.
Sincerely,
Anthony Thomas
"Radis Bill" <Radis Bill@.discussions.microsoft.com> wrote in message
news:63EFB560-DFC7-4D36-B331-62846758B058@.microsoft.com...
Is it possible to recover master database from problematic master.mdf and/or
problematic mastlog.ldf? No backups exist. The error that appeared in event
log is
Error:9003, Severity:20, State 1. and right after that: "Cannot recover
master database.Exiting" . The reason I am posting this is that I know there
is something starnge going on because there was no hard disk failure and the
problem appeared after power loss of the server. But scan disk did not
report
any problem when the server rebooted after the power loss. So maybe the file
is "not so corrupted" or maybe it is a fixable problem. Thank you in
advance.
master.mdf recovery
Is it possible to recover master database from problematic master.mdf and/or
problematic mastlog.ldf? No backups exist. The error that appeared in event
log is
Error:9003, Severity:20, State 1. and right after that: "Cannot recover
master database.Exiting" . The reason I am posting this is that I know there
is something starnge going on because there was no hard disk failure and the
problem appeared after power loss of the server. But scan disk did not repor
t
any problem when the server rebooted after the power loss. So maybe the file
is "not so corrupted" or maybe it is a fixable problem. Thank you in advance
.Hi
9003: The LSN %S_LSN passed to log scan in database '%.*ls' is invalid.
You have corruption. SQL server might have been in the middle of writing to
the DB when the power outage occured. This can corrupt the DB.
Without a backup of Master, you are high and dry. Your only option is the
run the Rebuild Wizard (Rebuildm.exe), but you loose all your user logins.
Look up the topic in BOL.
Regards
Mike
"Radis Bill" wrote:
[vbcol=seagreen]
> Is it possible to recover master database from problematic master.mdf and/
or
> problematic mastlog.ldf? No backups exist. The error that appeared in even
t
> log is
> Error:9003, Severity:20, State 1. and right after that: "Cannot recover
> master database.Exiting" . The reason I am posting this is that I know the
re
> is something starnge going on because there was no hard disk failure and t
he
> problem appeared after power loss of the server. But scan disk did not rep
ort
> any problem when the server rebooted after the power loss. So maybe the fi
le
> is "not so corrupted" or maybe it is a fixable problem. Thank you in advance.[/vbc
ol]|||From the console, you might be able to start sqlservr with the -T3607
option. The recovers non of the databases, system nor users. This may
allow you to export the configuration contexts from the system tables from
within the master database. If you do this, then there is a chance that you
would have all the information necessary to replace the content on a rebuilt
master. However, THIS IS A COMPLICATED SITUATION. CALL MS PSS FOR
ASSISTANCE.
Sincerely,
Anthony Thomas
"Radis Bill" <Radis Bill@.discussions.microsoft.com> wrote in message
news:63EFB560-DFC7-4D36-B331-62846758B058@.microsoft.com...
Is it possible to recover master database from problematic master.mdf and/or
problematic mastlog.ldf? No backups exist. The error that appeared in event
log is
Error:9003, Severity:20, State 1. and right after that: "Cannot recover
master database.Exiting" . The reason I am posting this is that I know there
is something starnge going on because there was no hard disk failure and the
problem appeared after power loss of the server. But scan disk did not
report
any problem when the server rebooted after the power loss. So maybe the file
is "not so corrupted" or maybe it is a fixable problem. Thank you in
advance.
problematic mastlog.ldf? No backups exist. The error that appeared in event
log is
Error:9003, Severity:20, State 1. and right after that: "Cannot recover
master database.Exiting" . The reason I am posting this is that I know there
is something starnge going on because there was no hard disk failure and the
problem appeared after power loss of the server. But scan disk did not repor
t
any problem when the server rebooted after the power loss. So maybe the file
is "not so corrupted" or maybe it is a fixable problem. Thank you in advance
.Hi
9003: The LSN %S_LSN passed to log scan in database '%.*ls' is invalid.
You have corruption. SQL server might have been in the middle of writing to
the DB when the power outage occured. This can corrupt the DB.
Without a backup of Master, you are high and dry. Your only option is the
run the Rebuild Wizard (Rebuildm.exe), but you loose all your user logins.
Look up the topic in BOL.
Regards
Mike
"Radis Bill" wrote:
[vbcol=seagreen]
> Is it possible to recover master database from problematic master.mdf and/
or
> problematic mastlog.ldf? No backups exist. The error that appeared in even
t
> log is
> Error:9003, Severity:20, State 1. and right after that: "Cannot recover
> master database.Exiting" . The reason I am posting this is that I know the
re
> is something starnge going on because there was no hard disk failure and t
he
> problem appeared after power loss of the server. But scan disk did not rep
ort
> any problem when the server rebooted after the power loss. So maybe the fi
le
> is "not so corrupted" or maybe it is a fixable problem. Thank you in advance.[/vbc
ol]|||From the console, you might be able to start sqlservr with the -T3607
option. The recovers non of the databases, system nor users. This may
allow you to export the configuration contexts from the system tables from
within the master database. If you do this, then there is a chance that you
would have all the information necessary to replace the content on a rebuilt
master. However, THIS IS A COMPLICATED SITUATION. CALL MS PSS FOR
ASSISTANCE.
Sincerely,
Anthony Thomas
"Radis Bill" <Radis Bill@.discussions.microsoft.com> wrote in message
news:63EFB560-DFC7-4D36-B331-62846758B058@.microsoft.com...
Is it possible to recover master database from problematic master.mdf and/or
problematic mastlog.ldf? No backups exist. The error that appeared in event
log is
Error:9003, Severity:20, State 1. and right after that: "Cannot recover
master database.Exiting" . The reason I am posting this is that I know there
is something starnge going on because there was no hard disk failure and the
problem appeared after power loss of the server. But scan disk did not
report
any problem when the server rebooted after the power loss. So maybe the file
is "not so corrupted" or maybe it is a fixable problem. Thank you in
advance.
Master, Model, MSDB What Recovery Models
What Recovery Model and what Backup Type should be used on the Master, Model
and MSDB databases?Master and MSDB no choice as they get reset to simple anyway. Regular
(daily) full backups tends to be the most common.
Model - matters little but it does set the default recovey model for new
databses being created.
Mike John
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
> What Recovery Model and what Backup Type should be used on the Master,
> Model
> and MSDB databases?|||Hmmmm
1. Are you saying that that the Master and MSDB will always stay in simple
no matter what I pick?
2. If I do a full back up of the Master and MSDB every night and the
recovery mode is locked to simple, the Transaction Log that comes with the
full is not really used, it just seems to restore to the last "static" state.
"Mike John" wrote:
> Master and MSDB no choice as they get reset to simple anyway. Regular
> (daily) full backups tends to be the most common.
> Model - matters little but it does set the default recovey model for new
> databses being created.
> Mike John
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
> > What Recovery Model and what Backup Type should be used on the Master,
> > Model
> > and MSDB databases?
>
>|||You can have msdb in full recovery mode. I usually to log backups for msdb. The problem is that
Agent will set msdb to simple on startup. But you can create a job that reverses this and set the
job as a startup job.
You can set master to full, but that is a "null" operation as behavior is still same as simple and
you still cannot do log backups. I'd prefer an error message if I (try) to set master to full.
The transaction log is definitely used in simple recovery mode, for things as rollbacks and recovery
on startup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:62355AFE-F239-49BB-8F33-C50CDCD900C8@.microsoft.com...
> Hmmmm
> 1. Are you saying that that the Master and MSDB will always stay in simple
> no matter what I pick?
> 2. If I do a full back up of the Master and MSDB every night and the
> recovery mode is locked to simple, the Transaction Log that comes with the
> full is not really used, it just seems to restore to the last "static" state.
> "Mike John" wrote:
>> Master and MSDB no choice as they get reset to simple anyway. Regular
>> (daily) full backups tends to be the most common.
>> Model - matters little but it does set the default recovey model for new
>> databses being created.
>> Mike John
>> "Rich" <Rich@.discussions.microsoft.com> wrote in message
>> news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
>> > What Recovery Model and what Backup Type should be used on the Master,
>> > Model
>> > and MSDB databases?
>>
and MSDB databases?Master and MSDB no choice as they get reset to simple anyway. Regular
(daily) full backups tends to be the most common.
Model - matters little but it does set the default recovey model for new
databses being created.
Mike John
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
> What Recovery Model and what Backup Type should be used on the Master,
> Model
> and MSDB databases?|||Hmmmm
1. Are you saying that that the Master and MSDB will always stay in simple
no matter what I pick?
2. If I do a full back up of the Master and MSDB every night and the
recovery mode is locked to simple, the Transaction Log that comes with the
full is not really used, it just seems to restore to the last "static" state.
"Mike John" wrote:
> Master and MSDB no choice as they get reset to simple anyway. Regular
> (daily) full backups tends to be the most common.
> Model - matters little but it does set the default recovey model for new
> databses being created.
> Mike John
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
> > What Recovery Model and what Backup Type should be used on the Master,
> > Model
> > and MSDB databases?
>
>|||You can have msdb in full recovery mode. I usually to log backups for msdb. The problem is that
Agent will set msdb to simple on startup. But you can create a job that reverses this and set the
job as a startup job.
You can set master to full, but that is a "null" operation as behavior is still same as simple and
you still cannot do log backups. I'd prefer an error message if I (try) to set master to full.
The transaction log is definitely used in simple recovery mode, for things as rollbacks and recovery
on startup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:62355AFE-F239-49BB-8F33-C50CDCD900C8@.microsoft.com...
> Hmmmm
> 1. Are you saying that that the Master and MSDB will always stay in simple
> no matter what I pick?
> 2. If I do a full back up of the Master and MSDB every night and the
> recovery mode is locked to simple, the Transaction Log that comes with the
> full is not really used, it just seems to restore to the last "static" state.
> "Mike John" wrote:
>> Master and MSDB no choice as they get reset to simple anyway. Regular
>> (daily) full backups tends to be the most common.
>> Model - matters little but it does set the default recovey model for new
>> databses being created.
>> Mike John
>> "Rich" <Rich@.discussions.microsoft.com> wrote in message
>> news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
>> > What Recovery Model and what Backup Type should be used on the Master,
>> > Model
>> > and MSDB databases?
>>
Master, Model, MSDB What Recovery Models
What Recovery Model and what Backup Type should be used on the Master, Model
and MSDB databases?
Master and MSDB no choice as they get reset to simple anyway. Regular
(daily) full backups tends to be the most common.
Model - matters little but it does set the default recovey model for new
databses being created.
Mike John
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
> What Recovery Model and what Backup Type should be used on the Master,
> Model
> and MSDB databases?
|||Hmmmm
1. Are you saying that that the Master and MSDB will always stay in simple
no matter what I pick?
2. If I do a full back up of the Master and MSDB every night and the
recovery mode is locked to simple, the Transaction Log that comes with the
full is not really used, it just seems to restore to the last "static" state.
"Mike John" wrote:
> Master and MSDB no choice as they get reset to simple anyway. Regular
> (daily) full backups tends to be the most common.
> Model - matters little but it does set the default recovey model for new
> databses being created.
> Mike John
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
>
>
|||You can have msdb in full recovery mode. I usually to log backups for msdb. The problem is that
Agent will set msdb to simple on startup. But you can create a job that reverses this and set the
job as a startup job.
You can set master to full, but that is a "null" operation as behavior is still same as simple and
you still cannot do log backups. I'd prefer an error message if I (try) to set master to full.
The transaction log is definitely used in simple recovery mode, for things as rollbacks and recovery
on startup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:62355AFE-F239-49BB-8F33-C50CDCD900C8@.microsoft.com...[vbcol=seagreen]
> Hmmmm
> 1. Are you saying that that the Master and MSDB will always stay in simple
> no matter what I pick?
> 2. If I do a full back up of the Master and MSDB every night and the
> recovery mode is locked to simple, the Transaction Log that comes with the
> full is not really used, it just seems to restore to the last "static" state.
> "Mike John" wrote:
and MSDB databases?
Master and MSDB no choice as they get reset to simple anyway. Regular
(daily) full backups tends to be the most common.
Model - matters little but it does set the default recovey model for new
databses being created.
Mike John
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
> What Recovery Model and what Backup Type should be used on the Master,
> Model
> and MSDB databases?
|||Hmmmm
1. Are you saying that that the Master and MSDB will always stay in simple
no matter what I pick?
2. If I do a full back up of the Master and MSDB every night and the
recovery mode is locked to simple, the Transaction Log that comes with the
full is not really used, it just seems to restore to the last "static" state.
"Mike John" wrote:
> Master and MSDB no choice as they get reset to simple anyway. Regular
> (daily) full backups tends to be the most common.
> Model - matters little but it does set the default recovey model for new
> databses being created.
> Mike John
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
>
>
|||You can have msdb in full recovery mode. I usually to log backups for msdb. The problem is that
Agent will set msdb to simple on startup. But you can create a job that reverses this and set the
job as a startup job.
You can set master to full, but that is a "null" operation as behavior is still same as simple and
you still cannot do log backups. I'd prefer an error message if I (try) to set master to full.
The transaction log is definitely used in simple recovery mode, for things as rollbacks and recovery
on startup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:62355AFE-F239-49BB-8F33-C50CDCD900C8@.microsoft.com...[vbcol=seagreen]
> Hmmmm
> 1. Are you saying that that the Master and MSDB will always stay in simple
> no matter what I pick?
> 2. If I do a full back up of the Master and MSDB every night and the
> recovery mode is locked to simple, the Transaction Log that comes with the
> full is not really used, it just seems to restore to the last "static" state.
> "Mike John" wrote:
Master, Model, MSDB What Recovery Models
What Recovery Model and what Backup Type should be used on the Master, Model
and MSDB databases?Master and MSDB no choice as they get reset to simple anyway. Regular
(daily) full backups tends to be the most common.
Model - matters little but it does set the default recovey model for new
databses being created.
Mike John
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
> What Recovery Model and what Backup Type should be used on the Master,
> Model
> and MSDB databases?|||Hmmmm
1. Are you saying that that the Master and MSDB will always stay in simple
no matter what I pick?
2. If I do a full back up of the Master and MSDB every night and the
recovery mode is locked to simple, the Transaction Log that comes with the
full is not really used, it just seems to restore to the last "static" state
.
"Mike John" wrote:
> Master and MSDB no choice as they get reset to simple anyway. Regular
> (daily) full backups tends to be the most common.
> Model - matters little but it does set the default recovey model for new
> databses being created.
> Mike John
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
>
>|||You can have msdb in full recovery mode. I usually to log backups for msdb.
The problem is that
Agent will set msdb to simple on startup. But you can create a job that reve
rses this and set the
job as a startup job.
You can set master to full, but that is a "null" operation as behavior is st
ill same as simple and
you still cannot do log backups. I'd prefer an error message if I (try) to s
et master to full.
The transaction log is definitely used in simple recovery mode, for things a
s rollbacks and recovery
on startup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:62355AFE-F239-49BB-8F33-C50CDCD900C8@.microsoft.com...[vbcol=seagreen]
> Hmmmm
> 1. Are you saying that that the Master and MSDB will always stay in simple
> no matter what I pick?
> 2. If I do a full back up of the Master and MSDB every night and the
> recovery mode is locked to simple, the Transaction Log that comes with the
> full is not really used, it just seems to restore to the last "static" sta
te.
> "Mike John" wrote:
>
and MSDB databases?Master and MSDB no choice as they get reset to simple anyway. Regular
(daily) full backups tends to be the most common.
Model - matters little but it does set the default recovey model for new
databses being created.
Mike John
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
> What Recovery Model and what Backup Type should be used on the Master,
> Model
> and MSDB databases?|||Hmmmm
1. Are you saying that that the Master and MSDB will always stay in simple
no matter what I pick?
2. If I do a full back up of the Master and MSDB every night and the
recovery mode is locked to simple, the Transaction Log that comes with the
full is not really used, it just seems to restore to the last "static" state
.
"Mike John" wrote:
> Master and MSDB no choice as they get reset to simple anyway. Regular
> (daily) full backups tends to be the most common.
> Model - matters little but it does set the default recovey model for new
> databses being created.
> Mike John
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:70327943-6C4C-46B0-98AD-C875FCD7F9D1@.microsoft.com...
>
>|||You can have msdb in full recovery mode. I usually to log backups for msdb.
The problem is that
Agent will set msdb to simple on startup. But you can create a job that reve
rses this and set the
job as a startup job.
You can set master to full, but that is a "null" operation as behavior is st
ill same as simple and
you still cannot do log backups. I'd prefer an error message if I (try) to s
et master to full.
The transaction log is definitely used in simple recovery mode, for things a
s rollbacks and recovery
on startup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:62355AFE-F239-49BB-8F33-C50CDCD900C8@.microsoft.com...[vbcol=seagreen]
> Hmmmm
> 1. Are you saying that that the Master and MSDB will always stay in simple
> no matter what I pick?
> 2. If I do a full back up of the Master and MSDB every night and the
> recovery mode is locked to simple, the Transaction Log that comes with the
> full is not really used, it just seems to restore to the last "static" sta
te.
> "Mike John" wrote:
>
Subscribe to:
Comments (Atom)