Extremely large unused/reserved space for table

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 7,2000 » Administration » Extremely large unused/reserved space for...

15 posts, Page 2 of 2

««1 2

Extremely large unused/reserved space for table

Rate Topic

Display Mode

Topic Options

Author

Message

ALZDBA

Posted Tuesday, November 11, 2008 7:52 AM

SSCertifiable

Group: General Forum Members
Last Login: Wednesday, May 22, 2013 2:17 AM
Points: 6,862, Visits: 8,049

Adi Cohn (11/11/2008)

ALZDBA (11/11/2008)

I would add sp_updatestatistics to the todo list.

(I always combine dbcc updateusage (0) with count_rows and sp_updatestatistics ! )

Are you talking about sp_updatestats? If so why are you running it? AFAIK it has nothing to do with the inaccuracies in the catalog tables. Can you pleas explain the why it is better to run sp_updatestats?

Adi

Both statements alter their part of statistic information in the db.

If you update one part, you might as well update the other.

If catalog data is out of date or inaccurate , imo it is best to update the whole of it.

btw what version of sql2000 are you on ? (sp + cu/hf)

Johan

     Jul 13

Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere w00t

- How to post Performance Problems
- How to post data/code to get the best help

- How to prevent a sore throat after hours of presenting ppt ?

"press F1 for solution", "press shift+F1 for urgent solution" BigGrin

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me Hehe

Post #600678

Wandrag

Posted Tuesday, November 11, 2008 1:40 PM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Thursday, May 09, 2013 2:08 AM
Points: 505, Visits: 961

ALZDBA (11/11/2008)

Adi Cohn (11/11/2008)

ALZDBA (11/11/2008)

I would add sp_updatestatistics to the todo list.

(I always combine dbcc updateusage (0) with count_rows and sp_updatestatistics ! )

I'm running SQL2000 SP4, 64bit quad core processor.

Post #600908

jerry650-1118771

Posted Tuesday, June 23, 2009 2:32 AM

Forum Newbie

Group: General Forum Members
Last Login: Friday, February 22, 2013 11:40 PM
Points: 1, Visits: 31

http://support.microsoft.com/default.aspx?scid=kb;EN-US;924947

1. make sure every table has clustered index
2. rebuild index for every table.
3. shrink database
4. done

Post #739980

Ian Scarlett

Posted Tuesday, June 23, 2009 3:04 AM

Ten Centuries

Group: General Forum Members
Last Login: Tuesday, May 21, 2013 2:12 AM
Points: 1,322, Visits: 4,400

This is a known issue with SQL2000 on tables with BLOB columns. This KB article explains:-

http://support.microsoft.com/kb/324432

I wrestled with this problem earlier in the year, and the only solution that didn't involve dropping and recreating tables (which I didn't want to do because of the implications for merge replication) was to use dbcc shrinkfile with the "emptyfile" option:-

--add a new file to the database
ALTER DATABASE x ADD FILE(newfile,.........)
--move data from the the existing file to the new file
DBCC SHRINKFILE('oldfile','EMPTYFILE')
--now move it back
DBCC SHRINKFILE('newfile','EMPTYFILE')
--delete the new file
ALTER DATABASE x REMOVE FILE newfile

This worked, and the system was "usable" while this was running... which it wouldn't have been with the other solutions.

Post #740006

Mario Kazumassa Shimao

Posted Wednesday, December 01, 2010 5:13 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, December 01, 2010 5:07 AM
Points: 1, Visits: 3

I had a similar problem and solved using DBCC CLEANTABLE

Post #1028532

« Prev Topic | Next Topic »

15 posts, Page 2 of 2

««1 2

Permissions