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

More documents

Recommendations

Info

fragmentation may occur depends on user activity, but as a general rule, Dassault Systèmesrecommends checking index fragmentation at least monthly.For more information about reorganizing and rebuilding indexes, see Reorganizing andRebuilding Indexes.Periodically Check Database IntegrityDespite the sophisticated data management techniques embedded in the SQL Server DatabaseEngine, some corruption can still occur in a database, most notably as the result of a hardwareproblem. To head off the potential impact of such problems, you should regularly check theintegrity of the database with the T-SQL statement DBCC CHECKDB.It is best practice to include database integrity checks in a scheduled job that executes DBCCCHECKDB or to use a scheduled Maintenance Plan that includes the Check Database Integritytask.If any problems are detected, you can restore from backups (usually the best option) or use oneof the REPAIR options on DBCC CHECKDB.Monitor Space UsedOver time, the space used in your ENOVIA database for data and indexes will increase.Regardless of the initial space allocations you have made, you occasionally need to check theamount of space remaining in data and log files and on the host disk volumes.You can check the space consumed and remaining for the ENOVIA database using the StandardReports in SSMS. The Disk Usage report displays the currently reserved space in data and logfiles and the amount of disk space that is in use. This is also a convenient place to check for anyrecent data or log file growth. If growth is occurring, it may indicate that a rearrangement orexpansion of data files is necessary.Details on space usage can also be obtained via T-SQL by using the sp_spaceused storedprocedure. See sp_spaceused (Transact-SQL) in SQL Server Books Online for details.Use SQL Server Agent Jobs and AlertsMany of the ongoing database management and monitoring tasks required to administer yourENOVIA database can and should be automated. SQL Server 2008 includes SQL Server Agent, ajob scheduling and alerting service that is tightly intertwined with the SQL Server DatabaseEngine. SQL Server Agent can be used to schedule regular backups, database integrity checks,index reorganization jobs, and many other routine tasks. It can also be used to check DatabaseEngine metrics and alert someone if they are outside normal bounds.SQL Server 2008 Maintenance Plans also provide a neatly packaged way to define and scheduleroutine management tasks for a database or for multiple databases.34
Dassault Systèmes recommends using these tools to configure automated maintenance andmonitoring tasks for the ENOVIA database.Tools for Monitoring Database Server PerformanceOnce your ENOVIA database is in production, it is important to establish a baseline of its normalperformance characteristics and to check its health and status periodically. The followingsections discuss some of the tools and techniques available for monitoring database serverperformance.SQL Server Activity MonitorA good, easy-to-use starting point for monitoring your SQL Server 2008 instance is the ActivityMonitor in SSMS. This tool combines several key pieces of information into one view. Althoughit does not provide highly detailed insight on its own, Activity Monitor can be a good part ofyour SQL Server monitoring toolbox.To open Activity Monitor, right-click the server icon in the Object Explorer pane of SSMS andselect the Activity Monitor item. There is also a button for Activity Monitor on the Standardtoolbar in SSMS. The Activity Monitor opens as a new tab in the main Management Studiowindow.The Overview section shows summary graphs of four key metrics for getting a sense of the loadon the server. The % Processor Time is an average of CPU utilization across all processors.Waiting Tasks shows the number of tasks waiting on CPU, memory, disk, locks, or otherresources. The Database I/O graph shows overall disk I/O throughput of SQL Server 2008. BatchRequests/sec shows the number of individual T-SQL batches executed per second (for example,SQL statements or stored procedures calls from applications).The other sections (also called panes) in the Activity Monitor tab provide detailed snapshots ofdifferent aspects of the Database Engine’s current workload. While a full discussion of thesesections and how to interpret the information provided is beyond the scope of this white paper,a brief introduction to each section follows.Processes section: This section presents a list of the active user connections to theserver. For each connection, useful troubleshooting information is provided, includingthe current database the connection is using, what resource the connection is waitingon (if any), and whether the connection is blocked by another connection. TheProcesses section is thus useful for getting an idea of the number of active connectionsand what sort of performance roadblocks they may be experiencing.Resource Waits section: This section provides a summary of the “waits” the DatabaseEngine is observing in current activity. Examples of waits are network I/O for clients topull results across the wire, disk I/O for the server to pull data from disk into buffermemory, or lock waits while one connection waits on a transaction lock held by anotherconnection. Besides the type of wait, this section shows the cumulative and recent35
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 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

Create successful ePaper yourself

Delete template?

Save as template?