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 |
sqldba20
Posting Yak Master
183 Posts |
Posted - 2008-04-04 : 07:56:09
|
Folks:I have a table with almost 3 million records and 260 columns. An update (lots of joins) for 1 Month data takes around 35 to 40 mins (updates around 300K records) but If I issue the same update for 4 months data it takes around 7 to 8 hours. Has this anything to do with Index fill factor. The table fill factor is 90%. Thanks ! |
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-04-04 : 09:51:23
|
This is the problem of denormalization of table. Update/inserts are affected. You should normalize this table(260 column OMG!!). We don't have column greater than 15(max) in our table. |
 |
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2008-04-04 : 10:23:41
|
Could you perhaps post the table structure, the indexes you have on that table and the update statement?ThanksGail Shaw--Have a nice day, unless you have other plans |
 |
|
tosscrosby
Aged Yak Warrior
676 Posts |
Posted - 2008-04-04 : 13:35:47
|
Gail - Weird to see you as a "Starting Member" in a SQL forum!Terry |
 |
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-04-05 : 00:10:34
|
>> Has this anything to do with Index fill factor.Check page split per second in perfmon. If that number is high, you may need smaller fill factor. Also check update statement's executin plan. |
 |
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-04-05 : 12:38:33
|
Usually for high update/insert table ,it is better to set index fill factor 60-70,but i wouldn't recommend that.It will affect other select query. Normalization will be best option for you |
 |
|
|
|
|