Help - Creating a New HDB and Long Term Storage

Creating a New HDB and Long Term Storage

▷: SQL Server or SQL Server Express is selected.

▷: You have SQL Server administrator rights to create a History Database.

▷: The destination folder where the HDB data and log files will be stored, typically GMSDatabases, is not compressed.

▷: For the hard disk sector-size support boundaries in the SQL server, see http://support.microsoft.com/kb/926930/[language code] from Microsoft.

1.: In the SMC tree, select History Infrastructure > [SQL Server Name].

2.: Click Add .

3.: Open the Settings expander and enter data into the following fields:

-: HDB name: Enter a name for the HDB (do not use special characters, see Settings)

-: Data size: Set the size of the HDB:
‒ Maximum 10 GB for SQL Server Express
‒ Maximum 250 GB for SQL Server
(See the NOTE following this procedure on database size).

-: Recovery model: Select the backup model (see Recovery Models).

-: Administration model: Select the option Automatic or Manual.
NOTE: If you select Manual mode, the GMS HDB Service is switched off. The administration of the History Database is controlled (for example, backups or size of the history database) by the customer’s IT department.

4.: Select the Files and Paths expander (do not use special characters - see Files and Paths) and enter the following data:

-: Data file: C:\[MyHDB]\HDB.mdf

-: Log file: C:\[MyLog]\HDB.ldf

-: Backup file: C:\[MyBak]\HDB.bak

-: Recovery log path: C:\[MyRevoveryPath]
NOTE: If you do not use the standard paths in the Data file, Log file, Backup file, and Recovery log path fields and if the SQL Server is on a different computer, you must first create the folders before you click Save.

5.: Select the Security expander and check the entered user.

6.: (Optional) Select the Long Term Storage expander and enter or select the following data:

-: Data files: Select the destination where you want to save the data files (.mdf).

-: Log files: Select the destination where you want to save the log files (.ldf).
NOTE: Due to security and performance reasons, save the data and log files on two separate physical hard disks (not two separate partitions).

-: Recovery files: Select the destination where you want to save the recovery files.

-: Storage slices: Enter how many storage slices the Long Term Storage should have (max. 10). When this number is reached, the oldest storage slice is archived. The Slices table shows the storage slices.

-: Max size: Enter the maximum size of a storage slice. When this number is reached, another storage slice is created.
NOTE: This entry may override the entry in the Time Sliced field.

-: Archives: Select a destination where you want to save the archived storage slices. The Archives table shows the archived storage slices.
NOTE: If you do not use the standard paths in the Data files, Log files, Recovery files, and Archives fields and if the SQL Server is on a different computer, you must first create the folders before you click Save.

-: Start: Select to activate the storage. The storage will be activated when you click Save.

-: Time Sliced: Select when a new storage slice is created. For example, if you select monthly, a new storage slice is created each month.
NOTE: This entry may override the entry in the Max size field.

-: Closing Time: Select at what time a new storage slice is created.

-: Add Storage: Click to create more Long Term Storages.
NOTE: Rename the default storage name in System Browser if requested.

7.: Click Save .

8.: Click Yes.

⇨: The History Database is created and displays in the SMC tree. This may take a few minutes depending on the selected database size.

⇨: The History Database starts automatically.

⇨: History data is logged after linking to the project.

⇨: The Long Term Storage is created when the state in the State column in the Storage table changes to On. A Long Term Storage slice with the state CURRENT is created in the Slices table. See also Configuring History Database and Add or Rename Storage Names.

NOTE 1:
Select a database size on the engineering computer that is not overly large (1 to 5 GB). The larger the database, the longer it takes to restore date to a customer computer. After restoring data to the customer computer, select Change HDB Properties and extend the database file size according to the project requirements (50 to 250 GB).
NOTE 2:
We recommend not encrypting the hard disk where the database is located. If you encrypt the hard disk with a software application, such as BitLocker, the SMC may not be able to connect to the database. If you want to encrypt your hard disk, use the SQL Server Enterprise Edition, which has Transparent Data Encryption (TDE).

	NOTICE
	Data Loss Data loss will differ depending on the selected recovery model (Simple or Full). See Recovery Models.

Further information

•: Editing a Long Term Storage

•: Deactivating a Long Term Storage

•: Mounting an Archived Long Term Storage Slice

•: Unmounting a Mounted Long Term Storage Slice

•: Deleting an HDB