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 |
|
cancer192
Starting Member
10 Posts |
 Posted - 2009-07-02 : 04:34:31
|
| Hi,I was trying to archive almost 13 millions of records into another db when i encountered with this error:"The transaction log for database 'Original' is full."And so I decided to archive it by smaller chunks instead of the whole lot in one go and below are my statistics:Column header:Attempt #: Original record # | Original DB size | Archive DB size | Orginal_log size | Archive_log sizeData:Initial: 12726180 | 3.59GB | 338MB | 1024KB | 1024KB1st: 11726180 | 3.59GB | 700MB | 984MB | 739MB2nd: 10726180 | 3.59GB | 989MB | 984MB | 739MB3rd: 9726180 | 3.59GB | 1.24GB | 984MB | 739MB4th: 8726180 | 3.59GB | 1.53GB | 984MB | 739MB5th: 7726180 | 3.59GB | 1.81GB | 984MB | 739MB6th: 6726180 | 3.59GB | 2.09GB | 984MB | 739MB7th: 5768900 | 3.59GB | 2.36GB | 984MB | 739MB8th: 4768900 | 3.59GB | 2.64GB | 984MB | 739MB9th: 0 | 3.59GB | 3.99GB | 4.41GB | 3.65GBFrom the above, is it normal for Original_log and the Archive_log to not grow in size when I was archiving it for every 1 million records? And finally the size shoots up in the last archive? |
|
|
|
|
|
DB log file gets full when archiving