Hi, We have MOSS 2007 SP1 databases in sql server 2005 ee x64 with sp3. Right now the content database size is 50 GB and expect to grow 100 GB in next 3-4 months. Currently the TempDB size is 10 GB and space left on TempDB drive is 40 GB. For a content database of size 100 GB, approximately how much tempDB space is required? If we expect that a content database will grow up to 100GB then what is the best way to Presize the TempDB? I mean how much space we can allocate for tempDB's mdf & ldf file proactively? Are there any metrics available for this in any share point documentation? Thanks

Capacity sizing is unique to every environment which is why it's more of an art than a science. What I would advise you is to make sure that the TempDB is on a seperate disk array on your SAN and not on the same spindles. All updates to the SharePoint DB is written first to the TempDB and then it flows to the SharePoint DBs. If the files are on the same disks, your performance will be adversely affected. You may even wish to split the MDF and LDF files for the TempDB onto seperate disks too. I trust that answers your question...ThanksChttp://www.cjvandyk.com/blog

Thanks Cornelius, we have disk allocation on SAN as below: Disk1: Primary data files Disk2: Primary Log files Disk3: Tempdb (both mdf & ldf on same disk)--> Increased the tempDb's mdf file to 10 GB & log file to 5 GB Disk4: backups So now we added one more Disk called Disk5 to keep secondary files. And want to create a secondary file for content database. So can I just create the secondary file and place it on DISK 5 or Do I need to anything else?

Hi, Ideally, place the tempdb, content databases, and SQL Server 2008 transaction logs on separate physical hard disks. It is a product team-recommended practice that the number and size of data files allocated for the TempDB should be equal to the number and size of core CPUs. This equated to 16 files for this effort, matching the number of core CPUs in the Fujitsu PRIMEQUEST server. The original TempDB data files, as well as the additional 15 TempDB data files created, were set to an equal starting size of 500MB. These data files were also spread across unique LUNs, consistent with the content database volumes. Optimal TempDB data file sizes can be calculated using the following formula1: [MAX DB SIZE (KB)] X [.25] / [# CORES] = DATA FILE SIZE (KB) For more information about TempDB data file, please refer to the following article: Scaling SharePoint 2007: Storage Architecture (R2) http://go.microsoft.com/fwlink/?LinkId=119399&clcid=0x409 Planning and Monitoring SQL Server Storage for Office SharePoint Server: Performance Recommendations and Best Practices (white paper) http://technet.microsoft.com/en-us/library/cc263261.aspx Hope this helps. Rock WangRock Wang MSFT

hope these links help http://technet.microsoft.com/en-us/library/cc263261.aspx http://technet.microsoft.com/en-us/library/cc825329.aspx http://technet.microsoft.com/en-us/library/cc512725.aspx http://www.mssqltips.com/tip.asp?tip=1432