Archive for the ‘Configuration Database’ Category

1. Close Distance Rule:

Keep Web Frontends, Application Servers and Database Servers physically located as close as  possible.


Rule of thumb: No more than 1 ms of latency between WFEs/AS and DB servers. In practice, this means: WFEs/ASs should reside in the same data center as DB servers.



2. Co-Location/Separation of Databases

Certain databases must be co-located or ideally separated from other databases.


Rule of thumb: Separate the following databases:





Source: Microsoft Technet


Rule of thumb: Co-locate the following databases:




Source: Microsoft Technet


3. Constantly Monitor Database Servers

Size: Rules of thumb:

    Pre-grow databases and logs.

    Monitor disk space at all times.

    < 50 Databases per SQL Server instance (when mirroring)

                          < 200 GB per content database



Metrics: Rules of thumb:

    Network Queue: 0 or 1 for best performance

    Average Disk Queue length (latency) : < 5 ms

                       Memory used: < 70%

                       Free disk space: > 25%

                       Buffer cache hit ratio: >= 90%


4. Transaction Logs Backup

Rule of thumb: Back up and truncate the transaction logs every 5 minutes. Shrinking the transaction logs is not recommended since it will have a performance impact while it re-grows.



For preventing the transaction logs to grow unexpectedly, view the following KB: http://support.microsoft.com/kb/873235


That’s it for this time. Have fun configuring your DB servers for your SP2010 environment. As usual, no responsibility is taken for any damage that could occurr. And as ususal, I highly recommend trying all changes on a test environment and the adaptation to your specific IT infrastructure.


Enjoy and best regards,


Read Full Post »

Hi folks,

just a quick one this time:


How do we connect a server to an existing configuration database? Simply by issuing the psconfig.exe command:


psconfig.exe -cmd configdb -connect -server <Server_name> -database <Database_name>


Please note that this will disconnect the server from the farm it is currently connected to!


Similarly, you can explicitly disconnect a server from a farm:


psconfig.exe -cmd configdb -disconnect -server <Server_name>


Moreover, you can:


  • Provision the Services (handy in case of unresolvable service application errors)
  • Provision the Central Administration (handy in case of unresolvable CA errors)
  • Resume a failed upgrade
  • Repair SharePoint 2010 installations


The repair is also quite simple:

psconfig.exe –cmd setup /repair

Afterwards, depending on your deployment, choose one of the following:


  • Case 1: Single Server Deployment: run psconfig.exe –cmd setup
  • Case 2: Farm Deployment: Run the Products Configuration Wizard


The psconfig tool is really a bit of an SP2010 administrator’s (configuration) army knife. You can check out its full capabilities here




Best regards,


Read Full Post »