Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
0% found this document useful (0 votes)
10 views

Automation Manager Database Migration To SQL Server

The document outlines the steps for migrating Automation Manager to SQL Server, requiring SQL Server 2008 or later and SQL Server Management Studio Express. It details the creation of a new database, configuration of SQL Server connections in Alphacam 2018R1, and methods for importing and migrating data from legacy CDM installations. Additionally, it provides warnings about data loss during migration and emphasizes the importance of backing up existing databases.

Uploaded by

prog.r
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views

Automation Manager Database Migration To SQL Server

The document outlines the steps for migrating Automation Manager to SQL Server, requiring SQL Server 2008 or later and SQL Server Management Studio Express. It details the creation of a new database, configuration of SQL Server connections in Alphacam 2018R1, and methods for importing and migrating data from legacy CDM installations. Additionally, it provides warnings about data loss during migration and emphasizes the importance of backing up existing databases.

Uploaded by

prog.r
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

Automation Manager Migration To SQL Server

Prerequisites:

SQL Server 2008 or later must be installed. Download from here:

https://www.microsoft.com/en-gb/download/details.aspx?id=30438

SQL Server Management Studio Express must be installed (part of the above download)

You will also need the following file:

• Create Automation Manager Database With System Data.sql

This is located on:

\\ukrdg-fs-001\Support\AutomationManager\SQL Server Database Scripts

Launch “Microsoft SQL Server Management Studio” and connect to the correct server:

Select the “New Database” item from the Database node of the Object Explorer:
The New Database Dialog will be displayed.

Type a “Database name” for the database:

Leave all other options at their default setting.

Click OK to create the database.

Select the database created with the above step in the object explorer. Select the “Open File” toolbar
button or the File | Open | File… menu.

Navigate to and select “Create Automation Manager Database With System Data.sql”
Ensuring that the new database is selected in the dropdown:

Click the “Execute” button.

A message should be displayed in the message window indicating success:

The following 7 messages should be displayed:


Automation Manager Configuration Of SQL Server

This assumes that SQL Server has been installed and the Automation Manager database has been created
as detailed above.

Connecting To SQL Server Using Alphacam 2018R1:

For Alphacam 2018R1, a new settings dialog has been added:

This allows SQL Server to be selected and configured more easily. Select Microsoft SQL Server and
Configure:
A dialog will be displayed allowing a SQL Server connection to be configured:

Click the server name drop down to see the list of available SQL Server instances.

Choose how the user connects to this instance of SQL Server. If using “SQL Server Authentication” the user
name and password will be required from whoever installed SQL Server.

Click the drop down to select the database on the selected server:

The database created in the steps above should be on the list.

Click the “Test Connection” button to ensure the user can connect to this database, then click OK to save
the connection properties.
Creating A Connection To SQL Server Prior To Alphacam 2018R1

Prior to Alphacam 2018R1 the connection string to SQL Server needed to be created manually.

Create a new text file in:

LICOMDAT\Automation Manager Data

Called:

“AutomationManager.con”

Edit this file using notepad or a text editor. The connection string is of this format:
Data Source= UKRDG-PC-00058;Initial Catalog=Automation Manager;Integrated
Security=SSPI

(for Windows authentication)

or
Data Source=UKRDG-PC-00058;Initial Catalog=Automation Manager;Integrated
Security=False;User ID=<user id>;Password=<password>

(for SQL Server authentication)

Data Source is the name of the SQL Server instance, or the computer name for a local database

Initial Catalog is the name of the database


Migrating The Data

The Automation Manager ribbon bar contains the following command related to data migration:

“Import Data From CDM” will attempt migrate data from existing CDM installations (SQL Server or
Microsoft Access) into the Automation Manager database. This command is visible to users with:

• a valid CDM license (ACCDM-0)


• a reseller license
• an Automation Manager Plus licence

“Migrate Data To SQL Server” will migrate existing Automation Manager data (VistaDB format) to SQL
Server. This command is visible to reseller licenses only, where the Customer Name contains “Planit”,
“Vero” or “Development”. This is an intentional restriction.
Importing Data From CDM

The “Import Data From CDM” command will attempt to connect to a legacy CDM database. The legacy
database used will be that specified in Configure Database of legacy CDM:

Where no legacy connection exists but the user has data to migrate (for example a new PC with only
Alphacam 2017R2 or newer installed), the data migration will look for and use:

Licomdat\CDM Data\CDM.mdb

Ensure the legacy CDM database file file exists in this location with this filename in this scenario.

On successful connection to a legacy database, the CDM Data migration Dialog will be shown:

Select the items to be migrated and click OK to start the migration.

Depending on the amount of data, this can take a short time to perform the migration. (Possibly 30 minutes
for a larger database)

NOTE: The data migration will prevent repeated attempts to migrate the same data. This will give an
informative error message at the end of the migration advising how many rows have been imported and
how many duplicates were encountered.
Migrating Automation Manager Data To SQL Server

Click the “Migrate Data To SQL Server” button on the Automation Manager Ribbon Bar:

The following waring will be displayed:

Any existing Automation Manager Data on the specified SQL Server database will be lost. Ensure a database
backup is performed using SQL Server Management Studio if needed.

A dialog box will be displayed after the migration indication success or detailing any problems that were
encountered:

You might also like