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 |
|
helpme
Posting Yak Master
141 Posts |
 Posted - 2004-11-28 : 21:05:33
|
| I have created a database with simple recovery. I tried inserting several thousand records into a table, but ran out of transaction log space. I guess I need to increase the transaction log size.My question is, why am I having problems with the transaction log space with 'simple' recovery? |
|
|
pyeoh
Starting Member
18 Posts |
Posted - 2004-11-28 : 21:26:02
|
| That's the way SQL Server is designed. All transactions are first written to the trx log, before written to the data files (which may occur later). A trx is 'committed' when it has been successfully written to the log. In a simple recovery model, the space occupied by your trxs (once they have been committed) will be overwritten by subsequent trxs. Thus, your trx log still requires enough space to hold your trx.If possible, you might consider committing your trx in batches, to reduce the size requirement of the trx log.Peter Yeohhttp://www.yohz.comNeed smaller SQL2K backups? Use MiniSQLBackup Lite, free! |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
|
|
helpme
Posting Yak Master
141 Posts |
Posted - 2004-11-28 : 22:32:50
|
| Thanks for the replies! |
|
|
|
|
|
|
more transaction log issues