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 |
|
cat_jesus
Aged Yak Warrior
547 Posts |
 Posted - 2002-08-01 : 07:57:04
|
| I have a process that creates denormalized data in a very specific format on a database that is only about 4 Gig in size. During this process about 24 work tables are truncated and then refilled with data. This process causes the transaction log to fill up rather quickly. We don't really need to keep the tlog information for these tables since the data is transient anyway but we do need the rest of the tlog. I have been trying to figure out how to turn transaction logging off for just my process and I can't find anything. This process is too convoluted to use bulk copy or BCP(though it does use BCP at the end). The only thing I can think of at this point is to put my work tables on a different database. Are there any pitfalls I should be aware of when writing SQL that hits tables on different databases? Will I be able to do things like joins on tables in different databases? Is there some way I can turn logging off for my SP?(I'm pretty sure the answer is no but I figured, what the hell).We're running SQL 7.0 Thanks,Cat |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-08-01 : 09:32:00
|
| No, you can't turn off logging for your process. I think creating a separate staging database (with "trunc. log on chkpt." option turned on) is a way to go. You will be able to join to its tables without any problems using the 3-part naming convention (db.owner.table). |
 |
|
|
|
|
|
Avoiding the transaction log