i have read one your article What is the best value for the Fill Factor? – Index, Fill Factor and Performance – Part 2
where you have explained one approx fill factor criteria. I have a query regarding cluster index. I have a table where my cluster index is on a unique column but all other columns in this table are updated through out the process.(Appx 15-20 times or more a day) Should I keep fill factor to 100 as per the unique index or should i make it somewhere in between 70-90 as data is contineously updating in this table.

Basicly I want to know what we need to do with Fill factor if my unique queue where we have the clustered index is not changing but all the rest columns are updating contioneously.

I am using SQL Server 2005 and index frag is 66.67% all the time. I tired drop/create and reorganize and rebuild the indexes. but still the total fragmentation is 66.67%. How to reduce it.

Thanks!

Amit Kumar

Is there any difference between Alter Index ..Rebuild and
DBCC DBREINDEX ?

I think this is confusing please get it corrected from second line where it says rebuilding.. It conrtadicts

Heavily fragmented indexes can degrade query performance and cause your application to respond slowly. I prefer Index Rebuilding is required if Index is fragmented more than 10%. Reorganizing an index de-fragments the leaf level of clustered and non-clustered indexes on tables and views by physically reordering the leaf-level pages to match the logical order (left to right) of the leaf nodes.

I have huge database around 2 tb all most of the tables are partioned.

1. Rebuilding an index at partition level is better or the whole table.

2. If I have to rebuild all partition

is it better by giving partition # like below

ALTER INDEX IX_TransactionHistory_TransactionDate
ON Production.TransactionHistory
REBUILD Partition = 5;
GO

or

ALTER INDEX IX_TransactionHistory_TransactionDate
ON Production.TransactionHistory
PARTITION = ALL

Is the second option is same as rebuild index on the whole table or it goes one partition at a time.

Could please provide me the archiecture of sqlserver2005.

I just want to know how it works

I am facing a problem while rebuilding or reorganising a few of my DB inedexes. My Environment is SQL Server 2005 and I am using “ALTER INDEX ….” command.
These indexes remain “Fragmented” even aftre rebuilding or reorganising severl time.
Can you please tell me what could be the reasons?

With Regards,

M Azim

This is a the latest version of this script as of 2008-11-12:

What are your thoughts on this post from Kalen Delaney?

http://sqlblog.com/blogs/kalen_delaney/archive/2008/02/28/fragmentation-revisited.aspx

Excerpts:
“Fragmentation is really only an issue if there are LOTS of pages. I usually say that if there are less than 100 pages, you should never worry about fragmentation. However, this this whitepaper suggests that a better cutoff would actually be 1000 pages: (link)” See orig post for actual link.

“REBUILD doesn’t seem to make a difference in the avg_fragmentation_in_percent value is when there are too few pages in the table.”

Thanks,
WCM

i heared alot abt u. impressive….
i am working in dubai. we are havinf problem related to Database Performance. Few days before, we upgraded the sql server. we moved our database from sql server 2000 to sql server 2005 by restoring the backup of SQL server 2000 on SQL Server 2005. we are having a web site which is using this Database. The database was working normally on sql server 200 but after we moved, its dead slow…i mean the over all performance of DB is very slow..we reindex the Database again in SQL Server 2005 but no use…its still same…

Just wanna know, is there any setting in SQL Server 2005 after restoring database from SQL Server 2000???
i mean can u help me which step i am missing ???

hope to have your reply soon

Regards

BASHARIT

to find fragmented indexes

SQL SERVER 2000:
DBCC SHOWCONTIG was used to find index fragmentation. In SQL SERVER 2005 it is deprecated and replaced by query to sys.DM_DB_INDEX_PHYSICAL_STATS.

SQL SERVER 2005:
SELECT query to sys.DM_DB_INDEX_PHYSICAL_S…

After reading your post I wanted to point something out. You said:

“I have been asked following two questions many times:
1) What is difference between FILLFACTOR = 0 AND FILLFACTOR = 100?
They are SAME.”

I cannot speak on behalf on SQL 2005 but with SQL 2k this is not an entirely a true statement as there is a difference between the two.

FILLFACTOR = 100 is 100% fill rate and is generally a bad idea.

FILLFACTOR = 0 is a wildcard for whatever the existing fill factor on the index was set to previously.

If the index previously had a FILLFACTOR of 100 then this statement would be true as the fill rate would be 100%.

However if the index had a FILLFACTOR of 90 and a FILLFACTOR = 0 was used, the fill rate of 90% would be retained.

I use a FILLFACTOR of 0 almost exclusively when reindexing a database, as FILLFACTOR’s on index should be individually tuned based on types of activity in that particular table. I would not want to change those values when doing a bulk reindex of a database.

DECLARE @Database VARCHAR(100)
DECLARE @Table VARCHAR(100)
DECLARE @cmd NVARCHAR(300)
DECLARE @fillfactor INT

SET @fillfactor = 70
SET @Database = ‘TestOnly’

SET @cmd = ‘DECLARE TableCursor CURSOR FOR SELECT table_catalog + ”.” + table_schema + ”.” + table_name as tableName
FROM ‘ + @Database + ‘.INFORMATION_SCHEMA.TABLES WHERE table_type = ”BASE TABLE”’

EXEC (@cmd)
OPEN TableCursor

FETCH NEXT FROM TableCursor INTO @Table
WHILE @@FETCH_STATUS = 0
BEGIN

SET @cmd = ‘ALTER INDEX ALL ON ‘ + @Table + ‘ REBUILD WITH (FILLFACTOR = ‘ + CONVERT(VARCHAR(3),@fillfactor) + ‘)’
EXEC (@cmd)

FETCH NEXT FROM TableCursor INTO @Table
END

CLOSE TableCursor
DEALLOCATE TableCursor

Error messages:
The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active. shud i try to defragment it, how can i defragment it.plz give me a long term solution bcoz branches are going to increase like anything… do u have any contact no. its urgent

The value returned for avg_fragmentation_in_percent from
sys.dm_db_index_physical_stats is Percent or .%

i.e. if .01 is returned is that .01% or 10% ?

Thanks,
Paul

Well it worked for me …

I created a table with a primary key, which create a clustered index by default and then I checked the fragmentation level using the command given by Dave, I saw the level was 0 (Zero)

Then I inserted 12000 rows in the table, then I saw the index fragmentation level was 20 % , and then I executed the second query,

Instantly my index fragmentation level became 0 %.

Worked for me … !

Whats the difference between rebuild and reorganize? Do they just run at different speeds or is there some other difference between them.

Cheers,
Aaron

ALTER INDEX ALL ON dbo.Mail_Messages
REBUILD WITH (FILLFACTOR = 90, SORT_IN_TEMPDB = ON,
STATISTICS_NORECOMPUTE = ON)

I executed the above statement but my fragmentation is still over 85%. I have used the rebuild and reorg in the maintenance plan also and I cannot get my fragmentation to reduce.

Any suggestions?

Thanks