.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Post New Web Links

Index Rebuild in SQL 2005

Posted By:      Posted Date: October 13, 2010    Points: 0   Category :Sql Server
 

I am doing a single pk index rebuild on a 100 gig table.  After running sp_who2, I see that the rebuild in suspended state.  Over a period of time, I have noticed that neither disk io nor cpu io is changing.   Is there a way for me to cancel it?  Is it frozen forever?

Any help is appreciated 




View Complete Post


More Related Resource Links

Maintenance plan to rebuild Full-text index ? (SQL 2005)

  
Is it possible, through the GUI Wizard, to create a Maintenance plan that rebuilds (rather than reorganise/optimise) a Full text index in 2005 ? The full text index is based on one table only - so would using the "Rebuild index task" in the Wizard do the trick ? I wouldn't mind if the other indexes on the table were rebuilt too, but main concern in the Full text Index. If not - then I guess it would be a scheduled job which does a ALTER FULLTEXT CATALOG catalog_name REBUILD, but I thought it would be nice to keep it within the - Management - Maintenance plans - section of SQL Management Studio. Also - should this be preceeded with a transaction log backup ? Had some issues rebuilding them last night - seemed a Log backup was needed.

index rebuild (offline) on sql 2005 sp3 enterprise causes drastics growth of the database size(mdf)

  

index rebuild (offline) on sql 2005 sp3 enterprise causes drastics growth of the database size(mdf)

database grew from 40 GB to 500 GB. space is reserved no free space to reclaim after reindex completes.

pls guide


Rebuild index failed

  
I scheduled a maint plan to rebuild index. All table's indexes are successfully built except for one table. The error message I got:   Failed:(-1073548784) Executing the query "ALTER INDEX [Index_name] ON [dbo].[table] REBUILD WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY  = OFF, ONLINE = ON )" failed with the following error: "Online index operations can only be performed in Enterprise edition of SQL Server.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. Can someone tell me what the problem is and how to fix it? Thanks.

Where are the index rebuild transactions stored during an online index rebuild with SORT_IN_TEMPB se

  
I am reposting this from another forum. In this article http://msdn.microsoft.com/en-us/library/ms184246(v=SQL.100).aspx, it is stated that "The index transactions will be stored in the tempdb transaction log, and the concurrent user transactions will be stored in the transaction log of the user database. This allows for the transaction log of the user database to be truncated during the index operation if it is required." However, this doesn't seem to be the case for me. I am running Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) on a Windows Server 2008 x64 EE server in FULL recovery mode with all user databases set to 100 for their compatibility mode.  The server has 48GB of ram.  I have a nightly job that runs ALTER INDEX REBUILD or ALTER INDEX REORGANIZE for each index in a user database. The SP called by the job determines if the table has any underlying LOB datatypes and if so will not attempt an online rebuild, it also determines whether to rebuild or reorganize based off the fragmentation percentage of the index and does not use explicit transactions.  There are almost no concurrent user transactions running when I run the index rebuild job.  Each night, the user database log blows up during the index rebuild job (or it would if I didn't have a job in place that checked the amount of used space in the log and cancelled the inde

Does a Maintenance Plan "Rebuild Index" task on Tables + Views rebuild the full text indexes ?

  

As subject really.

I'm talking about a complete rebuild - not an incremental, or a re-organise.

SQL 2005

The full text indexes are only on individual tables, not Views.

I've asked a similar question before, but sufficiently different, and other is marked as Answered so thought I'd open a new Q : http://social.msdn.microsoft.com/Forums/en/sqltools/thread/5f17f4f1-fba9-436f-aedf-cfbfd89c8db2)

TIA


SQL Server 2005 rebuild indexes find corruption or cross linked files

  

Does anyone know if this is a known issue? What do you do when this happens? We had to go to a good backup from 3 days prior.

From the application log it appears there were cross linked files. Is this caused by the OS or Sql Server?

Pat M

Reno


PatM Reno

SQL 2005 Merge Replication : sysmergepublications unique index 'nc1sysmergepublications' fails

  
I've got one SQL 2005 SP2 server setup as Publisher and distributor which replicates through Merge pull subscriptions on SQL 2000 SP4 machines. Some of these SQL 2000 machines does republishing too. However, after a columndrop on one of the articles at the SQL 2005 machine by using sp_repldropcolumn the whole subscription sync came down on me with failures all over. All had the same error :

"Cannot insert duplicate key row in object 'dbo.sysmergepublications' with unique index 'nc1sysmergepublications'"
This procedure was called by sp_MScreateglobalreplica.

I have found that there are invalid publications in sysmergepublications, but only on publishers for the SQL 2000 subscription machines(excluding valid republishing publications). Deleting these pubID's does not help at all. With the first sync of any pull subscription (after the delete) they re-appear on the SQL 2005 machine.

However, I need to get the pull subscriptions going again. How can I clean the system tables to prevent any errors like above or duplicate keys in the sysmergesubscription table... Please do not recommend an overhaul. I need step by step procedures to get it going.

Rebuild Index Error -1073548784

  

I am getting the following error on Rebuild Index Maintenance Task.

