|
Home > Archive > Microsoft SQL Server forum > September 2005 > Transaction log ???
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Transaction log ???
|
|
| jorgemiguel.paulino@gmail.com 2005-09-28, 3:24 am |
| Hi all,
Hi have a database with a huge transaction log file (plus then 13gb)
and I only have 600mb disk space left. I remove the option that allows
increasing log automatically, but there are some things that I don't
know:
1 - If we could not see the transaction log in an easy way, why he
exists?
2 - How can I delete it or how can I erase some information in order
to reduce it?
Can anyone help me?
Tanks in advance
Jorge
| |
| Simon Hayes 2005-09-28, 7:23 am |
| I don't really understand your first question, but the log is there to
ensure that all changes to the database can be rolled back/forward if
necessary, such as when the server crashes. See "Transaction Logs" in
Books Online. As for shrinking it, see here:
http://support.microsoft.com/defaul...8&Product=sql2k
If you don't need transaction log backups (see "Selecting a Recovery
Model" in BOL), then the simplest option may be to set your database to
the simple recovery model - the log will then be truncated
automatically.
Simon
| |
|
| Just to be clear. Setting the recovery model to 'Simple' will truncate
inactive portions of the log (free space within the file) automatically.
But you will still need shrink the log file at least once to reclaim the
disk space.
"Simon Hayes" <sql@hayes.ch> wrote in message
news:1127900426.992461.284090@g43g2000cwa.googlegroups.com...
>I don't really understand your first question, but the log is there to
> ensure that all changes to the database can be rolled back/forward if
> necessary, such as when the server crashes. See "Transaction Logs" in
> Books Online. As for shrinking it, see here:
>
> http://support.microsoft.com/defaul...8&Product=sql2k
>
> If you don't need transaction log backups (see "Selecting a Recovery
> Model" in BOL), then the simplest option may be to set your database to
> the simple recovery model - the log will then be truncated
> automatically.
>
> Simon
>
|
|
|
|
|