Creating clustered index on exiting table

5 pts.
Tags:
SQL Server 2005
SQL Server Indexes
I have a SQL Server 2005 Enterprise Edition database table that has 768,526 rows in it with no primary key or clustered index. This database's logs are getting shipped to a disaster recovery server on an hourly basis. I need to create a clustered primary key constraint on this table; however when testing in my staging enviornment the log file gets full or I run out of disk space. What is the best approach for creating this index?
Asked: Last updated:
Related Questions
1

Answer Wiki

Thanks. We'll let you know when a new response is added.

Your only solution is to add more disk space to the database server.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • DataIsMyPassion
    I have to believe the column(s) that will be target of your primary key has data that is unique. If that is the case can you live with creating a non-clustered unique index on the column(s) ? If one of the purposes of wanting to create a primary key in the first place is to ensure row uniqueness then you will have satisfied your condition. Even if your reason is to improve performance, you will have created an index that will be the basis for retrieving data rather than retrieving from the heap. You may also want to check if your tempdb is constrained on max size. Index creation sometimes use tempdb.
    10 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: