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

More documents

Recommendations

Info

Be sure to include regular backups of the master and msdb databases as part of youroverall backup strategy. The master database contains information about the databaseson your system, and the msdb database stores information about scheduled jobs.If you are using SQL Server 2008 Enterprise edition or later, use backup compression toreduce the size of backups and the time required to take them.Finally, remember that what you really need in an emergency is a restore, not a backup.Therefore, plan your restore strategy carefully, and test restoration of your database fromactual backups to validate that you have covered everything.Synchronize ENOVIA Database and File BackupsAn additional consideration when managing overall backup of the ENOVIA application is theinteraction between the SQL Server database and the file repository. Since the Resource Tierincludes both the ENOVIA database and the ENOVIA file server(s), a full and consistent backupof the Resource Tier requires both database and file backups.The ENOVIA database contains references (essentially, file pointers) to content in the filerepository. To ensure maximum consistency between the database file references and theactual content of the file repository, some attention must be paid to backing up bothsimultaneously.Dassault Systèmes recommends choosing one of two approaches to do this:Option 1: Take cold backups—that is, take the system offline to halt user activity, backup both the database and file repository, and then put the system back online.Option 2: Take online backups and accept some small potential inconsistency. Theissues with this approach can be minimized if the backups are taken during periods oflow activity.More information about this advanced topic is available from Dassault Systèmes.Monitor Index Fragmentation and Defragment when NecessarySQL Server 2008 uses indexes to provide fast access to information when users or applicationsrequest it. These indexes are maintained by the Database Engine as the table data grows and/orchanges. Over time, the indexes can become fragmented; especially in databases that handleheavy insert, update, and delete activity. An index is fragmented when the physical ordering ondisk does not match the logical order of the data (as defined by the index key) or when datapages that contain the index are dispersed across non-adjacent sections of the disk.Fragmentation of an index can reduce the speed of data access and result in slower applicationperformance. It can also cause more disk space to be used than is actually necessary. Indexfragmentation can be corrected by reorganizing or rebuilding the index.You can tell which indexes, if any, have fragmentation problems by using thesys.dm_db_physical_stats() system function. This function provides many details about the32
physical layout of the index. However, the most important result column for trackingfragmentation is avg_fragmentation_in_percent. This column indicates how fragmented theindex is on disk. A low number means low fragmentation (good); a high number means highfragmentation (bad).For example, this query returns index physical stats for all the indexes in the current database:SELECT OBJECT_NAME(object_id),index_id,page_count,index_type_desc,avg_fragmentation_in_percent,fragment_countFROM sys.dm_db_index_physical_stats(db_id(),NULL,NULL,NULL,'LIMITED')To identify the indexes by name, you can join against the sys.indexes system view.Similar information is also available in the Standard Reports in SSMS. To view this report, rightclickthe ENOVIA database, select Reports > Standard Reports, and select the Index PhysicalStatistics report on the fly-out menu.Table 10 provides general guidelines for interpreting the avg_fragmentation_in_percent value.Table 10: Guidelines for handling fragmentationFragmentationRecommended Action< 5% Do nothing5% to 30% Reorganize withALTER INDEX REORGANIZE> 50% Rebuild withALTER INDEX REBUILD WITH (ONLINE=ON)orCREATE INDEX with DROP_EXISTING=ONReorganizing an index does not block user access to the index while underway. However,rebuilding or re-creating the index does prevent user access to the index. The exception to this isif the ALTER INDEX REBUILD statement is used with the ONLINE = ON option. Note that onlineindex rebuild requires the Enterprise edition of SQL Server 2008.Periodically checking index fragmentation and taking any necessary corrective action isimportant to maintaining the performance of your ENOVIA deployment. The rate at which33
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 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?