10.07.2015 Views

Best Practices for Running Dassault Systèmes ENOVIA ... - Microsoft

Best Practices for Running Dassault Systèmes ENOVIA ... - Microsoft

Best Practices for Running Dassault Systèmes ENOVIA ... - Microsoft

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

You must restart SQL Server 2008 <strong>for</strong> this change to take effect. Note that SQL Server 2008creates fresh copies of the tempdb data and log files every time the service starts, so there is noneed to move any files yourself. Just restart the service, and you will see the files in the newlocation(s) you have specified.Size tempdbPre-sizing tempdb to a sufficiently large size is strongly recommended. Tempdb should beconfigured on a separate disk from the operating system and data files. All the files in tempdbshould be identical in size since SQL Server 2008 uses a proportional fill algorithm. Tempdbsizing should be per<strong>for</strong>med after a series of thorough tests so that it has had a chance to grow toa meaningful size. You may also want to increase the FILEGROWTH setting <strong>for</strong> tempdb to 50megabytes (MBs). This prevents tempdb from expanding too frequently, which can affectper<strong>for</strong>mance. Set the tempdb database to auto grow, but use this option to increase disk space<strong>for</strong> unplanned exceptions.For in<strong>for</strong>mation on SQL Server 2008 tempdb size recommendations, see Optimizing tempdbPer<strong>for</strong>mance.When the READ_COMMITTED_SNAPSHOT database option is set to ON, logical copies aremaintained <strong>for</strong> all data modifications per<strong>for</strong>med in the database. Every time a row is modifiedby a specific transaction, the instance of the Database Engine stores a version of the previouslycommitted image of the row in tempdb until the transaction that modified the row iscommitted. The tempdb database should be sized to have sufficient capacity to store these rowversions in addition to the other objects that are usually stored in tempdb.Set the file growth increment to a reasonable size to prevent the tempdb database files fromgrowing by too small a value. If the file growth is too small compared to the amount of data thatis being written to tempdb, tempdb may have to constantly expand, and this will negativelyaffect per<strong>for</strong>mance.Note: To avoid negatively impacting per<strong>for</strong>mance, administrators should monitor filegrowth and not enable automatic file growth. Every time SQL Server 2008 is started, thetempdb file is re-created with the default size. While tempdb can grow, it does takeresources to per<strong>for</strong>m this task. To reduce the overhead of tempdb growing, you maywant to permanently increase the default size of tempdb after carefully monitoring itsgrowth.Table 5 provides general guidelines <strong>for</strong> setting the FILEGROWTH increment <strong>for</strong> tempdb files.19

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!