Skip to main content

What is Fill Factor in SQL Server

Fill Factor works in performance tuning area, for the index the most important property is Fill Factor. Fill Factor responsible to determine the percentage of space on each leaf-level page to be filled with data. As we know page is smallest unit of SQL server which size is 8k. Every page cans one or more than one row which is depending on size of row.

The Fill Factor specifies the % of fullness of the leaf level pages of an index. When an index is created or rebuild then filled up pages with data depend on Fill Factor. For example if we create an index and put the  value of Fill Factor is 70 then pages will filled up with data 70% other 30% space will be remain.

For Example, I am creating a Temp named table for testing of Index with Fill Factor.


CREATE TABLE Temp
(
       id INT IDENTITY(1,1),
       Name VARCHAR(100)
)

DECLARE @count INT=100000;
WHILE (@count>0)
BEGIN
       INSERT INTO Temp
       VALUES('SQL Server tutorial by codefari.com Type'+CONVERT(VARCHAR(100),@count))
       SET @count=@count-1
END

SELECT COUNT(*) FROM Temp




Now run following script


EXEC sp_spaceused 'dbo.Temp'



Result Set





High Fill Factor value

You can see index size 8kb and unused 8kb both are same, because we did not create any index on this table.

Now see following scrip I am creating a non-clustered Index with Fill Factor 100%




USE [Test]
GO

/****** Object:  Index [Name]    Script Date: 11/27/2015 6:34:53 PM ******/
CREATE NONCLUSTERED INDEX [Name] ON [dbo].[Temp]
(
       [Name] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF,
 DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON,
 FILLFACTOR = 100) ON [PRIMARY]
GO




Again run following script



EXEC sp_spaceused 'dbo.Temp'




Result Set






Here Index size become 6404 kb and unused 176kb. Here we have taken Fill Factor 100%. 
Note: You may choose high Fill Factor value if there is very little or no changes the underlying table's data. Means if you have an index that is constantly changing you would want to have a lower value to keep some free space available for new index entries.  Otherwise SQL Server would have to constantly do page splits to fit the new values into the index pages.

Low Fill Factor value
Now if we put value of Fill Factor as 50% then what will happen you may see in following example.
Drop the created index first and run the following script again.

USE [Test]
GO

/****** Object:  Index [Name]    Script Date: 11/27/2015 6:34:53 PM ******/
CREATE NONCLUSTERED INDEX [Name] ON [dbo].[Temp]
(
       [Name] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF,
 DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON,
 FILLFACTOR = 50) ON [PRIMARY]
GO


Again run the following script

EXEC sp_spaceused 'dbo.Temp'


Result Set





Now here you can see index_size is 12544kb and unused 248kb.



Note: With new data records added, the index pages need to have sufficient space to take the new entries. When there is not enough space a page split needs to occur which could impact performance depending on how frequently page splits need to occur.
 


Popular posts from this blog

Query to find stored procedures by nested stored procedure name

Problem: Suppose we have a stored procedure which has been used in several stored procedure, I mean stored procedure usp_proc1 is nested in many stored procedures like below
BEGIN DECLARE@ResultTABLE ( IDINT, NAMEVARCHAR(50), [ADDRESS]VARCHAR(255) ) INSERTINTO@Result EXECusp_proc1@Name='codefari' END
So I want to find all those queries who containing usp_proc1
Solution: There is a lot of solutions, I'm giving some of them below. If you want to get the only name of the stored procedures then use the following query. Using join query on system tables syscomments and sysobjects we can get the stored procedures name which containing the particular table, nested procs or any other string.
SELECTDISTINCTo.name FROMsyscommentss INNERJOINsysobjectsoONs.id=o.id

Check for changes to an SQL Server table?

Problem: Suppose your team is working on the under-development project so it might be possible continuous work on the database and perform changes in Table, Stored procedure as per requirement, and daily you have to update the testing server database as per changes are done in developing server database then how it is possible to trace those changes. There are a lot of solutions for this problem which is listed below Solution 1: For SQL Server 2000, 2005 and above use the CHECKSUM command SELECTCHECKSUM_AGG(BINARY_CHECKSUM(*))FROMYour_Table_NameWITH (NOLOCK); That will return the same number each time its run as long as the table contents haven't changed. Unfortunately CHECKSUM does not work always properly to detect changes. It is only a primitive checksum and no CRC calculation. Therefore you can't use it to detect all changes, e. g. symmetrical changes result in the same CHECKSUM! Solution 2: 1.Run the following query. Before executing query replace DB_Name with your database name…

Merge and Merge join transformation in SSIS

MERGE TRANSFORMATION
Using Merge Transformation we can combine two sorted data-set into single data-set basically Merge Transformation used to combines rows from two sorted data flows into one sorted data flow. Following tasks you may perform using Merge Transformation: 1.Suppose we have a scenario like, we need to merge data from a database table and excel means we want to merge data from two different data sources. For such type of scenario, you can use Merge Transformation. 2.If we want to merge data from two same structured tables but exists two different servers. 3.Sometimes we get an error due to data in a row, after correcting errors in the data we can re-merge rows easily. See below explanations may help you to understand Merge Transformation: I do evaluate here, you already know about the data source, data conversion, data flow, task flow, control flow etc. Note:Before Merge transformation, we need to sort the data using Sort Transformation. After sorting data add data path to Merge…