"Executing the query "ALTER INDEX [PK_cartrige] ON [dbo..." failed with the following error: "A severe error occurred on the current command.  The results, if any, should be discarded.
A severe error occurred on the current command.  The results, if any, should be discarded.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly."

Where can i find more details on troubleshooting this error and find more details on the error. It seems to be a persistant problem since sql server 2005.

Details:

  1. -Maintenance Plan has been working well for months.
  2. -Std Edition Sql Server 2008
  3. -Db Integrity check successfull
  4. -sort result in tempdb is off
  5. -keep index online while reindexing is off
  6. -local server connection works for all other jobs prior to the task

Rebuild Index and Update Column Statistics

  

As Index rebuild process will create and update stats, we should not update stats as the row sampling would be less than ideal. However, here is my question. Would a column Stats need to be updated after a Index Rebuild.

If yes, why, if no why. Please provide some documentation to get a better understanding of this with the help of an example. 

Thank you.


SQL 2005 Inserting into Cluster vs. Non Clustered index table

  

All things being equal, when inserting data into cluster indexed table, assuming I am inserting in the order of clustered index, is there a difference how sql server will fill in the physical pages compared to if the inserted table had only non-clustered index? 

On a different subject, is the physical location of data on a page effects query performance?  If so, how?

Thanks in advance


Maintenace Plan - Index online rebuild failed

  

Hi,

on my sql 2008, using Wizard, I created a Maintenance Plan with one of the tasks - to rebuild indexes online. It is important for us that indexes are rebuilt online.

I've got the following error:

Executing the query "ALTER INDEX [aspnet_Membership_index] ON [dbo].[aspnet_Membership] REBUILD WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, SORT_IN_TEMPDB = OFF, ONLINE = ON )
" failed with the following error: "Online index operation cannot be performed for index 'aspnet_Membership_index' because the index contains column 'Comment' of data type text, ntext, image, varchar(max), nvarchar(max), varbinary(max) or xml. For non-clustered index the column could be an include column of the index, for clustered index it could be any column of the table. In case of drop_existing the column could be part of new or old index. The operation must be performed offline.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

What are my options?

thank you!


Index Rebuild failing with sql error msg 8966, level 16, state 2, line 20

  

Working with a customer trying to help him re-index his database. Database is a little over a terabyte and I gave him a re-indexing script to run on his SQL Server 2005 Enterprise server.

FYI
It had been recommended by a 3rd party load testing company that all of our re-indexing be done in "offline" mode so the re-indexing was done in offline mode for this customer.

The first reindex attempt stopped with a "severe" error message in the "query window" when sql reached the largest table in the system, which I found out contains about 29 milliion rows. The previous indexes had been successfully rebuilt or reorganized based on the percentage of fragmentation.

I asked for the sql error logs and found the "severe" error message written to the log around the time of a "sql server restart". I asked the customer and he admitted to restarting sql server. I suspected that the reindex script had not completed but could not be sure.

I decided to approach it next by rebuilding the index on the huge table only. He called me the next day and told me the rebuild had failed. He sent me the error logs and he also informed me he had killed the index query after it had been running for over 24 hours.

I found some IO errors in the sql error logs referring to "15 seconds" had been exceeded a

SQL Server 2005 Transactional Replication Fails to Publish Stored Procedure Containing an Index Crea

  

I've experienced a bizarre problem with a SQL Server 2005 Transactional Publication. The issue is this: If the publication contains an article that is a stored procedure that contains a create index statement, then there is an error thrown when attempting to replicate the schema of the stored procedure to a subscriber.

The behavior is very odd, because even if the create index statement is commented out, it still gives the exception, and it will only work if it is removed altogether.

Here is the exact error that's being returned:

Command attempted: GRANT EXECUTE ON [dbo].[usp_Test] TO [CompanyDatabase_access]

(Transaction sequence number: 0x00000170000008B9000500000000, Command ID: 5)

Error messages: Cannot find the object 'usp_Test', because it does not exist or you do not have permission. (Source: MSSQLServer, Error number: 15151) Get help: http://help/15151 Cannot find the object 'usp_Test', because it does not exist or you do not have permission. (Source: MSSQLServer, Error number: 15151) Get help: http://help/15151

The error is accurate, because when I check on the subscriber, the stored procedure wasn't created as expected... but that was the purpose of the publication...

Rebuild index

  
I Rebuild index on the table when Fragementation occurs then i have one doubt that is when we do the rebuild and reorganize on the table, what is the priority of locks on the table.

How to Encrypt and Decrypt a Password using SQLSERVER 2005?(Video)

  
Encypt and Decrypt a Password using SQLSERVER 2005(Video)

SQL Server 2005 Try and Catch Exception Handling

  
I'm pretty excited to see that there is some real error handling for T-SQL code in SQL Server 2005. It's pretty painful to have your wonderfully architected .NET solution tainted by less-than-VBScript error handling for stored procedures in the database. The big difference being the addition of TRY..CATCH blocks. Let's take a look:

sql server 2000 vs 2005

  

i would like to ask what the difference between sql server 2000 and 2005 


Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend