Recovery mode 'magically' changing

I have a database that is the source in a logshipping pair (SQL2k,
SP3a) that is 'magically' changing from Full Recovery to Simple
Recovery. Is there a trace flag I can turn on to catch this change and
where it is being triggered from?
Obviously this is wrecking havoc on my log shipping.
thanks
Meredith RyanYou have it in the errorlog file. You can also run a profiler trace with appropriate events and
filter to catch it.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"mryan" <coffegrl@.gmail.com> wrote in message
news:1149807873.715008.262910@.i40g2000cwc.googlegroups.com...
>I have a database that is the source in a logshipping pair (SQL2k,
> SP3a) that is 'magically' changing from Full Recovery to Simple
> Recovery. Is there a trace flag I can turn on to catch this change and
> where it is being triggered from?
> Obviously this is wrecking havoc on my log shipping.
> thanks
> Meredith Ryan
>|||This isn't the master database is it?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"mryan" <coffegrl@.gmail.com> wrote in message
news:1149807873.715008.262910@.i40g2000cwc.googlegroups.com...
>I have a database that is the source in a logshipping pair (SQL2k,
> SP3a) that is 'magically' changing from Full Recovery to Simple
> Recovery. Is there a trace flag I can turn on to catch this change and
> where it is being triggered from?
> Obviously this is wrecking havoc on my log shipping.
> thanks
> Meredith Ryan
>|||No,
It is a user DB. Looks like two of my user DB's are changing. I know
that it was changed last night between 6:30pm and 9pm - After I changed
it to Full earlier in the day.
-Meredith
Roger Wolter[MSFT] wrote:
> This isn't the master database is it?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "mryan" <coffegrl@.gmail.com> wrote in message
> news:1149807873.715008.262910@.i40g2000cwc.googlegroups.com...
> >I have a database that is the source in a logshipping pair (SQL2k,
> > SP3a) that is 'magically' changing from Full Recovery to Simple
> > Recovery. Is there a trace flag I can turn on to catch this change and
> > where it is being triggered from?
> > Obviously this is wrecking havoc on my log shipping.
> >
> > thanks
> > Meredith Ryan
> >|||I don't see anything with value in the Error Log. I do see the Error:
15457... message, but with the error log only showing me a SPID I
can't track down who is making the change.
Also,. All occurances of Error 15457 show that the Advanced Config
changed from 1 to 1. Wouldn't that signify no change at all?
Tibor Karaszi wrote:
> You have it in the errorlog file. You can also run a profiler trace with appropriate events and
> filter to catch it.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "mryan" <coffegrl@.gmail.com> wrote in message
> news:1149807873.715008.262910@.i40g2000cwc.googlegroups.com...
> >I have a database that is the source in a logshipping pair (SQL2k,
> > SP3a) that is 'magically' changing from Full Recovery to Simple
> > Recovery. Is there a trace flag I can turn on to catch this change and
> > where it is being triggered from?
> > Obviously this is wrecking havoc on my log shipping.
> >
> > thanks
> > Meredith Ryan
> >|||> Also,. All occurances of Error 15457 show that the Advanced Config
> changed from 1 to 1. Wouldn't that signify no change at all?
That is just EM setting advanced option when you show properties on a server. Not related to this
problem.
Perhaps 2000 doesn't show this in eventlog, I looked at 2005. I'd do a profiler trace to see who it
is.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"mryan" <coffegrl@.gmail.com> wrote in message
news:1149868370.743087.299980@.u72g2000cwu.googlegroups.com...
>I don't see anything with value in the Error Log. I do see the Error:
> 15457... message, but with the error log only showing me a SPID I
> can't track down who is making the change.
> Also,. All occurances of Error 15457 show that the Advanced Config
> changed from 1 to 1. Wouldn't that signify no change at all?
> Tibor Karaszi wrote:
>> You have it in the errorlog file. You can also run a profiler trace with appropriate events and
>> filter to catch it.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "mryan" <coffegrl@.gmail.com> wrote in message
>> news:1149807873.715008.262910@.i40g2000cwc.googlegroups.com...
>> >I have a database that is the source in a logshipping pair (SQL2k,
>> > SP3a) that is 'magically' changing from Full Recovery to Simple
>> > Recovery. Is there a trace flag I can turn on to catch this change and
>> > where it is being triggered from?
>> > Obviously this is wrecking havoc on my log shipping.
>> >
>> > thanks
>> > Meredith Ryan
>> >
>