Database Research & Development

  • Home
  • NoSQL
    • NoSQL
    • Cassandra
  • Databases
    • Database Theory
    • Database Designing
    • SQL Server Coding Standards
    • SQL Server
    • PostgreSQL
    • MySQL
    • Greenplum
    • Linux
  • Interviews
    • SQL Server Interviews
    • MySQL Interviews
    • SQL Puzzles
  • DBA Scripts
    • SQL Server DBA Scripts
    • PostgreSQL DBA Scripts
    • MySQL DBA Scripts
    • Greenplum DBA Scripts
  • Home
  • Blog Archives !
  • (: Laugh@dbrnd :)
  • Contact Me !
sqlserverinterviews
Home 2016 December SQL Server: Index Performance Tuning with the Fill Factor

SQL Server: Index Performance Tuning with the Fill Factor

This article is half-done without your Comment! *** Please share your thoughts via Comment ***

Recently, I have published a series of articles about the PostgreSQL Fillfactor.

The Fill factor has been a always important parameter for Table and Index so again in this post, I am going to share about the SQL Server Fillfactor.

What is Fill Factor?PostgreSQL Table FillFactor

In the SQL Server, data stored in an 8KB data page, and by changing a Fill Factor value we can decide that how much we can make page free for future growth and update.

SQL Server Fill Factor is basically for Indexes. The default value for Fill Factor is 0 which is same as 100. You can set Fill factor value between 1 and 100. The value 0 and 100 means no free space on that page and page is full.

Fill factor is an Important parameter:

Carefully we should change the value of Fill Factor otherwise It will be a performance killer for SQL Server.

We should change the Fill factor value from the default 100 to between 70 and 90 bases on data size.

Because, If your index is updating again and again and Fill factor is the default, it requires more new pages to store new data.

It has to move half data into the new pages and has to change the index pointer from old pages to new pages.

This all operation requires more CPU and I/O processes and it creates page level fragmentation by splitting the pages.

If we make some free space available on the same page by changing the Fill factor value, it does not require any extra step to hold new data and saves lots of internal operation and time.

Best Practices:

SQL Server provides two different options to change and set the Fill factor value.
You can change Fill Factor value at SQL Server Instance Level and Index level.

If you change Fill Factor at the instance level, all indexes use this Fill factor value which is not advisable option because we have to change Fill factor value only for more fragmented indexes.

We should analyse the index performance bases on, how data frequently update the indexes and then we should change the Fill factor value for those indexes only.

Dec 31, 2016Anvesh Patel
SQL Server: The truth about TABLE WITH (NOLOCK)SQL Server: Configure Fill factor for Index and Server Instance
Anvesh Patel
Anvesh Patel

Database Engineer

December 31, 2016 SQL ServerAnvesh Patel, database, database research and development, dbrnd, Fill Factor, index, SQL Query, SQL Server, SQL Server Administrator, SQL Server Monitoring, SQL Server Performance Tunning, SQL Server Tips and Tricks, TSQL
About Me!

I'm Anvesh Patel, a Database Engineer certified by Oracle and IBM. I'm working as a Database Architect, Database Optimizer, Database Administrator, Database Developer. Providing the best articles and solutions for different problems in the best manner through my blogs is my passion. I have more than six years of experience with various RDBMS products like MSSQL Server, PostgreSQL, MySQL, Greenplum and currently learning and doing research on BIGData and NoSQL technology. -- Hyderabad, India.

About DBRND !

dbrnd

This is a personal blog (www.dbrnd.com).

Any views or opinions represented in this blog are personal and belong solely to the blog owner and do not represent those of people, institutions or organizations that the owner may or may not be associated with in professional or personal capacity, unless explicitly stated.

Feel free to challenge me, disagree with me, or tell me I’m completely nuts in the comments section of each blog entry, but I reserve the right to delete any comment for any reason whatsoever (abusive, profane, rude, or anonymous comments) - so keep it polite.

The content of this website is protected by copyright. No portion of this website may be copied or replicated in any form without the written consent of the website owner.

Recent Comments !
  • Anvesh Patel { Sure will do... } – May 27, 12:43 PM
  • Anvesh Patel { Great... } – May 27, 12:41 PM
  • Anvesh Patel { Great... } – May 27, 12:39 PM
  • Anvesh Patel { Great... } – May 27, 12:36 PM
  • Anvesh Patel { Great... } – May 27, 12:28 PM
  • Anvesh Patel { Great... } – May 27, 12:27 PM
  • Anvesh Patel { Great... } – May 27, 12:16 PM
  • Older »
Follow Me !
  • facebook
  • linkedin
  • twitter
  • youtube
  • google
  • flickr
© 2015 – 2019 All rights reserved. Database Research & Development (dbrnd.com)
Posting....