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 |
|
bjornh
Yak Posting Veteran
87 Posts |
Posted - 2004-02-02 : 17:14:41
|
| Hi,let me explain what i mean with this title:I have a log table that logs visitor information. Every night i process these tables and put the information into presentation tables. It works 'ok' at the moment, but i want to improve the speed of writing visitors. Because the parsescript needs a couple of indexes, i came up the following solution:- create a table without indexes, this is where the writing takes place- a table with indexes (same columns), (maybe a temptable?)- copy all the data of that day into the table with indexes, run the query's and truncate the tableI am thinking of bulk insert or something, because logging this action isn't nessecary (it's the same data) or using a temp table.Is this a wise thing to do, and are there other things i might should consider?ThanksBjorn |
|
|
ehorn
Master Smack Fu Yak Hacker
1632 Posts |
Posted - 2004-02-02 : 17:38:20
|
quote: Every night i process these tables and put the information into presentation tables
What do you mean by presentation tables? |
 |
|
|
bjornh
Yak Posting Veteran
87 Posts |
Posted - 2004-02-02 : 17:45:35
|
| these are the tables that contain computed values of the collected data to gain preformance (example: 21-1-2004 | 4559 visitors | 303030 pageviews) |
 |
|
|
ehorn
Master Smack Fu Yak Hacker
1632 Posts |
Posted - 2004-02-02 : 18:00:11
|
| What is the log table structure and size, what indexes are being used?If you are experiencing hotspots as a result of indexing. Maybe you can alter your index schema. perhaps a composite index which may prevent hotspots on inserts and still be useful for parsescript functions. |
 |
|
|
|
|
|