TSLS – Luke Smith

Some random thoughts:

When attaching a content database to Sharepoint the SQL Log file can be the same to twice the size of the current data size. the reason for this is that sharepoint takes an internal backup of the data verifies it (as well as some other magic) then attaches it to sharepoint, once attached the backup is removed (you may need to shrink the log)

Suggest using command prompt to attach rather than UI. run “stsadm.exe -o addcontentdb -url http://yourwebapp  -databasename WSS_Content_yourwebapp

To attach a content DB of 100GB can take between 30 – 1h 30m depending on the hardware (for a resent attach I performed it took 1h 30min) and can consume between 60G – 200Gb worth of Tlog (for a resent attach I performed it consumed 79GB)

Note: Tlog will still grow in simple mode

Suggest keeping content databases to 50Gb (100Mb being the Microsoft maximun recommendation)

1. Configure SPN for Web Application Pool Account

setspn.exe -A HTTP/’WebApplicationNETBIOSURL’ domain\’ApplicationPoolAccount’
setspn.exe -A HTTP/’WebApplicationFQDNURL’ domain\’ApplicationPoolAccount’

*Using Port numbers with kerberos causes authentication problems within IE, would always suggest using netbios or\and FQDN, if your web application has been configured to use a port number suggest creating an Alternative access mapping.

2. Trust Computer and User for Delegation

AD Users and computers -> Properties of account – Make sure account is trusted and not sensitive

3. Enable Kerberos against the Web Application.

In Central Admin select Authentication Provider and then select Kerberos

For more information please see here:

http://support.microsoft.com/kb/953130

LS UPDATED: 11-Aug-09