Aight, so I added a full text catalog and a full text index for one specific column and table in my database.
Now the issue is, whenever I rebuild it, it locks the full text index forever, making it unsuable. Now, there are only 30,000 records i need to search, so it isn't like there is this massive amount of data. What am I doing wrong to where it is locking the index and disallowing me to use the stored procedure that does the searching?
The indexes have changed in SQL Server 2005 but it places locks on the table or column during rebuilds that is the reason to schedule the now discontinued index related DBCC statements to run at night or when ever is a slow time for your users. There are some access restrictions during rebuild so, you may want to plan and use the new tuning advisor. In previous versions I know if needed you can count the IAM (index allocation mapping) pages and Extents so you can prevent related performance issues. Try the link below for the new index rebuild information. Hope this helps.
http://msdn2.microsoft.com/en-us/library/ms188388.aspx
|||today we got a messagge like full text index is corrupt.Do u know why does this happen?
PS: we did send TRUNCATE TABLE COMMAND to the table that had the index...is it a problem?
sql
No comments:
Post a Comment