Split TempDb in SharePoint 2010 Sql Server DB

Question

Hi ,
We have envirenment of sharepoint farm,one Database server.We have plan to split tempDb acording microsoft best practices.
By the time of we have the largest content database is 260 in size and SQL Server has a 2-core processor.
So the tempdb would be split in two files with 40 GB per .mdf file.
Kinldy suiggest hopw to split TempDb.
Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS
|
| Twitter

Answer 1

Hi Shanky,
We are not facing any issue,But we had take Micorosft RaaS services,Microsoft Consutlatan suggest thet we should break oure TempDb
RaaS   ISSUE/RISK
Initial Size of Temp DB is too   small
TempDB database Size may be too   small.
SQL Server instance has only one   tempdb data file while there are more than one scheduler in use
One or more user database files   are placed on same disk volume along with TempDB database files
REMEDIATION   COMMENTS
The size   and physical placement of the tempdb database can affect the performance of a   SharePoint farm. For example, if the size that is defined for tempdb
is too   small, part of the system-processing load may be taken up with autogrowing   tempdb to the size required to support the workload every time you restart   the instance of SQL Server. You can avoid this overhead by increasing the  
sizes of the tempdb data and log files.
Currently   .mdf and .ldf files are in the D volume along with all other SharePoint   databases and there is just one tempdb .mdf file.
More information:
http://technet.microsoft.com/en-us/library/ms175527(v=SQL.105).aspx
ACTION   PLAN
Set the   recovery model of tempdb to SIMPLE recovery model.
Create   as many files as needed to maximize disk bandwidth. Using multiple files   reduces tempdb storage contention and yields significantly better   scalability. However,
do not create too many files because this can reduce   performance and increase management overhead. As a general guideline, use
# of TempDB Files = # of Processors Cores   / 4 and then adjust the number of files up or down as necessary.
Preallocate   space for all tempdb files by setting the file size to a value large enough   to accommodate the typical workload in the environment. You can go by a rule  
of thumb that the size should be 25% of the largest SharePoint content   database.
Important: Make each TEMPDB   data file the same size.
Allow   your TEMPDB files to grow automatically and monitor the disk free space, set   the file growth in fix size and not in percentage. We recommend the following  
general guidelines for setting the FILEGROWTH increment for tempdb files:
tempdb   file size from 0 to 100 MB - FILEGROWTH increment in 10 MB
tempdb   file size from 100 to 200 MB - FILEGROWTH increment in 20 MB
tempdb   file size from 200 MB or more - FILEGROWTH increment in 10%*
* The FILEGROWTH increment should be   set to a maximum of 6 GB, regardless of the tempdb file size.
Put the   tempdb database on a fast I/O subsystem. Use disk striping if there are many   directly attached disks.
Put the   tempdb database on disks that differ from those that are used by SharePoint.
Important: This action plan requires a downtime   of your SharePoint
farm as you will have to stop SQL Server services to move   data and transaction log files to different disks.
By the time of this remediation the   largest content database is 300 in size and SQL Server has a 2-core   processor. So the tempdb would be
split in two files with 40 GB per .mdf   file.
STATUS
SharePoint administrators will work   on the action plan.
Downtime required for to apply this   action plan? YES
Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS
|
| Twitter