Disk Usage - Intergraph Smart 3D - Installation & Upgrade

Intergraph Smart 3D Installation

Language
English
Product
Intergraph Smart 3D
Search by Category
Installation & Upgrade
Smart 3D Version
11 (2016)

Disk usage should remain under 85% of the maximum disk capacity, and the partition should not be compressed.

Sizing the Files

With Microsoft SQL Server, a database is created by default with a data file of 1MB and a log file of 1MB.

A database can be associated to more than one data file and more than one log file.

Both files are set to grow by 10% increments until space is no longer available on the drive. These defaults, however, are not adequate for monitoring or for a production system. When the data or log files are growing, the process may consume a very large amount of server resources and slow down the interactive users or perturb the monitoring performed on the system. As a result, we recommend that you set the size of the files to avoid automatic growth.

Set the size to the maximum anticipated size of the file. Set the growth increment to size of the available space or 85% of the capacity of the drive.

If automatic file growth occurs, re-evaluate the situation and try to set more accurate sizes or plan to add more capacity for your database.

Determining RAID Configuration

Use the following database activity considerations to determine the appropriate RAID configuration for optimum performance:

  • Model Database - High level of reads and writes (select, insert, update, and delete activities).

  • Catalog Database - Medium to Low level of reads and writes (select, insert, update, and delete activities). Activities such as bulkload and copy to catalog are write activities. Both can write a significant amount of data.

  • Catalog Schema - Low level of reads and very low level of writes. Activities such as bulkload are used to write occasionally, but the amount of data is relatively small.

  • Site - Very Low level of reads and writes. While the Site is not read-only, the write activity is limited to a maximum of several rows per week.

  • Site Schema - Very Low level of reads with no writes.

  • Report Database and Report Schema - Read only. They contain views that are composed of queries mainly from the Site, Catalog, and Model Databases.

Microsoft SQL Server tempdb has a high level of read and write.

The following table is based on a Microsoft SQL Server setup and shows some reasonable orders of magnitude for small pilots based on testing conducted by Hexagon Asset Lifecycle Intelligence. The most critical files for performances and monitoring are isolated on their own physical drives (the G and H drives) while the less critical files share two drives (the E and F drives). The operating system, SQL server and paging files are installed on their own drives.

File

Initial Size

Growth Increment

Drive

Model data

10 GB

1 GB

G

Model log

1 GB

500 MB

H

Catalog data

1 GB

500 MB

E

Catalog log

500 MB

100 MB

F

Catalog schema data

Default

Default

E

Catalog schema log

Default

Default

F

Site data

50 MB

10 MB

E

Site log

50 MB

10 MB

F

Site schema

Default

Default

E

Site schema log

Default

Default

F

Report data

Default

Default

E

Report log

N/A

N/A

F

Temp DB data

500 MB

100 MB

E

Temp DB log

1 GB

500 MB

F

  • The size of your Model database log file depends on your backup strategy. For more information about backing up your Smart 3D data, see Smart 3D Project Management.

  • Tempdb size is reset to the default every time the server is re-started.

  • We recommend that you have the same number of Tempdb data files as you have physical cores on the server machine, if you have up to eight physical cores. If you have more than eight cores, add eight data files, and only add more data files as necessary. Each data file should have the same initial size, growth increment, and drive location as specified above.

See Also

Smart 3D Database Server Recommendations
Recommendation for Database Monitoring
Monitoring the Databases
Assign System Administrator Privileges for SQL Server 2014