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 |
|
jhunt
Starting Member
21 Posts |
 Posted - 2003-07-09 : 01:38:16
|
| We have some package software and we send out an update file to all our customers with information on banks and branches. That information is updated on their SQL Server/MSDE (7 or 2000) using bulk insert statements within a transaction.(Actually a nested transaction- thats bad isn't it?)Anyway recently the log files on some of those users databases have been getting huge, in one case 2GB. I think that it is due to the nested transaction. My question is, how can i keep that log file to a reasonable size? Is there some SQL server setting I can use, or do I just run some tidy up code after the bulk inserts have run?(Remember the customer may not have Enterprise Manager and even if they do, can't be relied on to know how to use it.)ThanksJustin |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2003-07-09 : 03:19:37
|
| What logging settings are on the database? If it is on full logging and you do not need point in time recovery, try setting the logging to simple or bulk logged. -------Moo. |
 |
|
|
|
|
|
Keeping log files small