Free Whitepaper: Maximizing SQL 2012 Performance for SharePoint 2013 Whitepaper


Hello Everyone, For the past few weeks I was writing a Whitepaper about maximizing SQL 2012 Performance for SharePoint 2013. It’s  been reviewed by 4 great guys , and after being exclusive to for one week, I release it to the public!

If you want to see the interesting results I got with the modifications suggested in  this WhitePaper, you can read about them on SharePoint-Community.Net

Read the abstract or download the Whitepaper Directly  here!

As a SharePoint Consultant I get to see dozens of SharePoint farms every year, and one of the most common complaints I get from clients – is that SharePoint is slow. A lot of people think that SharePoint is slow because the SharePoint servers are lacking resources or, simply, because SharePoint is a slow product. Although resources allocated to the SharePoint servers (e.g. Web Front Ends and App servers) are important, not a lot of people realize that SharePoint performance is directly related to the database, SQL Server. In fact, 94% of SharePoint data is stored in SQL.

In this whitepaper, we will explore many options on how to optimize SQL Server 2012 for SharePoint 2013.  Here is a high level overview of what we intend to explore.
Plan before you install
In this section we will review important best practices on how to format your disks, as well as how to plan where databases, logs and your Temp DB will be located.  Furthermore, depending on the purpose of your SharePoint 2013 Farm, we will determine which databases are most important.

How to install SQL Server 2012
In this section we will discuss what changes during installation can impact SQL 2012 Server performance and explain the reasons behind them. For example, did you know SharePoint 2013 uses a different collation than the default SQL one?
Post installation changes
In this section we will examine the changes required immediately after you have installed SQL 2012. This will ensure that we have the correct settings from the outset. We will cover everything from Initial DB size to Fill Factor to Instant File Initialization.
 How to keep it performing well for the years to come
Now that you installed SharePoint 2013, Web Applications are starting to be created, content is added. Unfortunately, if you want to keep your SharePoint fast and your users happy, your job is not done. In this section we will make a list of things you need to check and modify, together with a schedule.  Luckily, since we made things right in the Post Installation changes, you won’t have to do them very often.

Leave  a comment and don’t forget to like us on Facebook here and to follow me on Google+ here and on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check the SharePoint Community Partners list for other great SharePoint Sites, and vote for my blog if you like my content!

Previous Post
Free SharePoint Server 2013 Resources Part 6
Next Post
Absolute SharePoint is migrating to WordPress This saturday


  • April 30, 2013 at 5:32 pm

    please repair link

    • April 30, 2013 at 6:02 pm

      Hi, can you please tell me what link doesn’t work? they all seem to be working!

  • July 4, 2013 at 3:30 pm
    Edwin Sarmiento

    Great work Vlad! Keep it up.

  • September 9, 2014 at 6:08 am
    Prasath S

    hi.. nice work…

    download link is not working

  • September 25, 2014 at 8:46 am

    Link still not working

  • June 26, 2017 at 7:29 pm
    Dean Gross

    If an existing SQL server has disks formatted as 4K instead of 64K, how can it be changed?

    • June 28, 2017 at 9:48 am

      You will need to move Databases off to another disk, reformat the disk, and then move the mback. There is no easy way unfortunately as a reformat is needed

  • September 12, 2017 at 11:15 am

    Where the paper says “begging”, that must be a typo for “beginning”.


Leave a Reply

15 49.0138 8.38624 1 0 4000 1 300 1