Best Practices for Running Dassault SystÃ¨mes ENOVIA ... - Microsoft

More documents

Recommendations

Info

Note: While the startup for a stand-alone SQL Server 2008 instance can be set toAutomatic, the startup for Windows Server failover cluster service should be set toManual. Instead of the service being started automatically, the Windows Server failovercluster service monitors and manages the instance. The startup type should be set toManual for all cluster-aware services, including full-text search and SQL Server Agent,and cannot be changed during installation.Microsoft recommends that you configure service accounts individually to provide leastprivileges for each service, where SQL Server services are granted the minimumpermissions they need to complete their tasks. For more information, see Setting UpWindows Service Accounts (http://msdn.microsoft.com/en-us/library/ms143504.aspx)and SQL Server Configuration - Service Accounts (http://msdn.microsoft.com/enus/library/cc281953.aspx)in SQL Server Books Online.Tempdb Best PracticesThe configuration of the SQL Server tempdb database is critical for best performance because ofthe potential of added performance stress on tempdb from new features such as readcommittedsnapshot isolation level and online index operations.It is recommended that tempdb be isolated from other database activity and be placed on itsown set of physical disks. It is especially important to use RAID 10 for tempdb.Move tempdbBy default, tempdb files are located in the same directory as the other SQL Server systemdatabases. For busy servers, this is usually not optimal. Tempdb should be moved during theinstallation process to a high-performance, fault-tolerant disk volume—for example, a RAID 1 orRAID 10 volume on fast disks. Tempdb should not be placed on a RAID 5 volume because of theinferior write performance of RAID 5. When configuring especially busy high-performancesystems, solid-state disks (SSDs) may also be considered for tempdb.If you did not move the tempdb during the installation process, move it after the installation iscompleted by using the ALTER DATABASE statement. For example, to move tempdb to the G:drive and the log file to the H: drive, execute the following commands in a Microsoft SQL ServerManagement Studio (SSMS) query window:USE master;GOALTER DATABASE tempdbMODIFY FILE (NAME = tempdev, FILENAME = 'G:\SQLData\tempdb.mdf');GOALTER DATABASE tempdbMODIFY FILE (NAME = templog, FILENAME = 'H:\SQLData\templog.ldf');GO18
You must restart SQL Server 2008 for 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 performed 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 for tempdb to 50megabytes (MBs). This prevents tempdb from expanding too frequently, which can affectperformance. Set the tempdb database to auto grow, but use this option to increase disk spacefor unplanned exceptions.For information on SQL Server 2008 tempdb size recommendations, see Optimizing tempdbPerformance.When the READ_COMMITTED_SNAPSHOT database option is set to ON, logical copies aremaintained for all data modifications performed 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 performance.Note: To avoid negatively impacting performance, 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 perform 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 for setting the FILEGROWTH increment for tempdb files.19
Page 2 and 3: DisclaimerThis document is provided
Page 4 and 5: CHECKLIST .........................
Page 6 and 7: Best Practices for Running ENOVIA o
Page 8 and 9: installing the equivalent x64 (64-b
Page 10 and 11: It is important to note that for EN
Page 12 and 13: Note that in Figure 4, svc-EnoviaSq
Page 14 and 15: Dassault Systèmes ENOVIA is design
Page 16 and 17: Figure 8: Choose server collation f
Page 20 and 21: Table 5: Tempdb FILEGROW increment
Page 22 and 23: Use Multiple, Dedicated DisksIf you
Page 24 and 25: Configure RAM on 32-bit Servers (V6
Page 26 and 27: Table 8: Recommendations for placem
Page 28 and 29: You should only take on the extra a
Page 30 and 31: log is available, it is possible to
Page 32 and 33: Be sure to include regular backups
Page 34 and 35: fragmentation may occur depends on
Page 36 and 37: amount of time spent on this type o
Page 38 and 39: Note that if you are using a named
Page 40 and 41: Use the full recovery model for the
Page 42: Links for Further InformationFor ge

Best Practices for Running Dassault SystÃ¨mes ENOVIA ... - Microsoft

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?