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?
>>
Showing posts with label backup. Show all posts
Showing posts with label backup. Show all posts
Monday, February 20, 2012
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:
>
Master, Model, and Msdb backup
Hi Everyone,
I'm orgainizing the backup maintenance plans for our
company. I create two different plans: one for all
production databases and one for the system databases.
I've got the recovery method set for "Simple" for the
system databases. In the "Optimization" tab in the
maintenance plan, I have just the "Update Statistics" with
a 10% sample. Reorganize index pages doesn't seem like it
would be necessary for these files. Is there anything
else in the optimiztion that I should set? Any
suggestions are appreciated.
Thanks in advance
Larry
Hi,
For System databases it is not required to reorganise the index pages
frequently becuase the changes are very few. So
you can go ahed with the way you planned.
Only thing is have a look into the maintenance plans and ensure that all
databases are backeup (both user and system) sucessfully daily.
Thanks
Hari
MCDBA
"Larry Morando" <anonymous@.discussions.microsoft.com> wrote in message
news:1c34401c4523d$a7dfef10$a501280a@.phx.gbl...
> Hi Everyone,
> I'm orgainizing the backup maintenance plans for our
> company. I create two different plans: one for all
> production databases and one for the system databases.
> I've got the recovery method set for "Simple" for the
> system databases. In the "Optimization" tab in the
> maintenance plan, I have just the "Update Statistics" with
> a 10% sample. Reorganize index pages doesn't seem like it
> would be necessary for these files. Is there anything
> else in the optimiztion that I should set? Any
> suggestions are appreciated.
> Thanks in advance
> Larry
I'm orgainizing the backup maintenance plans for our
company. I create two different plans: one for all
production databases and one for the system databases.
I've got the recovery method set for "Simple" for the
system databases. In the "Optimization" tab in the
maintenance plan, I have just the "Update Statistics" with
a 10% sample. Reorganize index pages doesn't seem like it
would be necessary for these files. Is there anything
else in the optimiztion that I should set? Any
suggestions are appreciated.
Thanks in advance
Larry
Hi,
For System databases it is not required to reorganise the index pages
frequently becuase the changes are very few. So
you can go ahed with the way you planned.
Only thing is have a look into the maintenance plans and ensure that all
databases are backeup (both user and system) sucessfully daily.
Thanks
Hari
MCDBA
"Larry Morando" <anonymous@.discussions.microsoft.com> wrote in message
news:1c34401c4523d$a7dfef10$a501280a@.phx.gbl...
> Hi Everyone,
> I'm orgainizing the backup maintenance plans for our
> company. I create two different plans: one for all
> production databases and one for the system databases.
> I've got the recovery method set for "Simple" for the
> system databases. In the "Optimization" tab in the
> maintenance plan, I have just the "Update Statistics" with
> a 10% sample. Reorganize index pages doesn't seem like it
> would be necessary for these files. Is there anything
> else in the optimiztion that I should set? Any
> suggestions are appreciated.
> Thanks in advance
> Larry
Master, Model, and Msdb backup
Hi Everyone,
I'm orgainizing the backup maintenance plans for our
company. I create two different plans: one for all
production databases and one for the system databases.
I've got the recovery method set for "Simple" for the
system databases. In the "Optimization" tab in the
maintenance plan, I have just the "Update Statistics" with
a 10% sample. Reorganize index pages doesn't seem like it
would be necessary for these files. Is there anything
else in the optimiztion that I should set? Any
suggestions are appreciated.
Thanks in advance
LarryHi,
For System databases it is not required to reorganise the index pages
frequently becuase the changes are very few. So
you can go ahed with the way you planned.
Only thing is have a look into the maintenance plans and ensure that all
databases are backeup (both user and system) sucessfully daily.
Thanks
Hari
MCDBA
"Larry Morando" <anonymous@.discussions.microsoft.com> wrote in message
news:1c34401c4523d$a7dfef10$a501280a@.phx
.gbl...
> Hi Everyone,
> I'm orgainizing the backup maintenance plans for our
> company. I create two different plans: one for all
> production databases and one for the system databases.
> I've got the recovery method set for "Simple" for the
> system databases. In the "Optimization" tab in the
> maintenance plan, I have just the "Update Statistics" with
> a 10% sample. Reorganize index pages doesn't seem like it
> would be necessary for these files. Is there anything
> else in the optimiztion that I should set? Any
> suggestions are appreciated.
> Thanks in advance
> Larry
I'm orgainizing the backup maintenance plans for our
company. I create two different plans: one for all
production databases and one for the system databases.
I've got the recovery method set for "Simple" for the
system databases. In the "Optimization" tab in the
maintenance plan, I have just the "Update Statistics" with
a 10% sample. Reorganize index pages doesn't seem like it
would be necessary for these files. Is there anything
else in the optimiztion that I should set? Any
suggestions are appreciated.
Thanks in advance
LarryHi,
For System databases it is not required to reorganise the index pages
frequently becuase the changes are very few. So
you can go ahed with the way you planned.
Only thing is have a look into the maintenance plans and ensure that all
databases are backeup (both user and system) sucessfully daily.
Thanks
Hari
MCDBA
"Larry Morando" <anonymous@.discussions.microsoft.com> wrote in message
news:1c34401c4523d$a7dfef10$a501280a@.phx
.gbl...
> Hi Everyone,
> I'm orgainizing the backup maintenance plans for our
> company. I create two different plans: one for all
> production databases and one for the system databases.
> I've got the recovery method set for "Simple" for the
> system databases. In the "Optimization" tab in the
> maintenance plan, I have just the "Update Statistics" with
> a 10% sample. Reorganize index pages doesn't seem like it
> would be necessary for these files. Is there anything
> else in the optimiztion that I should set? Any
> suggestions are appreciated.
> Thanks in advance
> Larry
Master, Model, and Msdb backup
Hi Everyone,
I'm orgainizing the backup maintenance plans for our
company. I create two different plans: one for all
production databases and one for the system databases.
I've got the recovery method set for "Simple" for the
system databases. In the "Optimization" tab in the
maintenance plan, I have just the "Update Statistics" with
a 10% sample. Reorganize index pages doesn't seem like it
would be necessary for these files. Is there anything
else in the optimiztion that I should set? Any
suggestions are appreciated.
Thanks in advance
LarryHi,
For System databases it is not required to reorganise the index pages
frequently becuase the changes are very few. So
you can go ahed with the way you planned.
Only thing is have a look into the maintenance plans and ensure that all
databases are backeup (both user and system) sucessfully daily.
Thanks
Hari
MCDBA
"Larry Morando" <anonymous@.discussions.microsoft.com> wrote in message
news:1c34401c4523d$a7dfef10$a501280a@.phx.gbl...
> Hi Everyone,
> I'm orgainizing the backup maintenance plans for our
> company. I create two different plans: one for all
> production databases and one for the system databases.
> I've got the recovery method set for "Simple" for the
> system databases. In the "Optimization" tab in the
> maintenance plan, I have just the "Update Statistics" with
> a 10% sample. Reorganize index pages doesn't seem like it
> would be necessary for these files. Is there anything
> else in the optimiztion that I should set? Any
> suggestions are appreciated.
> Thanks in advance
> Larry
I'm orgainizing the backup maintenance plans for our
company. I create two different plans: one for all
production databases and one for the system databases.
I've got the recovery method set for "Simple" for the
system databases. In the "Optimization" tab in the
maintenance plan, I have just the "Update Statistics" with
a 10% sample. Reorganize index pages doesn't seem like it
would be necessary for these files. Is there anything
else in the optimiztion that I should set? Any
suggestions are appreciated.
Thanks in advance
LarryHi,
For System databases it is not required to reorganise the index pages
frequently becuase the changes are very few. So
you can go ahed with the way you planned.
Only thing is have a look into the maintenance plans and ensure that all
databases are backeup (both user and system) sucessfully daily.
Thanks
Hari
MCDBA
"Larry Morando" <anonymous@.discussions.microsoft.com> wrote in message
news:1c34401c4523d$a7dfef10$a501280a@.phx.gbl...
> Hi Everyone,
> I'm orgainizing the backup maintenance plans for our
> company. I create two different plans: one for all
> production databases and one for the system databases.
> I've got the recovery method set for "Simple" for the
> system databases. In the "Optimization" tab in the
> maintenance plan, I have just the "Update Statistics" with
> a 10% sample. Reorganize index pages doesn't seem like it
> would be necessary for these files. Is there anything
> else in the optimiztion that I should set? Any
> suggestions are appreciated.
> Thanks in advance
> Larry
Master Transaction Log backup fails
:eek:
Okay. I changed the times that the transaction logs are backed up, via the built in maintenance schedule. It was then that I started to get failures only on the Transaction log backup for the master. The error that I get from the history log is Backup can not be performed on this database. This sub task is ignored. If I look in the file that is saved to disk :
Starting maintenance plan 'DB Maintenance Plan1' on 09/11/2004 02:30:00
Backup can not be performed on database 'master'. This sub task is ignored.
[1] Database onyx: Transaction Log Backup...
Destination: [R:\BACKUP\onyx\onyx_tlog_200411090230.TRN]
** Execution Time: 0 hrs, 0 mins, 23 secs **
[2] Database onyx: Verifying Backup...
** Execution Time: 0 hrs, 0 mins, 8 secs **
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan1' on 09/11/2004 02:30:31
SQLMAINT.EXE Process Exit Code: 1 (Failed)
I changed the backup back to its original time as this was the only change made. This has not resolved the problem. As I am new to SQL and still finding my feet All the other SQL maintenance plans that I changed are working fine.
Thanks
SteveCheck to make sure the database isnt in simple recovery mode. This would make transaction log backups fail. By default you cannot do a transaction log backup on the master database.
If you dont know how to check, do the following:
1. Right click the master database and click properties.
2. Click on the options tab.
3. Make sure recovery mode is set to full if you want to backup the transaction log.
-Mike|||The transaction log for the master database can not be backed up, or restored. You should do FULL backups of the master database, but transaction backups will not work.|||Actually, yes, you are correct. I dont know why I didnt remember this. Just do full backups instead of transaction log backups. The master database is usually very small so backups dont take a lot of disk space and full backups are much easier to restore.
-Mike|||No shame in that, Mike. I actually had a Microsoft technician tell me to put tempdb in Full Recovery mode, once. I don't know if he still works in the SQL Server group, anymore.|||;) Gents,
Thank youi for your help. I have looked into the issue and have submitted a few concerns to my management.
Many thanks
Okay. I changed the times that the transaction logs are backed up, via the built in maintenance schedule. It was then that I started to get failures only on the Transaction log backup for the master. The error that I get from the history log is Backup can not be performed on this database. This sub task is ignored. If I look in the file that is saved to disk :
Starting maintenance plan 'DB Maintenance Plan1' on 09/11/2004 02:30:00
Backup can not be performed on database 'master'. This sub task is ignored.
[1] Database onyx: Transaction Log Backup...
Destination: [R:\BACKUP\onyx\onyx_tlog_200411090230.TRN]
** Execution Time: 0 hrs, 0 mins, 23 secs **
[2] Database onyx: Verifying Backup...
** Execution Time: 0 hrs, 0 mins, 8 secs **
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan1' on 09/11/2004 02:30:31
SQLMAINT.EXE Process Exit Code: 1 (Failed)
I changed the backup back to its original time as this was the only change made. This has not resolved the problem. As I am new to SQL and still finding my feet All the other SQL maintenance plans that I changed are working fine.
Thanks
SteveCheck to make sure the database isnt in simple recovery mode. This would make transaction log backups fail. By default you cannot do a transaction log backup on the master database.
If you dont know how to check, do the following:
1. Right click the master database and click properties.
2. Click on the options tab.
3. Make sure recovery mode is set to full if you want to backup the transaction log.
-Mike|||The transaction log for the master database can not be backed up, or restored. You should do FULL backups of the master database, but transaction backups will not work.|||Actually, yes, you are correct. I dont know why I didnt remember this. Just do full backups instead of transaction log backups. The master database is usually very small so backups dont take a lot of disk space and full backups are much easier to restore.
-Mike|||No shame in that, Mike. I actually had a Microsoft technician tell me to put tempdb in Full Recovery mode, once. I don't know if he still works in the SQL Server group, anymore.|||;) Gents,
Thank youi for your help. I have looked into the issue and have submitted a few concerns to my management.
Many thanks
Master transaction log
Quick question - why is it not possible to backup the master database's transaction log
TIA
John BrownJohn Brown wrote:
> Quick question - why is it not possible to backup the master
> database's transaction log? TIA,
> John Brown
See:
PRB: Transaction Log Backups of Master Database Are Not Allowed
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q285/2/88.asp&NoWebContent=1
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks Sebastian, this is helpful, but what I wondered is is there any logical reason why a master transaction log backup is not possible
Regards
Joh|||John Brown wrote:
> Thanks Sebastian, this is helpful, but what I wondered is is there
> any logical reason why a master transaction log backup is not
> possible? Regards,
Yes, it is. Master database is setup in the SIMPLE recovery mode, when
transaction log is truncated on checkpoints and its space occupied by
commited transactions is constantly reused. That is why SIMPLE recovery
model does not allow transaction logs backups. It is a small database with
only a few transactions from time to time, SIMPLE recovery model is optimal
for this system database.
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
TIA
John BrownJohn Brown wrote:
> Quick question - why is it not possible to backup the master
> database's transaction log? TIA,
> John Brown
See:
PRB: Transaction Log Backups of Master Database Are Not Allowed
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q285/2/88.asp&NoWebContent=1
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks Sebastian, this is helpful, but what I wondered is is there any logical reason why a master transaction log backup is not possible
Regards
Joh|||John Brown wrote:
> Thanks Sebastian, this is helpful, but what I wondered is is there
> any logical reason why a master transaction log backup is not
> possible? Regards,
Yes, it is. Master database is setup in the SIMPLE recovery mode, when
transaction log is truncated on checkpoints and its space occupied by
commited transactions is constantly reused. That is why SIMPLE recovery
model does not allow transaction logs backups. It is a small database with
only a few transactions from time to time, SIMPLE recovery model is optimal
for this system database.
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Master transaction log
Quick question - why is it not possible to backup the master database's tran
saction log?
TIA,
John BrownJohn Brown wrote:
> Quick question - why is it not possible to backup the master
> database's transaction log? TIA,
> John Brown
See:
PRB: Transaction Log Backups of Master Database Are Not Allowed
http://support.microsoft.com/defaul...&NoWebContent=1
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks Sebastian, this is helpful, but what I wondered is is there any logic
al reason why a master transaction log backup is not possible?
Regards,
John|||John Brown wrote:
> Thanks Sebastian, this is helpful, but what I wondered is is there
> any logical reason why a master transaction log backup is not
> possible? Regards,
Yes, it is. Master database is setup in the SIMPLE recovery mode, when
transaction log is truncated on checkpoints and its space occupied by
commited transactions is constantly reused. That is why SIMPLE recovery
model does not allow transaction logs backups. It is a small database with
only a few transactions from time to time, SIMPLE recovery model is optimal
for this system database.
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
saction log?
TIA,
John BrownJohn Brown wrote:
> Quick question - why is it not possible to backup the master
> database's transaction log? TIA,
> John Brown
See:
PRB: Transaction Log Backups of Master Database Are Not Allowed
http://support.microsoft.com/defaul...&NoWebContent=1
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks Sebastian, this is helpful, but what I wondered is is there any logic
al reason why a master transaction log backup is not possible?
Regards,
John|||John Brown wrote:
> Thanks Sebastian, this is helpful, but what I wondered is is there
> any logical reason why a master transaction log backup is not
> possible? Regards,
Yes, it is. Master database is setup in the SIMPLE recovery mode, when
transaction log is truncated on checkpoints and its space occupied by
commited transactions is constantly reused. That is why SIMPLE recovery
model does not allow transaction logs backups. It is a small database with
only a few transactions from time to time, SIMPLE recovery model is optimal
for this system database.
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)