Links for September 22, 2009

Problems with sql performance?

What to do if you have a big log.

http://blog.sqlauthority.com/2009/01/25/sql-server-shrinking-ndf-and-mdf-files-a-safe-operation/

Partitioned Tables in SQL Server 2005

sql 2008 data collector

http://blogs.msdn.com/buckwoody/archive/2008/04/17/sql-server-management-studio-standard-reports-the-full-list.aspx

sql server data collection mgmt

db tuning advisor sql server 2008

Log shipping setup video

Set Max Server Memory in SQL Server 2008

Use max server memory to prevent the SQL Server buffer pool from using more than the specified amount of memory, thus leaving remaining memory available to start other applications quickly. SQL Server does not immediately allocate the memory specified in max server memory on startup. Memory usage is increased as needed by SQL Server until reaching the value specified in max server memory. SQL Server cannot exceed this memory usage unless the value of max server memory is raised.

Before reducing the max server memory value, use Performance Monitor to examine the SQLServer:Buffer Manager performance object while under a load, and note the current values of the Stolen pages and Reserved pages counters. These counters report memory as the number of 8K pages. max server memory should be set above the sum of these two values to avoid out-of-memory errors. An approximate value for the lowest reasonable max server memory setting (in MB) is ([Stolen pages] + [Reserved pages])/ 100. To reduce the max server memory you may need to restart SQL Server to release the memory. For information about how to set memory options, see How to: Set a Fixed Amount of Memory (SQL Server Management Studio).