Posts Tagged ‘Configuration’

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,

While working through my current SP2010 lecture, I found an exercise which explained how to set up a document center and how to establish a connection to a web site. The goal of this set up? Simple: When working with a web application and working on documents, at a certain point you may want to have this information centralized. And here comes the document center into play. You can use it as a central access point for your documents without really caring how to upload and complete you document library there. In the end, while working in your web application, the “Send To” context menu of a document should contain an entry for sending the document to the document center. That’s all – simple but effective.

The exercise showed how to create a document center (just create a new site collection and select under “Enterprise” the “Document Center” template). So far, so good. The explanation went further and explained the need of setting up a “Send To” connection  (from the side of the web application). So far, everything made sense. As suggested, in Central Administration I went to “General Application Settings” | “Configure send to connection”. There, I had to choose the web application (http://sp2010:25001), specify a display name, and, most important, define the Send To URL. Which one to choose? I knew the URL of the document center, but this wasn’t verified as a valid URL. A bit of browsing on the internet told me that I should append _vti_bin/officialfile.asmx as a default to the URL.



After confirming, surprisingly I received the following error message:




Still not valid? Something must have been missing. So back to searching, and finally I could find it. After choosing the document center web application, choosing “Site Actions” | “Site Settings” | “Manage Site Features”, I arrived at the following mask:




There, I needed to activate the Content Organizer Feature – done! Now, one  could expect I needed to verify that the feature was really enabled. Still being in the document center, under “Site Administration”, there was the “Content Organizer Settings” menu entry enabled.




A click on it revealed a mask where different options could be set – but most important: The Web service URL I needed!




A little copy & paste, and the job was done! I hopped back to step 1 and set up the “send to connection” using the now valid URL. It worked.




As you can see in the screen above, in the web application containing the send to connection, the new “Doc Connection Center” is available and ready for use!


Stay tuned till the next time!

Best regards,


Read Full Post »

Hi all,

After a fresh installation (or upgrade from a MOSS 2007), there are a couple of configuration steps that need to be performed. One is the configuration of the usage and health data collection. This can be done either using the Central Administration or PowerShell. This post focuses on how to do the configuration using powershell.


As the very first step we would need to bring up the SharePoint 2010 Management Shell.

Then, by issuing the cmdlet:




we can specify multiple parameters in order to set the data collection up:


  • -LoggingEnabled (1 or 0)
  • -UsageLogLocation (file path)
  • -UsageLogMaxSpaceGB [1-20]

More parameters exist, however: these are the most interesting ones. So, for example, issuing the following command:


Set-SPUsageService –LoggingEnabled 1 –UsageLogLocation C:\Logs -UsageLogMaxSpaceGB 3


would enable the usage data collection and write the corresponding logs to C:\Logs, up to amount of 3 GB. Please bear in mind that the logs max space must be within the interval [1-20].




There is also a way of specifying the usage data collection for a single event type, using the following cmdlet:



The parameters of interest are here:

  • -Identity <GUID>
  • -Enable
  • -DayRetained [1-30]

An example command would be like follows:


Set-SPUsageDefinition -Identity 0a79e3a1-c60d-473b-82b7-
f43c2b4da -Enable -DaysRetained 15


This would set the event type with the GUID to be kept in the logs for 15 days.


Until here, we could have done the same operations using the Central Administration. However, there is a configuration that can only be performed using PowerShell:


Usage Logging in a Different Database.


As we might have guessed, another cmdlet is needed for this operation:



It uses the following parameters of interest:

  • -DatabaseServer <Server>
  • -DatabaseName <DBName>
  • -DatabaseUsername <User>
  • -DatabasePassword <PWD>

The latter two parameters, –DatabaseUsername and –DatabasePassword, are only required if our DB user differs from the user we are currently logged on as.


What else there is to mention? Well, do test the above commands thoroughly before applying them in any productive environment. They affect the logging and hence may have a negative and severe impact if applied the wrong way (or just as they are –please DO NOT copy paste and execute them – the parameters need to be adapted to your needs).


For all three methods, there exists also an additional –Verbose parameter, that tells you about success or failure of the application.


Best regards & happy SP-configuring!


Read Full Post »

Dear all,

During a few tryouts (and after a successful set-up of the SP 2010 Server), I went for the creation of the first web application – but no: after navigating to the Central Administration | Application Management | Manage Web Applications, I found myself with an all-greyed-out line of buttons in the “Web Application” ribbon. Now, according to forums, it turned out there are multiple (possible) sources which could cause this result (among them: not being an administrator, not being member of the farm administrator’s group, etc.). I checked these possibilities, and they were fine.


In this case, I just had to navigate to Control Panel | Change User Account Control Settings and change it to “Never notify”.



Fig. 1 The changed UAC


A restart of the server VM did the trick, and eventually the “Web Application” ribbon would show up as in the screenshot of Fig.2:




Fig. 2: After setting UAC to “Never notify”



Finally, the “New” button got activated and would allow for the creation of new SP 2010 – Web-Applications!

Best regards,


Read Full Post »