Database being set to SIMPLE Recovery (no MSDB)

My production seems to, either upon admin rebooting it for updates, or
for someother reason set the Recovermy Mode FROM Full TO Simple?
Weird. How can I track down what is doing this? its SQL 2000 SP4.
Thanks
Erik> My production seems to, either upon admin rebooting it for updates, or
> for someother reason set the Recovermy Mode FROM Full TO Simple?
> Weird. How can I track down what is doing this? its SQL 2000 SP4.
Use the Profiler - track ALTER DATABASE yourdb SET RECOVERY command.
--
Dejan Sarka, SQL Server MVP
Mentor, www.SolidQualityLearning.com
Anything written in this message represents solely the point of view of the
sender.
This message does not imply endorsement from Solid Quality Learning, and it
does not represent the point of view of Solid Quality Learning or any other
person, company or institution mentioned in this message

Database being set to SIMPLE Recovery (no MSDB)

My production seems to, either upon admin rebooting it for updates, or
for someother reason set the Recovermy Mode FROM Full TO Simple?
Weird. How can I track down what is doing this? its SQL 2000 SP4.
Thanks
Erik
> My production seems to, either upon admin rebooting it for updates, or
> for someother reason set the Recovermy Mode FROM Full TO Simple?
> Weird. How can I track down what is doing this? its SQL 2000 SP4.
Use the Profiler - track ALTER DATABASE yourdb SET RECOVERY command.
Dejan Sarka, SQL Server MVP
Mentor, www.SolidQualityLearning.com
Anything written in this message represents solely the point of view of the
sender.
This message does not imply endorsement from Solid Quality Learning, and it
does not represent the point of view of Solid Quality Learning or any other
person, company or institution mentioned in this message

Database being set to SIMPLE Recovery (no MSDB)

My production seems to, either upon admin rebooting it for updates, or
for someother reason set the Recovermy Mode FROM Full TO Simple?
Weird. How can I track down what is doing this? its SQL 2000 SP4.
Thanks
Erik> My production seems to, either upon admin rebooting it for updates, or
> for someother reason set the Recovermy Mode FROM Full TO Simple?
> Weird. How can I track down what is doing this? its SQL 2000 SP4.
Use the Profiler - track ALTER DATABASE yourdb SET RECOVERY command.
Dejan Sarka, SQL Server MVP
Mentor, www.SolidQualityLearning.com
Anything written in this message represents solely the point of view of the
sender.
This message does not imply endorsement from Solid Quality Learning, and it
does not represent the point of view of Solid Quality Learning or any other
person, company or institution mentioned in this message

Database backups

HI All
can some one please shed some light on backups please?
im running sql 2000 and i want to know how often i should
backup and restore my MSDB and MASTER databases.
Thanks in advance
ToddI personally do them every night. You really need to back them up though
when something in them changes. Seeing as they are system databases this
should be through the SQL Server interface or stored procs i.e.
New Jobs
New Logins
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Todd" <anonymous@.discussions.microsoft.com> wrote in message
news:030a01c3a70e$35404110$a101280a@.phx.gbl...
> HI All
> can some one please shed some light on backups please?
> im running sql 2000 and i want to know how often i should
> backup and restore my MSDB and MASTER databases.
> Thanks in advance
> Todd|||MSDB is important especially if you are doing things like
replication, etc. SQL Server uses it to store other
configuration/use. If you are not using any features that
utilize MSDB, then it is less important, but still
critical for SQL Server health. Generally it is fairly
small, so backing it up every night isn't a bad idea.
Master is the brains of the operation. It, too, is small,
but without a good and recent backup, you may be in
trouble if you need to restore it. I suggest nightly, but
at worst case, after updates such as a service pack since
you cannot, for example, restore a SP2 master to a SP3 SQL
Server.
You should never have to restore, but should always test
your backups elsewhere to ensure they are actually good.
However, in a D/R scenario, applying MSDB or MASTER to
another server could potentially have large negative
consequences since they contain configurations specific to
a particular instance of SQL Server.|||Hi,
I will do a daily backup of MSDB and Master database. As well as I have a
scheduled OS command which stops SQL Server and Agent during
sunday and copy the Master.mdf and mastlog.ldf file to a backup location.
This will help you a lot during crash situations.
Thanks
Hari
MCDBA
"Todd" <anonymous@.discussions.microsoft.com> wrote in message
news:030a01c3a70e$35404110$a101280a@.phx.gbl...
> HI All
> can some one please shed some light on backups please?
> im running sql 2000 and i want to know how often i should
> backup and restore my MSDB and MASTER databases.
> Thanks in advance
> Todd