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.

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 Not able to Rebuild index for Large table of 240gb

Author  Topic 

venkata manohar
Starting Member

4 Posts

Posted - 2012-03-19 : 11:05:30
Hi Every body,

I've a huge DB in which one table is taking app 240gb of data. While rebuilding index for the complete db all the tables are able to get rebuilded...except the one table with 240gb of data.

It's a SQL 2008 Server and the tables have been created few years back.

What are the best possible ways to check that specific table with large data?
What could be the problem ? What to be focused in that table ?
What could be the real bug that's jamming to rebuild the index ?

Can some one suggest me with their views.

It's from PROD SER....



Thanks in advance frenss..!!


Regards
Venkat

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2012-03-19 : 11:14:10
What exactly do you mean by "While rebuilding index for the complete db all the tables are able to get rebuilded...except the one table with 240gb of data."

The 240GB table just never gets a reindex run for it?
The reindex for the 240GB table fails with an error?
The reindex runs fine but the fragmentation doesn't change?
Something else?

--
Gail Shaw
SQL Server MVP
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2012-03-19 : 12:17:03
That's some serious cheese

How do you know that the one table is that big?

How big are the other tables?

How big is your log?

How big is tempDB?

How big is the Database over all?

How many fixed drives do you have and how big are they?

How much free space do you have

What is your RAID Config?



Brett

8-)

Hint: Want your questions answered fast? Follow the direction in this link
http://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx


Want to help yourself?

http://msdn.microsoft.com/en-us/library/ms130214.aspx

http://weblogs.sqlteam.com/brettk/

http://brettkaiser.blogspot.com/


Go to Top of Page

venkata manohar
Starting Member

4 Posts

Posted - 2012-03-19 : 12:31:43
Hi shaw !

Thankyou for the reply !!

Yes ! The 240GB table just never gets a reindex run for it..!!

Haven't checked the fragmentation yet !!

What could be the possible(max) objects that needs to be checked in the table which is not allowing to perform the rebuild of index ...?

Can you provide me any script for any table to rebuild index dear shaw..

that would be really helpful to me..!!


Thanks in advance !!

Regards
Venkat





Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2012-03-19 : 12:50:36
venkata,

Are you the DBA on this database? For how long?



Brett

8-)

Hint: Want your questions answered fast? Follow the direction in this link
http://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx


Want to help yourself?

http://msdn.microsoft.com/en-us/library/ms130214.aspx

http://weblogs.sqlteam.com/brettk/

http://brettkaiser.blogspot.com/


Go to Top of Page

venkata manohar
Starting Member

4 Posts

Posted - 2012-03-19 : 12:56:50
Hi Bret !!

I'm not a DBA. Why asking my friend ? I was given this role to fill some one's position.

Regards
Venkat
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-03-19 : 13:56:58
venkata, you need to show us your script.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2012-03-19 : 16:01:05
If that table never gets reindexed then there's something in the reindex script that excludes it. Not uncommon for custom rebuild scripts to explicitly exclude the largest tables in a DB. You'll have to check over the script and see why that table is excluded.

--
Gail Shaw
SQL Server MVP
Go to Top of Page

Bustaz Kool
Master Smack Fu Yak Hacker

1834 Posts

Posted - 2012-03-19 : 17:31:25
One possible reason to look for is that tables with blob data columns (image, text, varchar(MAX), etc.) cannot be rebuilt with the ONLINE=ON option. A table as large as the one you mention could easily have this configuration. You can rebuild the index with ONLINE=OFF but you'll want to find a time when you won't mind the table being unavailable.

HTH

=================================================
It is not so much our friends' help that helps us as the confident knowledge that they will help us. -Epicurus, philosopher (c. 341-270 BCE)
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2012-03-19 : 22:05:05
quote:
Originally posted by venkata manohar

Hi Bret !!

I'm not a DBA. Why asking my friend ? I was given this role to fill some one's position.

Regards
Venkat



BECAUSE..this is not a simple gig for someone to just step in on

I mean, we are here to help, but whomever asked you to do this...well..the rest is not nice...do they like you? They MAY be setting you up

Is this Production or Development?

Make sure you have a BACKUP BEFORE you do ANYTHING

How long that would take (as well as the reorg) I have NO Idea




Brett

8-)

Hint: Want your questions answered fast? Follow the direction in this link
http://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx


Want to help yourself?

http://msdn.microsoft.com/en-us/library/ms130214.aspx

http://weblogs.sqlteam.com/brettk/

http://brettkaiser.blogspot.com/


Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2012-03-20 : 04:57:38
probably obvious, but does the "big" table have a clustered index? Seems inconceivable that a 200GB+ table wouldn't ... but ...
Go to Top of Page
   

- Advertisement -