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 |
|
Bill_C
Constraint Violating Yak Guru
299 Posts |
 Posted - 2008-07-30 : 04:59:01
|
| Ran the above on one of my tables and got the following result:-DBCC results for 'dst_table'.There are 5338 rows in 70 pages for object "dst_table".DBCC execution completed. If DBCC printed error messages, contact your system administrator.Whats the 70 pages all about? should I look at defragin the table or is it OK? |
|
|
jason7655
Starting Member
24 Posts |
Posted - 2008-07-30 : 09:00:43
|
| Well, you didn't get an error so that's a good thing.You could look at the indexes on that table and defrag those if they need it.I'm a newbie as well but I would think you could update statistics on that and then update usage to get the 70 pages down, but I'm not sure it's a huge deal.Your fill factor and Pad come into play I believe. |
 |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-30 : 21:40:04
|
quote:
Originally posted by jason7655
Well, you didn't get an error so that's a good thing.You could look at the indexes on that table and defrag those if they need it.I'm a newbie as well but I would think you could update statistics on that and then update usage to get the 70 pages down, but I'm not sure it's a huge deal.Your fill factor and Pad come into play I believe.
Don't see any reason to Defrag index. You can run DBCC showcontig to see fragmentation. |
|
|
|
|
|
|
DBCC CHECKTABLE?