Add Ape Database to SQL Server
Install Calibration Control on Your SQL Server
Before beginning, ensure you are signed into your SQL Server with enough permissions to create and update databases and their objects (e.g., system admin).
Installing the apecal database on your on your existing SQL Server (2008 R2, 2012, or 2014) is a simple database restore from a provided backed up file. All SQL files needed to perform the install reside in the SQL Tools folder under the CC program folder located at Program Files (x86)\Ape Software\Calibration Control.
Restore Back-Up Database
From within SQL Server Management Studio with your SQL Server connected, right-click on the Database node and select Restore Database.
From within the Restore Database dialog, type the name apecal in the 'To database' field, select 'From device', and then click on the [. . .] button to the right of the ‘From device’ field.
From within the Specify Backup dialog, click the [Add] button.
Locate the backup file by navigating to or pasting in the 'Selected path'. Paste or type the File name of the file to restore from (e.g., apecal_s51_r52.bak). Then click [OK] to save and close the backup file and [OK] again to close the Specify Backup dialog.
When the Restore Database dialog is on the top again, click the checkbox in the Restore column of the backup set (file) you just designated and then click the [OK] button to begin the restore.
If successful, you should see the following confirmation dialog.
After closing the confirmation dialog, refresh the list of databases to see the new apecal database.
If the restore failed, you may need to repeat the above steps and specify different file names or path statements. Use the Options Page of the Restore Database dialog to modify the Database (e.g., Rows Data) or Log file names or the Path statement (i.e., Restore As).
Users can connect to the apecal SQL Server database using either Windows or SQL Server authentication. Each user will either need Database Roles or Explicit Permissions.
When using Database Roles, ensure each user has db_datareader and db_datawriter roles.
When using Explicit SQL Server Permissions, ensure each user is grated at least the Connect, Delete, Execute, Insert, Select, and Update permissions.
Last updated: 4 Jul 2016