<div>
<a href="http://doc.ddart.net/mssql/sql70/sp_da-di_4.htm" rel="ugc">http://doc.ddart.net/mssql/sql70/sp_da-di_4.htm</a><br />
<br />
to activate the full recovery mode:<br />
exec sp_dboption 'trunc. log on chkpt.', 'FALSE' <br />
<br />
to activate the simple recovery mode:<br />
exec sp_dboption 'trunc. log on chkpt.', 'TRUE'<br />

</div>


http://doc.ddart.net/mssql/sql70/sp_da-di_4.htm [http://doc.ddart.net/mssql/sql70/sp_da-di_4.htm]

to activate the full recovery mode:
exec sp_dboption 'trunc. log on chkpt.', 'FALSE'

to activate the simple recovery mode:
exec sp_dboption 'trunc. log on chkpt.', 'TRUE'


<div>
Aneeshattingal,<br />
<br />
That was EXACTLY what I was looking for. &nbsp;Thanks!
</div>


Aneeshattingal,

That was EXACTLY what I was looking for.  Thanks!

<div>
<div class="content wysiwyg-content">
Here's my situation: &nbsp;I have a developer who consistently forgets to reset the recovery model to Full after he works on his database (usually when he restores or if he changes models just for speed sake). &nbsp;Unfortunately, the DB server he's working with houses about 40 other databases. &nbsp;His is by far the largest, and the transaction log for him alone gets to the point where it chokes the server and brings down other DB's.<br />
<br />
Ideally what I would like to do is set up a job that runs every night before the backup runs that changes the recovery model on any user databases (or even specific ones if I have to) via a stored procedure, etc.<br />
<br />
Can anyone point me in the right direction? &nbsp;It would save immense amounts of grief.<br />
<br />
Thanks!
</div>
</div>


Here's my situation:  I have a developer who consistently forgets to reset the recovery model to Full after he works on his database (usually when he restores or if he changes models just for speed sake).  Unfortunately, the DB server he's working with houses about 40 other databases.  His is by far the largest, and the transaction log for him alone gets to the point where it chokes the server and brings down other DB's.

Ideally what I would like to do is set up a job that runs every night before the backup runs that changes the recovery model on any user databases (or even specific ones if I have to) via a stored procedure, etc.

Can anyone point me in the right direction?  It would save immense amounts of grief.

Thanks!

Is there a way to programmatically change the recovery model on user DB's in MS SQL Server 2000?

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.