I have a database here that's 3.3 GB that has a transaction log of 14.8 GB.
We want to make the log WAY smaller. like doing a checkpoint or backup with
log truncation or something.
Got some BOL / code snips for us?
Peace & happy computing,
Mike Labosh, MCSD
"When you kill a man, you're a murderer.
Kill many, and you're a conqueror.
Kill them all and you're a god." -- Dave MustaneThere's some info about log file shrinking in here:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Mike Labosh" <mlabosh@.hotmail.com> wrote in message news:up96UXaBGHA.4016@.TK2MSFTNGP11.phx
.gbl...
>I have a database here that's 3.3 GB that has a transaction log of 14.8 GB.
> We want to make the log WAY smaller. like doing a checkpoint or backup wi
th log truncation or
> something.
> Got some BOL / code snips for us?
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "When you kill a man, you're a murderer.
> Kill many, and you're a conqueror.
> Kill them all and you're a god." -- Dave Mustane
>|||How to truncate the Transaction Log:
http://msdn.microsoft.com/library/d...r />
_7vaf.asp
And just as important; why your transaction log may grow to a large size
between backups and how to minimize it's growth:
http://support.microsoft.com/kb/317375/
http://support.microsoft.com/defaul...kb;en-us;873235
"Mike Labosh" <mlabosh@.hotmail.com> wrote in message
news:up96UXaBGHA.4016@.TK2MSFTNGP11.phx.gbl...
>I have a database here that's 3.3 GB that has a transaction log of 14.8 GB.
> We want to make the log WAY smaller. like doing a checkpoint or backup
> with log truncation or something.
> Got some BOL / code snips for us?
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "When you kill a man, you're a murderer.
> Kill many, and you're a conqueror.
> Kill them all and you're a god." -- Dave Mustane
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment