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

More documents

Recommendations

Info

Note that if you are using a named instance of SQL Server 2008, the name of the object inPerformance Monitor is slightly different. For default (not named) instances, the object name isSQL Server: . For a named instance, the object name is MSSQL$InstanceName:. An example of this for an instance named ENOVIA is shown in Figure 12.Figure 12: Performance Monitor counters for a named instance of SQL Server38
ChecklistFor convenience, the following checklist summarizes and consolidates the best practicesdiscussed in this white paper. After familiarizing yourself with the preceding in-depth discussion,you can use this as a reminder to cover all the recommended best practices. Use a dedicated database server and instance. Choose the right SQL Server 2008 edition (Standard or Enterprise) for your needs. Use 64-bit SQL Server 2008 if your hardware allows. Consider acquiring 64-bithardware if it does not. Use a low-privilege Windows account for the SQL Server 2008 and SQL Server Agentservices. Grant the Perform volume maintenance tasks permission to the SQL Server serviceaccount to allow fast file initialization. Set the collation to Windows collation when installing SQL Server 2008. Set the server authentication mode to mixed. Configure the SQL Server Database Engine service and the SQL Server Agent service toauto-start. Size and place tempdb per best practices (as described in detail in this document). Set the maximum server memory for SQL Server per recommendations. Place the data and log files on physically distinct disk volumes. Use RAID 10 or RAID 5 for data files; use RAID 10 or RAID 1 for log files. Use large initial size for data and log files, based on projected growth. Leave automatic file growth enabled just in case. Spread the PRIMARY filegroup across equal-sized files on multiple disk volumes(optional). Use SQL Server data compression (SQL Server 2008 Enterprise edition only). Verify that the ENOVIA database is using Windows collation. On the ENOVIA database, use the following settings:ooooAuto Create Statistics = TrueAuto Update Statistics = TrueAuto Close = FalseAuto Shrink = False39
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 18 and 19: Note: While the startup for a stand
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 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?