Notice Each database type has a Schema version that corresponds to a version (or versions) of CM4D. These Schema/Version pairings must match for CM4D to connect to the database.
The ATS CM4D product relies on multiple Microsoft SQL Server databases to store the dimensional data that is used by its various applications.
Site Database
CM4D Database(s)
End-users will access these databases simultaneously or separately depending on the method of data access.
If you are using a SQL authentication user, refer also to the topic Create a SQL Authentication User.
The ATS CM4D software product relies on databases to house all relational data either input as raw data by DataSmith or data calculated by CM4D. The "CM4D Databases" include one Site Database and one or more CM4D Databases.
The two database types are both created and updated manually using SQL scripts included with your CM4D installation.
Notice
Each
database type has a Schema version that corresponds to a version (or versions)
of CM4D. These Schema/Version pairings must match for CM4D to connect
to the database.
A CM4D Site Database is used primarily for the internal enterprise management of the CM4D solution on a server. Some additional functions of the database include user management, user privilege management, CM4D Scheduler settings, and DataSource configurations.
A CM4D Site database may contain many CM4D databases. In some cases, those databases could contain many routines which share the same identifying information. For example, different databases could be created for different development phases of a product. These databases may all contain the same identifying information. How would DataSmith know to add data to the routine you intended it to? Adding another characteristic to your nominal file called Routine Code solves this problem.
See the topic, Create a Site Database.
A CM4D Database is used to store the actual measurement data and routines. You can implement multiple CM4D Databases. Different CM4D database may be used to provide a logical separation of data activities. For example, your company may deploy a distinct CM4D Database for each product, model year, manufacturing facility, etc. How you utilize these databases, however, is 100% customizable. The only thing that is required by CM4D is to define all of those databases within your CM4D Site Database and apply privileges and access to all users who need access to your CM4D data. This management is handled using the Site Manager application.
See the topic, Create a CM4D Database.
A Managed DataSource is a CM4D DataSource Database that is administrated at an enterprise level by a CM4D Site Database.
An Unmanaged DataSource is a CM4D DataSource Database that is not controlled by a Managed DataSource.
The Results database is a data warehouse containing all results data for CM4D. It is an extension to the CM4D databases but is not managed directly by the CM4D Site database. For end-users of CM4D, however, the Results Database and CM4D Databases are all a single storage entity.
Unlike the CM4D Databases, the Results database object, tables and stored procedures are created and updated using the DbMigrator application included with the CM4D install. This tool can be provided as a stand-alone to a DBA if needed. See here for information on the DbMigrator tool.