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 |
|
rkc01
Starting Member
43 Posts |
Posted - 2002-03-15 : 13:08:55
|
| I have a 6.5 table that won't defrag regardless of wether I run dbreindex or I drop and recreate the index. There are 2 non clustered indexes. Has anyone else ever experienced this? Any suggestions? thxs,rob |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-03-15 : 13:25:49
|
| Can you add a clustered index? Drop the non-clustered ones first, create the clustered index, and re-create them. That should clear it up. |
 |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-03-15 : 16:46:43
|
| What's an average length of a row in your table? If your average row takes up just over half a page, there will always be a lot of fragmentation as SQL Server will not be able to place more than a single row on a page (thus wasting the remaining space). If this becomes a big problem for you, you could vertically partition your data (move some columns to a separate table). |
 |
|
|
rkc01
Starting Member
43 Posts |
Posted - 2002-03-15 : 21:58:44
|
quote: Can you add a clustered index? Drop the non-clustered ones first, create the clustered index, and re-create them. That should clear it up.I can't. It's not my database. It's part of a payroll package that we distribute, (but we didn't design the app or the database). If I change it, the company we distribute for won't support it.
|
 |
|
|
rkc01
Starting Member
43 Posts |
Posted - 2002-03-15 : 22:02:49
|
quote: What's an average length of a row in your table? If your average row takes up just over half a page, there will always be a lot of fragmentation as SQL Server will not be able to place more than a single row on a page (thus wasting the remaining space). If this becomes a big problem for you, you could vertically partition your data (move some columns to a separate table).That was one of the first things I looked at. The rows aren't nearly long enough to cause it.
|
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-03-16 : 16:46:59
|
quote: I can't. It's not my database. It's part of a payroll package that we distribute, (but we didn't design the app or the database). If I change it, the company we distribute for won't support it.
If this is causing a performance issue that is unacceptable for you, I would suggest you contact the developers and have them address the problem. The way I see it, if they don't fix it, they're not supporting you anyway...which may also violate their software license agreements with you and others...so their threat of pulling support is pretty empty. |
 |
|
|
|
|
|
|
|