Hi,
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind of
input on this is very much appreciated.
Thank you
This is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>
|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:
> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
>
>
Showing posts with label whenever. Show all posts
Showing posts with label whenever. Show all posts
Saturday, February 25, 2012
MSDB Recovery Model Option
Hi,
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind of
input on this is very much appreciated.
Thank youThis is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:
> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> > Hi,
> >
> > On one of our servers, whenever there is a system reboot the recovery
> > model
> > option on the MSDB database is reset to 'Simple'. This is causing the
> > Transaction Log to fail. At that point I have to go back and change it to
> > 'Full' again. Is there any setting/configuration that I can change so the
> > recovery model is not changed and is always 'Full' like I setup. Any kind
> > of
> > input on this is very much appreciated.
> >
> > Thank you
> >
>
>
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind of
input on this is very much appreciated.
Thank youThis is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:
> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> > Hi,
> >
> > On one of our servers, whenever there is a system reboot the recovery
> > model
> > option on the MSDB database is reset to 'Simple'. This is causing the
> > Transaction Log to fail. At that point I have to go back and change it to
> > 'Full' again. Is there any setting/configuration that I can change so the
> > recovery model is not changed and is always 'Full' like I setup. Any kind
> > of
> > input on this is very much appreciated.
> >
> > Thank you
> >
>
>
MSDB Recovery Model Option
Hi,
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind o
f
input on this is very much appreciated.
Thank youThis is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:
> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
>
>
On one of our servers, whenever there is a system reboot the recovery model
option on the MSDB database is reset to 'Simple'. This is causing the
Transaction Log to fail. At that point I have to go back and change it to
'Full' again. Is there any setting/configuration that I can change so the
recovery model is not changed and is always 'Full' like I setup. Any kind o
f
input on this is very much appreciated.
Thank youThis is by design. Leave the MSDB database in simple recovery and do more
frequent full backups. SQL does not like full recovery for system
databases.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
> Hi,
> On one of our servers, whenever there is a system reboot the recovery
> model
> option on the MSDB database is reset to 'Simple'. This is causing the
> Transaction Log to fail. At that point I have to go back and change it to
> 'Full' again. Is there any setting/configuration that I can change so the
> recovery model is not changed and is always 'Full' like I setup. Any kind
> of
> input on this is very much appreciated.
> Thank you
>|||Thank you very very much Geoff.
"Geoff N. Hiten" wrote:
> This is by design. Leave the MSDB database in simple recovery and do more
> frequent full backups. SQL does not like full recovery for system
> databases.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "helpplease" <helpplease@.discussions.microsoft.com> wrote in message
> news:C862E63E-B996-43A8-8936-7C691D15C0F0@.microsoft.com...
>
>
msdb marked as suspect
Hi All,
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,
Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,
Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
msdb marked as suspect
Hi All,
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
msdb marked as suspect
Hi All,
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
Subscribe to:
Posts (Atom)