Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 1234»»»

Recovery model type of the database keeps changing Expand / Collapse
Author
Message
Posted Friday, February 08, 2008 9:08 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, April 24, 2013 2:28 PM
Points: 261, Visits: 1,492
Hi, the Recovery model of the database keeps changing to Simple which results in the failure of the transaction log backup jobs. I am trying to find out how's it's getting changed, any ideas are appreciated. Thanks!!
Post #453312
Posted Friday, February 08, 2008 10:22 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 11:34 AM
Points: 4,007, Visits: 4,857
Is it a user database or a system database? What was the recovery model when the database was created?

Greg
Post #453356
Posted Friday, February 08, 2008 10:36 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Wednesday, May 22, 2013 7:57 PM
Points: 6,998, Visits: 13,949
Keep in mind that the reason it "fails" is that there's ultimately nothing to back up in Simple mode. since the transaction log automatically truncates as soon as the activity is committed - there's nothing retained long enough for it to get backed up.

Perhaps it's not such a bad thing: could be perfectly appropriate depending on the purpose of said database.


----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Post #453367
Posted Friday, February 08, 2008 11:51 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, April 24, 2013 2:28 PM
Points: 261, Visits: 1,492
Greg Charles (2/8/2008)
Is it a user database or a system database? What was the recovery model when the database was created?


It's a user db, I do'nt know the recovery model when the db was created. Thanks for the speedy response.
Post #453396
Posted Wednesday, February 13, 2008 2:12 PM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 11:34 AM
Points: 4,007, Visits: 4,857
I've never heard of a database spontaneously change recovery models. I'd say that either the database is being restored from a backup made when the recovery model was simple or an Alter Database command is being executed by a member of sysadmin or db_owner.

Greg
Post #455401
Posted Wednesday, February 13, 2008 3:28 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, April 24, 2013 2:28 PM
Points: 261, Visits: 1,492
Greg Charles (2/13/2008)
I've never heard of a database spontaneously change recovery models. I'd say that either the database is being restored from a backup made when the recovery model was simple or an Alter Database command is being executed by a member of sysadmin or db_owner.


I checked all the sql jobs in that server I can't find any where about the altering of the db to simple. And also it's really wierd that it's happening to only one db out of 20 db's. And that db belongs to Desktop authority application, I do'nt think that application is changing the db to simple, Thanks for all the responses.
Post #455435
Posted Thursday, February 14, 2008 9:25 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 11:34 AM
Points: 4,007, Visits: 4,857
I have a couple more ideas. Changing the recovery model should be logged in the Windows Server Application log. Look in Event Viewer to see if there's a user or application related to the change.

You could run a Profiler trace to capture actions in the database. If the change always seems to occur at a particular time (like at night), you wouldn't have to run the trace very long.


Greg
Post #455803
Posted Thursday, February 14, 2008 9:40 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, May 22, 2013 3:51 PM
Points: 1,132, Visits: 664
Is the db a reporting or read only db? Is the db restored on a nightly basis from some other source?....I only mention this because I have seen this behavior with on of my dbs. The source db is set to simple, recovering the backup to the reporting system changes the destination from full recovery back to simple.
Post #455811
Posted Thursday, February 14, 2008 10:25 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, April 24, 2013 2:28 PM
Points: 261, Visits: 1,492
Greg Charles (2/14/2008)
I have a couple more ideas. Changing the recovery model should be logged in the Windows Server Application log. Look in Event Viewer to see if there's a user or application related to the change.

You could run a Profiler trace to capture actions in the database. If the change always seems to occur at a particular time (like at night), you wouldn't have to run the trace very long.


Here is information below from the event viewer:
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 2/10/2008
Time: 1:01:21 AM
User: username
Computer: server
Description:
5144 :
Autogrow of file 'DB_log' in database 'DB' cancelled or timed out after 0 ms. Use ALTER DATABASE to set a smaller FILEGROWTH or to set a new size

I think this might have caused it to change to Simple, but how can I fix this issue. Thanks!!
Post #455854
Posted Thursday, February 14, 2008 10:34 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: 2 days ago @ 3:46 PM
Points: 89, Visits: 952
You can also check the db datecreated if it's recent, you'll have an idea when the database just got restored.

_____________
Donn Policarpio
Post #455857
« Prev Topic | Next Topic »

Add to briefcase 1234»»»

Permissions Expand / Collapse