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

More documents

Recommendations

Info

Table 8: Recommendations for placement of ENOVIA databaseFile Type Placement RecommendedRAID LevelDisk SpeedData(.mdf, .ndf)Physically separate disks orlogical unit number (LUN) fromthe logRAID 10 or RAID 510,000 RPM or fasterDisk(s) should not be used forother heavy file I/OLog(.ldf)Physically separate disks or LUNfrom data filesDisk(s) should not be used forother heavy file I/ORAID 1 or RAID 10RAID 5 is discouragedfor log10,000 RPM or fasterNote that when placing data and log files on separate disk volumes, the disk volumes should bephysically separate. The drive letters on which the files are placed should map to distinctphysical disk drive sets. Placement on different partitions/LUNs on a single disk drive set doesnot help performance or fault tolerance.Depending on the available I/O subsystem and the number of physical disks, it is recommendedthat you keep the following entities on separate volumes, controllers, or I/O paths:Application database data filesApplication database log filesTempdb database data filesTempdb database log filesSize Data Files Up FrontThe databases of most ENOVIA installations grow over time. For best long-term performance,Dassault Systèmes recommends sizing data and log files to match the expected long-term size ofthe ENOVIA database.If no explicit size is specified, SQL Server 2008 creates data and log files based on the size of aspecial template database called model. This is usually just a few MBs in size. As data flows in tothe ENOVIA database, SQL Server 2008 automatically extends the data and log files as needed.For large, heavily used databases, this eventually produces data files that are highly fragmentedon disk, and this fragmentation has a negative effect on performance. There is also a small runtimeperformance penalty every time a file is extended.These problems can easily be avoided by sizing files appropriately when the database is created.The following guidelines are recommended for setting the initial size of database files.26
1. Estimate long-term size of the ENOVIA database (for example, one to three years).2. To get the recommended data file size:Add 50% for small-sized databases (< 100 GB).Add 35% for medium-sized databases (> 100 GB).Add 25% for larger databases (> 500 GB).3. Maintain the size of the transaction log file so that it scales with the level of transactionactivity.Note: Optimization of the tempdb transaction log benefits performance and disk usage.For more information on managing the tempdb transaction log for SQL Server 2008, seeManaging the Size of the Transaction Log File.Table illustrates these calculations for a new ENOVIA database.Table 9: Recommendations for sizing ENOVIA databaseConstituent Example 1 Example 2Estimated Long-Term Size ofData + Indexes (1-3 years)50 GB 400 GBAdd buffer 25 GB 140 GBInitial Data File Size 75 GB 540 GBInitial Log File Size 15 GB 100 GBAlthough the initial size of the database should be sufficient for some time, you should enableautomatic file growth to avoid a production problem if the data files run out of space.As a rule, the file size for the ENOVIA database should be actively managed. Dassault Systèmesrecommends configuring data files at 1-GB growth increments and log files at 1-GB growthincrements. Avoid using large percent-based growth settings on large log files because theinitialization of new log segments can temporarily block activity on the database.Distribute the PRIMARY Filegroup Across Files on Multiple Disks (Optional)For heavily used ENOVIA databases, overall performance can be affected by the throughputlimitations of working with a single data file on a single disk volume.With SQL Server 2008, you can easily spread the I/O load for your ENOVIA database acrossmultiple disk volumes or RAID sets by mapping SQL Server filegroups to multiple files. (Note thatit is not necessary to create multiple database files on the same disk volume because this doesnot provide significant performance gains).27
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 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

Create successful ePaper yourself

Delete template?

Save as template?