Drop Table

Support Forum for database administrators and web based access to important newsgroups related to databases
Register on Database Support Forum Edit your profileCalendarFind other Database Support forum membersFrequently Asked QuestionsSearch this forum -> 
For Database admins: Free Database-related Magazines Now Free shipping to Texas


Post New Thread










Thread
Author

Transaction log ???
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


Report this thread to moderator Post Follow-up to this message
Old Post
jorgemiguel.paulino@gmail.com
09-28-05 08:24 AM


Re: Transaction log ???
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


Report this thread to moderator Post Follow-up to this message
Old Post
Simon Hayes
09-28-05 12:23 PM


Re: Transaction log ???
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:
>
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;272318&Product=sql2k[/ur
l]
>
> 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
>



Report this thread to moderator Post Follow-up to this message
Old Post
Danny
09-28-05 12:23 PM


Sponsored Links





Last Thread Next Thread
Post New Thread

Microsoft SQL Server forum archive

Show a Printable Version Email This Page to Someone! Receive updates to this thread
Microsoft SQL Server
Access database support
PostgreSQL Replication
SQL Server ODBC
FoxPro Support
PostgreSQL pgAdmin
SQL Server Clustering
MySQL ODBC
Web Applications with dBASE
SQL Server CE
MySQL++
Sybase Database Support
MS SQL Full Text Search
PostgreSQL Administration
SQL Anywhere support
DB2 UDB Database
Paradox Database Support
Filemaker Database
Berkley DB
SQL 2000/2000i database
ASE Database
Forum Jump:
All times are GMT. The time now is 12:38 PM.

 
Mobile devices forum | Database support forum archive




Copyrights DropTable.com Database Support Forum 2004 - 2006