Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Transaction log
- Thread starter hameja
- Start date
In Query Analyzer run this command, and it shows you, where the log file is:
EXECUTE sp_helpdb 'your_database_name'
You have to backup your transaction log
or shring database ( free up alocated unused space )
DBCC SHRINGDATABASE
(
your_database_name
)
Zhavic
---------------------------------------------------------------
In the 1960s you needed the power of two Comodore64s to get a rocket to the moon. Now you need a machine which is a vast number of times more powerful just to run the most popular GUI.
EXECUTE sp_helpdb 'your_database_name'
You have to backup your transaction log
or shring database ( free up alocated unused space )
DBCC SHRINGDATABASE
(
your_database_name
)
Zhavic
---------------------------------------------------------------
In the 1960s you needed the power of two Comodore64s to get a rocket to the moon. Now you need a machine which is a vast number of times more powerful just to run the most popular GUI.
- Thread starter
- #3
Just run a backup and it will fix you for now.
The log file is probably in the same directory as your data files but technically it could be anywhere. Check the properties page of the database to see the actual path.
What you want to do to fix this for good depends.
First of all are you running SQL 7 or above? If so you are probably running out actual disk space as well as filling the log because the default is to grow that file automatically.
Basically though you need to decide if you want to perform "Log" backups on this database. They allow you to perform quick backups that only record the changes to the database since the last full or log backup.
If you don't want to do that you can check the database option to "truncate log on checkpoint". That will keep the logs from growing.
Just performing a regular backup will also do the trick.
The log file is probably in the same directory as your data files but technically it could be anywhere. Check the properties page of the database to see the actual path.
What you want to do to fix this for good depends.
First of all are you running SQL 7 or above? If so you are probably running out actual disk space as well as filling the log because the default is to grow that file automatically.
Basically though you need to decide if you want to perform "Log" backups on this database. They allow you to perform quick backups that only record the changes to the database since the last full or log backup.
If you don't want to do that you can check the database option to "truncate log on checkpoint". That will keep the logs from growing.
Just performing a regular backup will also do the trick.
- Status
Similar threads
- Locked
- Question