Is the DBCC ShrinkFile command the only to keep the size fi the logs under control? Back in the version 6 days, I used to use truncate log as part of the back command but it looks like that has been discontinued.


>>So to go through 50 databases I would do something like this:
>>
>>

>>Alter Database MyDatabase Set Recovery Simple
>>Use MyDatabase
>>DBCC ShrinkFile (MyDatabase_Log,1)
>>Alter Database MyDatabase Set Recovery ?? -- set back to the original setting?
>>
>>Alter Database MyDatabase_2 Set Recovery Simple
>>Use MyDatabase_2
>>DBCC ShrinkFile (MyDatabase_2_Log,1)
>>Alter Database MyDatabase Set Recovery ??
>>
>>

>>Do I need to put "go" between the lines?
>
>Well, if you set it like that, you will not benefit from the full log, in case you would need it. In my case, I never keep it. At midnight, before the backup, it does that automatically. So, I only copy the data. But, if you really do not need the full log, yes, that could be an approach to use. There might be something simpler directly at the backup command line however. But, that would work for sure. As for the go, I do not think it is necessary here. But, you can try. If it doesn't execute, then you can insert it.