Optimizing SQL TempDB for SharePoint
Background
The TempDB is a system database in Microsoft SQL Server and is available to all users connected to the SQL instance.. It is used to temporarily store user objects that are explicitly created. For example, global or local temporary tables, temporary stored procedures, table variables, or cursors. Tables and procedures that are stored in the TempDB are automatically dropped on disconnect and the system always starts with a clean copy of the database.
For more information on the TempDB, check here.
Many administrators overlook how TempDB affects performance in SharePoint. According to the SharePoint 2010 storage optimization guide, SharePoint farm performance can be significantly impeded by insufficient I/O for tempDB.
Recommendations
Here are some tips from Microsoft on improving TempDB performance.
- It is therefore recommended that the TempDB database is moved to your fastest disk. This should preferably be on a RAID 10 array.
- Preallocate space for all tempdb files by setting the value large enough to accommodate the typical workload in the environment.
- Create as many files as needed to maximize disk bandwidth. Using multiple files reduces storage contention. The guideline is 1 TempDB per CPU.
- Make each data file the same size to allow for optimal proportional-fill performance.
- Put the TempDB on a seperate disk to those that aused by user databases.
How to move the TempDB database
Open Microsoft SQL Server Management Studio
Click on New Query and paste the following code in, replace the paths to suit your environment:
USE master GO ALTER DATABASE TempDB MODIFY FILE (NAME = tempdev, FILENAME = 'c:\Databases\tempdb.mdf') GO ALTER DATABASE TempDB MODIFY FILE (NAME = templog, FILENAME = 'c:\Databases\templog.ldf') GO |
Categories
Recent Posts
- Save document library as template option not available
- Short break
- Speed up SharePoint using the IIS Blobcache
- Could not generate mail report.An exception occurred while executing a Transact-SQL statement or batch.No global profile is configured. Specify a profile name in the @profile_name parameter.
- Microsoft SharePoint is not supported with version 4.0.30319.296 of the Microsoft .Net Runtime.
Popular Posts
- SharePoint Keeps Prompting for Credentials Problem SharePoint keeps prompting you for credentials in the following scenarios: You ...
- Security Token Service Application- Broken Problem Had an issue today on one of my developer's VMs. ...
- User Profile Service Stuck on Starting Problem You have followed Harbar's Rational Guide to setting up the ...
- Event 8313 Topology – Load Balancer EndpointFailure – SearchService.svc Problem Encountered the following error while analysing the logs on our ...
- Event 6398 and 5586 SharePoint Foundation Problem Event logs were getting filled with the following errors: Event 5586, ...
- The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered. Problem You install .NET Framework 4.0 on your SharePoint 2010 WFE ...
- The security validation for this page is invalid Problem: After applying SharePoint 2010 Service Pack 1 and June 2011 ...
- Start a workflow using PowerShell Requirement Start a workflow on all / specific items in a ...
- Using Export-SPWeb to export libraries / lists This is a simple one but many people get the ...
- Unable to change User Profile Service Account Problem So you made a mistake by trying to change the ...
Tags
Backup and Restore Branding Content Management Content Organizer database Debugging Document Conversion Service DPM Event 7362 Expiration Policy IIS InfoPath Information Management Javascript KB2266203 Masterpage Migration Mysite OCS Office Page Layouts PowerPivot Powershell RBS Records Center Regional Settings Search Search Center Security Send-to Connection SharePoint Diagnostic Studio SharePoint Manager Solutions SPD Uploading Usage and Health Data Collection User Profile Service Visual Upgrade Web Analytics Web Content Management Webdav Webparts Workflow WSS XSLT
