Thanks in Advance

Good morning!

please tell me why i got a lock with REORGANIZE?

E.g.:

– conn 1
begin tran
alter index idx_nci_orderid on Sales.OrderDetails reorganize

– conn 2
select orderid, productid, unitprice, qty, discount from Sales.OrderDetails where orderid = 10248
– locked

– conn 1
commit tran

– conn 2 – lock has been released

Why it is said that REORGANIZE would not lock resources?

Thanks!

I’m planning on implementing this on our server but afraid because of the possible loss of data.

Thanks in advance.

Thanks for the article.

I reorganize index(composite cluster index) the table(around 200GB).
After reorganize its size increased 400GB.
Could you please help me with this.

Thanks in Advance.
Any suggestion are welcome

I need clarification w.r.t rebuilding or reorganizing indexes. Based on avg_fragmentation_in_percent >5 and 30 (rebuild)

SELECT B.name as TableName,c.name IndexName,A.OBJECT_ID,avg_fragmentation_in_percent
FROM SYS.dm_db_index_physical_stats(DB_ID(),NULL,NULL,NULL,NULL) A
JOIN SYS.objects B ON A.object_id=B.object_id
JOIN SYS.indexes C ON B.object_id=C.object_id
WHERE c.name is not null

After rebuilding or reorganizing the indexes “avg_fragmentation_in_percent” remains same. This will change after rebuild or reorganizing the indexes or it will remain same?

My Full-Text search takes a long time to perform the search operation. The table on which the Full Text is enabled, contains 97 Lac records and every 1 hour 3 to 4k records are imported to this table.

During the FTS, CPU shows 100% performance on the database server with high CPU consumption of this process: MSFTESQL

The rebuilt on the full text catalog is performed every night. I also tried to do a reorganize every-night but it did’nt helped me.

Could you please guide me what should I do in this case and will Rebuild or Reorganize of FTI , boost performance.

USE DB;
GO
ALTER INDEX ALL ON dbo.mytable REBUILD
GO

error:

Msg 156, Level 15, State 1, Line 1
Incorrect syntax near the keyword ‘INDEX’.

Thank you.

Can you please explain the conditions under which SQL Optimizer uses a wrong index than what it should logically? For example, using a clustered index scan instead of using a NC which was created for that particular column. For example, I am searching for VENDORS and there is a NC index on VENDORS but SQL is using a Clustered INdex that is on an identity column.

Hemant

Small tables (for me around 200 pages) will always have high fragmentation. For these tables you don’t really gain much by having an index on them anyway.