Does anyone know what the "4IDR" databases are? (Master/Model/MSDB)
MSSQL Log entry: Starting up database 'master4IDR'.
I do see the .mdf & .ldf, but I have no such db on this server.
What are these databases?
Thanx!
I've never see any such animals. My guess is that some 3rd party tool (like backup sw or similar)
has created these.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"JLS" <jlshoop@.hotmail.com> wrote in message news:eYXq6WBIFHA.2620@.tk2msftngp13.phx.gbl...
Does anyone know what the "4IDR" databases are? (Master/Model/MSDB)
MSSQL Log entry: Starting up database 'master4IDR'.
I do see the .mdf & .ldf, but I have no such db on this server.
What are these databases?
Thanx!
|||I did a google search on 'masteri4dr' and got several, but inconclusive,
hits. Many referred to third party backup software.
Try running the query below to identify the databases associated with these
files.
SELECT *
FROM master..sysaltfiles
WHERE filename LIKE '%4IDR.mdf%'
Hope this helps.
Dan Guzman
SQL Server MVP
"JLS" <jlshoop@.hotmail.com> wrote in message
news:eYXq6WBIFHA.2620@.tk2msftngp13.phx.gbl...
Does anyone know what the "4IDR" databases are? (Master/Model/MSDB)
MSSQL Log entry: Starting up database 'master4IDR'.
I do see the .mdf & .ldf, but I have no such db on this server.
What are these databases?
Thanx!
Showing posts with label model. Show all posts
Showing posts with label model. Show all posts
Saturday, February 25, 2012
master4IDR ??
Does anyone know what the "4IDR" databases are? (Master/Model/MSDB)
MSSQL Log entry: Starting up database 'master4IDR'.
I do see the .mdf & .ldf, but I have no such db on this server.
What are these databases?
Thanx!I've never see any such animals. My guess is that some 3rd party tool (like
backup sw or similar)
has created these.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"JLS" <jlshoop@.hotmail.com> wrote in message news:eYXq6WBIFHA.2620@.tk2msftng
p13.phx.gbl...
Does anyone know what the "4IDR" databases are? (Master/Model/MSDB)
MSSQL Log entry: Starting up database 'master4IDR'.
I do see the .mdf & .ldf, but I have no such db on this server.
What are these databases?
Thanx!|||I did a google search on 'masteri4dr' and got several, but inconclusive,
hits. Many referred to third party backup software.
Try running the query below to identify the databases associated with these
files.
SELECT *
FROM master..sysaltfiles
WHERE filename LIKE '%4IDR.mdf%'
Hope this helps.
Dan Guzman
SQL Server MVP
"JLS" <jlshoop@.hotmail.com> wrote in message
news:eYXq6WBIFHA.2620@.tk2msftngp13.phx.gbl...
Does anyone know what the "4IDR" databases are? (Master/Model/MSDB)
MSSQL Log entry: Starting up database 'master4IDR'.
I do see the .mdf & .ldf, but I have no such db on this server.
What are these databases?
Thanx!
MSSQL Log entry: Starting up database 'master4IDR'.
I do see the .mdf & .ldf, but I have no such db on this server.
What are these databases?
Thanx!I've never see any such animals. My guess is that some 3rd party tool (like
backup sw or similar)
has created these.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"JLS" <jlshoop@.hotmail.com> wrote in message news:eYXq6WBIFHA.2620@.tk2msftng
p13.phx.gbl...
Does anyone know what the "4IDR" databases are? (Master/Model/MSDB)
MSSQL Log entry: Starting up database 'master4IDR'.
I do see the .mdf & .ldf, but I have no such db on this server.
What are these databases?
Thanx!|||I did a google search on 'masteri4dr' and got several, but inconclusive,
hits. Many referred to third party backup software.
Try running the query below to identify the databases associated with these
files.
SELECT *
FROM master..sysaltfiles
WHERE filename LIKE '%4IDR.mdf%'
Hope this helps.
Dan Guzman
SQL Server MVP
"JLS" <jlshoop@.hotmail.com> wrote in message
news:eYXq6WBIFHA.2620@.tk2msftngp13.phx.gbl...
Does anyone know what the "4IDR" databases are? (Master/Model/MSDB)
MSSQL Log entry: Starting up database 'master4IDR'.
I do see the .mdf & .ldf, but I have no such db on this server.
What are these databases?
Thanx!
Monday, February 20, 2012
Master, Tempdb, Msdb, Model?
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
I would put the temp DB on a seperate drive as well
http://sqlservercode.blogspot.com/
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
> Any opinions are appreciated!
>
|||And also move the log file to a separate file
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
> Any opinions are appreciated!
>
|||I use to have data and log on same drive for system databases. The possible exception is tempdb.
This can be a high-activity database, so same reasoning goes for tempdb as for other databases.
Also, moving database files for system databases is a bit special, so read KB 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFTNGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate
drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
|||Thanx everyone!
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFTNGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
I would put the temp DB on a seperate drive as well
http://sqlservercode.blogspot.com/
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
> Any opinions are appreciated!
>
|||And also move the log file to a separate file
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
> Any opinions are appreciated!
>
|||I use to have data and log on same drive for system databases. The possible exception is tempdb.
This can be a high-activity database, so same reasoning goes for tempdb as for other databases.
Also, moving database files for system databases is a bit special, so read KB 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFTNGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate
drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
|||Thanx everyone!
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFTNGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
Master, Tempdb, Msdb, Model?
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!I would put the temp DB on a seperate drive as well
http://sqlservercode.blogspot.com/
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||And also move the log file to a separate file
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||I use to have data and log on same drive for system databases. The possible
exception is tempdb.
This can be a high-activity database, so same reasoning goes for tempdb as f
or other databases.
Also, moving database files for system databases is a bit special, so read K
B 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate
drives, but I am not sure of what a "best practice" is for the Sql system da
tabases.
Any opinions are appreciated!|||Thanx everyone!
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!I would put the temp DB on a seperate drive as well
http://sqlservercode.blogspot.com/
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||And also move the log file to a separate file
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||I use to have data and log on same drive for system databases. The possible
exception is tempdb.
This can be a high-activity database, so same reasoning goes for tempdb as f
or other databases.
Also, moving database files for system databases is a bit special, so read K
B 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate
drives, but I am not sure of what a "best practice" is for the Sql system da
tabases.
Any opinions are appreciated!|||Thanx everyone!
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!
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:
>
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
Labels:
allproduction,
backup,
create,
database,
databases,
maintenance,
master,
microsoft,
model,
msdb,
mysql,
oracle,
orgainizing,
ourcompany,
plans,
server,
sql
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
Labels:
allproduction,
backup,
create,
database,
databases,
maintenance,
master,
microsoft,
model,
msdb,
mysql,
oracle,
orgainizing,
ourcompany,
plans,
server,
sql
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 & msdb in database list
On a new, clustered, install of SQL Server 2000, I can't see the master,
model, msdb & tempdb databases in the Database list of Enterprise Manager.
I suspect I may have changed a setting, but I'm not sure what, or where.That is a setting in EM for the registered server. From memory: right-click the registered server,
select "Edit server registration" and you will find an option whether to hide system objects.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jay" <nospan@.nospam.org> wrote in message news:%236DFzT9HIHA.1188@.TK2MSFTNGP04.phx.gbl...
> On a new, clustered, install of SQL Server 2000, I can't see the master, model, msdb & tempdb
> databases in the Database list of Enterprise Manager.
> I suspect I may have changed a setting, but I'm not sure what, or where.
>
>|||Try this,
On Enterprise Manager, right-clik your server and select Edit SQL Server
Registration Properties and check the box 'Show system databases and system
objects'. Click Ok. Your system databases must be there.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Jay" wrote:
> On a new, clustered, install of SQL Server 2000, I can't see the master,
> model, msdb & tempdb databases in the Database list of Enterprise Manager.
> I suspect I may have changed a setting, but I'm not sure what, or where.
>
>|||Excellent, thanks guys
"Jay" <nospan@.nospam.org> wrote in message
news:%236DFzT9HIHA.1188@.TK2MSFTNGP04.phx.gbl...
> On a new, clustered, install of SQL Server 2000, I can't see the master,
> model, msdb & tempdb databases in the Database list of Enterprise Manager.
> I suspect I may have changed a setting, but I'm not sure what, or where.
>
>
model, msdb & tempdb databases in the Database list of Enterprise Manager.
I suspect I may have changed a setting, but I'm not sure what, or where.That is a setting in EM for the registered server. From memory: right-click the registered server,
select "Edit server registration" and you will find an option whether to hide system objects.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jay" <nospan@.nospam.org> wrote in message news:%236DFzT9HIHA.1188@.TK2MSFTNGP04.phx.gbl...
> On a new, clustered, install of SQL Server 2000, I can't see the master, model, msdb & tempdb
> databases in the Database list of Enterprise Manager.
> I suspect I may have changed a setting, but I'm not sure what, or where.
>
>|||Try this,
On Enterprise Manager, right-clik your server and select Edit SQL Server
Registration Properties and check the box 'Show system databases and system
objects'. Click Ok. Your system databases must be there.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Jay" wrote:
> On a new, clustered, install of SQL Server 2000, I can't see the master,
> model, msdb & tempdb databases in the Database list of Enterprise Manager.
> I suspect I may have changed a setting, but I'm not sure what, or where.
>
>|||Excellent, thanks guys
"Jay" <nospan@.nospam.org> wrote in message
news:%236DFzT9HIHA.1188@.TK2MSFTNGP04.phx.gbl...
> On a new, clustered, install of SQL Server 2000, I can't see the master,
> model, msdb & tempdb databases in the Database list of Enterprise Manager.
> I suspect I may have changed a setting, but I'm not sure what, or where.
>
>
Subscribe to:
Comments (Atom)