Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sarahmfr
Posting Yak Master
214 Posts |
 Posted - 2012-01-17 : 10:50:09
|
| Hi All,I am using transactions in my database.The transaction log is increasing so quickly.What is the best way to reduce the size without loosing any information.Which backup and restore process would be the best.I am using full backup and restoration.If I did a full backup then simple back with transaction log truncate then another full backup will that workorDo a full backup,run a command to shrink the transaction log, then run another full backup. and on restoration use full restoreI am not a database admin I am just a database developer.Thanks a lot.sarah |
|
|
Peter99
Constraint Violating Yak Guru
498 Posts |
Posted - 2012-01-17 : 10:59:07
|
| I don't know what r u doing there? To decrease Transaction log file size, take transaction log backup frequently i.e. every 15 minutes. |
 |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2012-01-17 : 11:41:35
|
| Please read through this - [url]http://www.sqlservercentral.com/articles/64582/[/url]--Gail ShawSQL Server MVP |
|
|
|
sarahmfr
Posting Yak Master
214 Posts |
Posted - 2012-01-19 : 21:34:49
|
| Thank yousarah |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2012-01-20 : 05:23:50
|
| We do a transaction log backup every 15 minutes, and every 2 minutes during our housekeeping task (purge stale data and rebuild indexes)Keep an eye on your Transaction Log Backup files and see if there is a particular time of the day/week when the log backup filesizes are particularly large - that will be when you largest transaction "load" is occurring, and you can then consider how you reduce that "load" |
|
|
|
|
|
|
Huge log file