We have a user database on which the recovery model keeps changing to Simple.
I go in every day and manually change it to Full, but nearly every night it
automatically gets set back to Simple. Why is this happening?
Note: I have read the previous threads which discuss this problem happening
with the msdb database. But in my case, it isn't msdb - it is a USER
database."CadeBryant" <CadeBryant@.discussions.microsoft.com> wrote in message
news:F90570AE-4AD3-4D2F-B53C-0928E6D6FD0B@.microsoft.com...
> We have a user database on which the recovery model keeps changing to
> Simple.
> I go in every day and manually change it to Full, but nearly every night
> it
> automatically gets set back to Simple. Why is this happening?
> Note: I have read the previous threads which discuss this problem
> happening
> with the msdb database. But in my case, it isn't msdb - it is a USER
> database.
Check for any maintenance jobs, especially any that do attempt fixes on the
databases.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||The only maintenance jobs are for the system DBs - nothing for the user DBs.
"Greg D. Moore (Strider)" wrote:
> "CadeBryant" <CadeBryant@.discussions.microsoft.com> wrote in message
> news:F90570AE-4AD3-4D2F-B53C-0928E6D6FD0B@.microsoft.com...
> > We have a user database on which the recovery model keeps changing to
> > Simple.
> > I go in every day and manually change it to Full, but nearly every night
> > it
> > automatically gets set back to Simple. Why is this happening?
> >
> > Note: I have read the previous threads which discuss this problem
> > happening
> > with the msdb database. But in my case, it isn't msdb - it is a USER
> > database.
>
> Check for any maintenance jobs, especially any that do attempt fixes on the
> databases.
>
> --
> Greg Moore
> SQL Server DBA Consulting
> sql (at) greenms.com http://www.greenms.com
>
>|||I suggest you use a server side Profiler trace to catch commands (use filter in the trace) such as
sp_dboption and ALTER DATABASE.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"CadeBryant" <CadeBryant@.discussions.microsoft.com> wrote in message
news:27A46AE4-5BD3-4E09-A433-002A030782DB@.microsoft.com...
> The only maintenance jobs are for the system DBs - nothing for the user DBs.
> "Greg D. Moore (Strider)" wrote:
>> "CadeBryant" <CadeBryant@.discussions.microsoft.com> wrote in message
>> news:F90570AE-4AD3-4D2F-B53C-0928E6D6FD0B@.microsoft.com...
>> > We have a user database on which the recovery model keeps changing to
>> > Simple.
>> > I go in every day and manually change it to Full, but nearly every night
>> > it
>> > automatically gets set back to Simple. Why is this happening?
>> >
>> > Note: I have read the previous threads which discuss this problem
>> > happening
>> > with the msdb database. But in my case, it isn't msdb - it is a USER
>> > database.
>>
>> Check for any maintenance jobs, especially any that do attempt fixes on the
>> databases.
>>
>> --
>> Greg Moore
>> SQL Server DBA Consulting
>> sql (at) greenms.com http://www.greenms.com
>>
Showing posts with label manually. Show all posts
Showing posts with label manually. Show all posts
Wednesday, March 28, 2012
Recovery model on user db automatically changes from Full to Simpl
We have a user database on which the recovery model keeps changing to Simple.
I go in every day and manually change it to Full, but nearly every night it
automatically gets set back to Simple. Why is this happening?
Note: I have read the previous threads which discuss this problem happening
with the msdb database. But in my case, it isn't msdb - it is a USER
database.
"CadeBryant" <CadeBryant@.discussions.microsoft.com> wrote in message
news:F90570AE-4AD3-4D2F-B53C-0928E6D6FD0B@.microsoft.com...
> We have a user database on which the recovery model keeps changing to
> Simple.
> I go in every day and manually change it to Full, but nearly every night
> it
> automatically gets set back to Simple. Why is this happening?
> Note: I have read the previous threads which discuss this problem
> happening
> with the msdb database. But in my case, it isn't msdb - it is a USER
> database.
Check for any maintenance jobs, especially any that do attempt fixes on the
databases.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
|||The only maintenance jobs are for the system DBs - nothing for the user DBs.
"Greg D. Moore (Strider)" wrote:
> "CadeBryant" <CadeBryant@.discussions.microsoft.com> wrote in message
> news:F90570AE-4AD3-4D2F-B53C-0928E6D6FD0B@.microsoft.com...
>
> Check for any maintenance jobs, especially any that do attempt fixes on the
> databases.
>
> --
> Greg Moore
> SQL Server DBA Consulting
> sql (at) greenms.com http://www.greenms.com
>
>
I go in every day and manually change it to Full, but nearly every night it
automatically gets set back to Simple. Why is this happening?
Note: I have read the previous threads which discuss this problem happening
with the msdb database. But in my case, it isn't msdb - it is a USER
database.
"CadeBryant" <CadeBryant@.discussions.microsoft.com> wrote in message
news:F90570AE-4AD3-4D2F-B53C-0928E6D6FD0B@.microsoft.com...
> We have a user database on which the recovery model keeps changing to
> Simple.
> I go in every day and manually change it to Full, but nearly every night
> it
> automatically gets set back to Simple. Why is this happening?
> Note: I have read the previous threads which discuss this problem
> happening
> with the msdb database. But in my case, it isn't msdb - it is a USER
> database.
Check for any maintenance jobs, especially any that do attempt fixes on the
databases.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
|||The only maintenance jobs are for the system DBs - nothing for the user DBs.
"Greg D. Moore (Strider)" wrote:
> "CadeBryant" <CadeBryant@.discussions.microsoft.com> wrote in message
> news:F90570AE-4AD3-4D2F-B53C-0928E6D6FD0B@.microsoft.com...
>
> Check for any maintenance jobs, especially any that do attempt fixes on the
> databases.
>
> --
> Greg Moore
> SQL Server DBA Consulting
> sql (at) greenms.com http://www.greenms.com
>
>
Recovery model on user db automatically changes from Full to Simpl
We have a user database on which the recovery model keeps changing to Simple
.
I go in every day and manually change it to Full, but nearly every night it
automatically gets set back to Simple. Why is this happening?
Note: I have read the previous threads which discuss this problem happening
with the msdb database. But in my case, it isn't msdb - it is a USER
database."CadeBryant" <CadeBryant@.discussions.microsoft.com> wrote in message
news:F90570AE-4AD3-4D2F-B53C-0928E6D6FD0B@.microsoft.com...
> We have a user database on which the recovery model keeps changing to
> Simple.
> I go in every day and manually change it to Full, but nearly every night
> it
> automatically gets set back to Simple. Why is this happening?
> Note: I have read the previous threads which discuss this problem
> happening
> with the msdb database. But in my case, it isn't msdb - it is a USER
> database.
Check for any maintenance jobs, especially any that do attempt fixes on the
databases.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
.
I go in every day and manually change it to Full, but nearly every night it
automatically gets set back to Simple. Why is this happening?
Note: I have read the previous threads which discuss this problem happening
with the msdb database. But in my case, it isn't msdb - it is a USER
database."CadeBryant" <CadeBryant@.discussions.microsoft.com> wrote in message
news:F90570AE-4AD3-4D2F-B53C-0928E6D6FD0B@.microsoft.com...
> We have a user database on which the recovery model keeps changing to
> Simple.
> I go in every day and manually change it to Full, but nearly every night
> it
> automatically gets set back to Simple. Why is this happening?
> Note: I have read the previous threads which discuss this problem
> happening
> with the msdb database. But in my case, it isn't msdb - it is a USER
> database.
Check for any maintenance jobs, especially any that do attempt fixes on the
databases.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
Subscribe to:
Posts (Atom)