User guide - Accelario · Source SQL Server instance – host, port, instance name,...

1 Accelario for SQL Server User Guide

Accelario www.accelario.com

USER GUIDE

Accelario Migration Suite for SQL Server 2.6 (build 157.55) Last update: August 2019


TABLE OF CONTENTS

Contents

Introduction .............................................................................................................................................................................................................. 3

KEY CAPABILITIES AND USE CASES .................................................................................................................................................................................... 3

ENVIRONMENT REFRESH MANAGEMENT AT A FINGERTIP ................................................................................................................................... 3

MULTI-STEP MIGRATION ......................................................................................................................................................................................................... 4

Accelario Definitions ............................................................................................................................................................................................. 5

WORKFLOW .................................................................................................................................................................................................................................... 5

SOURCE DATABASE ..................................................................................................................................................................................................................... 5

DESTINATION DATABASE ........................................................................................................................................................................................................ 5

LINK TO SOURCE .......................................................................................................................................................................................................................... 5

Software Installation Pre-Requisites .............................................................................................................................................................. 6

CONTROL WORKSTATION ....................................................................................................................................................................................................... 6

SOURCE AND DESTINATION DATABASES ........................................................................................................................................................................ 6

DESTINATION SERVER PRE CONFIGURATION ............................................................................................................................................................... 6

Stage 1 – Setup ......................................................................................................................................................................................................... 7

Stage 2 – Logon ........................................................................................................................................................................................................ 8

Security Logon................................................................................................................................................................................................................................ 9

Stage 2 - Configuration ....................................................................................................................................................................................... 10

2.1 WORKFLOWS ....................................................................................................................................................................................................................... 10

2.2 LINK TO SOURCE ................................................................................................................................................................................................................ 11

2.3 DATABASES CONFIGURATION .................................................................................................................................................................................... 12

2.4 TABLES CONFIGURATION.............................................................................................................................................................................................. 13

2.5 ADMIN OPTIONS................................................................................................................................................................................................................. 15

2.6 BASIC OPTIONS ................................................................................................................................................................................................................... 16

Stage 3 - Monitoring............................................................................................................................................................................................. 17

3.1 PREPARE GROUP ................................................................................................................................................................................................................ 18

3.2 COPY DATA GROUP ........................................................................................................................................................................................................... 19

3.3 CREATE INDEXES GROUP............................................................................................................................................................................................... 21

3.4 FINALIZE GROUP ................................................................................................................................................................................................................ 23

Security users ......................................................................................................................................................................................................... 24

Appendix 1 – Manually setup auto-login with SQL Server authentication ................................................................................... 25

Contact Information ............................................................................................................................................................................................. 26

Company Information ......................................................................................................................................................................................... 26

1


Introduction

Data migration processes tend to be complex and tedious, keeping DBA teams busy for months and involving risks and lengthy downtime. Despite thorough planning, many projects fail to meet their schedule and budget or yield bad data quality in the target application. Driven by the vision that automation and methodology are the key to faster processes and better results, Accelario set up a team to develop a migration tool that incorporated his abundant field experience. Initial trials clearly proved the case for Accelario as a top solution, which quickly came to be deployed for diverse use cases in consulting projects. Over the past years, hundreds of databases have been migrated and consolidated with the help of Accelario Migration Suite. Constantly refined and complemented with new features and technologies, the Suite tackles virtually any Oracle cross-platform migration scenario and refresh needs of our customers.

Accelario Migration Suite is an innovative and proven software solution for logical cross-platform migration of SQL Server databases. Built on our multi-step migration methodology, the Accelario Suite automates and accelerates migration and consolidation processes and greatly mitigates risks. Organizations benefit from optimized data quality on the target platform and immediate ROI through greatly reduced project duration, costs and cutover times compared to those incurred by manually implemented projects.

KEY CAPABILITIES AND USE CASES Proven solution for logical cross-platform migration, from any to any platform OS-agnostic: supports any Windows version. Built for complex migration projects involving parallel work, excessive data amounts and consolidation of various sources into one target database. Supports latest SQL Server versions and technologies Specific migration approach and rules for each individual platform, database version or application type (e.g. data warehouse, online production environments) according to industry best practices.

ENVIRONMENT REFRESH MANAGEMENT AT A FINGERTIP Copying and refreshing data between production, test and development environments is daily business for many DBAs. Choosing the right copying method, configuring source and target database, accurately forecasting storage and testing duplicated data tend to be lengthy complex processes, and even more so when different platforms or RDBMS versions are involved. Organizations today need to MASK their data while it is moving from Production to Test.

Accelario Environment Refresh Manger (ERM) presents a new and highly efficient approach to data duplication and refresh processes across environments. This automated tool provides DBAs with unprecedented management abilities and full control both at source and target, while accelerating execution and reducing source down time. Data moving rendered efficient and transparent with ERM, which automatically compresses data in the target environment and optimizes performance.


MULTI-STEP MIGRATION

Accelario solutions are based on the 5-step migration methodology we developed to automate and streamline data migration processes. Our methodology enables to move, refresh, consolidate and clone databases in one phase, providing full control over the process and making script writing obsolete. Accelario intuitive Management Interface walks users step by step through the process:

1. Prepare prior to copy

Preparing database infrastructure on the target

2. Copy data

Moving data with full control for users on both source and target sides. Data from multiple sources (clone, physical server, production, test environments) copied in parallel; pace set mainly by source power and size of tables.

3. Create indexes

Simultaneous to copy process and performance monitoring: online configuration and property adaptation for maximum results

4. Copy rest of the objects

Building views, procedures, etc. on the target

-------------------------

This User Guide will allow you to go step by step configuring Accelario for your needs, and enjoy this solution immediately. Start with Accelario Definitions section to have a better understanding on a few wordings. Please contact us directly for any questions [email protected]

[email protected]


Accelario Definitions

WORKFLOW A single work of refresh or copy. After set up it can be activated multiple times after single configuration.

SOURCE DATABASE A database from which we want to copy.

DESTINATION DATABASE A database to which we want to copy.

LINK TO SOURCE The action of linking source server. It is done by default during installation. May be overridden manually during configuration. The link is the same for all workflows.


Software Installation Pre-Requisites

CONTROL WORKSTATION

Memory 512 MB of RAM minimum, 1 GB recommended

Hard disk space 550 MB

Operating system Microsoft® Windows 7 and up Microsoft® Windows Server 2008 and up

Client application Browser: CHROME v32 and up

SOURCE AND DESTINATION DATABASES

SQL Server Versions SQL Server 2008 and up.

Network Direct network connection from destination database server to the source database server is required. For optimal performance 1Gbps and up is recommended.

DESTINATION SERVER PRE CONFIGURATION SQL Server instance is up and running Enough storage to store all the data

Supported platforms - OS Any operation system that runs SQL Server


Stage 1 – Setup

In order to start the setup, collect all the required details: Source SQL Server instance – host, port, instance name, administrator’s username and password. Destination SQL Server instance – same details as above.

Make sure that the Accelario server has sqlcmd.exe utility installed and that it has network connectivity to both servers

Use the supplied script to perform installation. The script will automatically:

Install repository database on the destination Install required objects on the source Create a link between source and destination Add a logon entry to the application Hide and encrypt all passwords

Goto directory APP_DIR\Setup Run script install_server_pair.ps1 providing all the details. The parameters are:

-app_dir <string> - location of Accelario application -source_host <string> - hostname of the source sql server -source_instance <string> - instance name of source sql server (optional) -source_port <number> - port of source sql server (optional) -source_admin_username <string> - source sql server admin username (optional) -source_admin_password <string> - source sql server admin password (optional) -source_awsrds - whether the source sql server is AWS RDS -dest_host <string> - hostname of destination sql server -dest_instance <string> - instance name of destination sql server (optional) -dest_port <number> - port of destination sql server (mandatory, specify 1433 if default) -dest_admin_username <string> - destination sql server admin username (optional) -dest_admin_password <string> - destination sql server admin password (optional) -dest_awsrds - whether the destination sql server is AWS RDS -force - do not confirm connection details, used in batches (optional) -overwrite - overwrite all database objects (optional)

Example for regular database as source and RDS database as destination: powershell .\install_server_pair.ps1 -app_dir C:\acc_mssql_mig\app -source_host

mydatabaseserver -source_port 1433 -dest_host

dest.ch89g65scglg.eu-central-1.rds.amazonaws.com -dest_port

1433 -overwrite -source_admin_username sa -source_admin_password

mypassword -dest_admin_username master -dest_admin_password

mypassword -dest_awsrds

Example for RDS databases as source and destination: powershell .\install_server_pair.ps1 -app_dir C:\acc_mssql_mig\app -source_host

source.ch89g65scglg.eu-central-1.rds.amazonaws.com -source_port

1433 -source_awsrds -dest_host

dest.ch89g65scglg.eu-central-1.rds.amazonaws.com -dest_port

1433 -overwrite -source_admin_username master -source_admin_password

mypassword -dest_admin_username master -dest_admin_password

mypassword -dest_awsrds


Stage 2 – Logon

This screen is used to manage connections to destination servers.

To create new connection press the "New" button.

The following details are required: Host – address of the destination server. This may be the IP address of hostname. Port –port of the database. Usually 1433. Database – repository database name. Authentication – SQL Server or Windows. In case of Windows authentication the login context of Accelario server is used. User – username to login, used in SQL Server authentication. The user should have privileges to perform databases migration. Password – password for the above user.


Security Logon The security mode allows to manage Accelario users with different permissions. It is turned on by default by installation script.

Username field – internal username of Accelario. It is provided by Accelario administrator. The default admin username is “admin” with password “admin123”.

The security mode is controlled by parameter USE_SECURITY in “acc_sys_properties” table in destination server

repository. Set it to 0 in order to disable security mode.


Stage 2 - Configuration

2.1 WORKFLOWS

Choose/create a Workflow and configure it:

* In security mode the non-admin users can see only permitted workflows.

Once the workflow was selected, the application will navigate to configuration wizard.


2.2 LINK TO SOURCE This screen is used to perform a link to source server. The link is created automatically by installation script.

In some cases it is required to recreate the link: Linked server name – the name of linked server that is created in destination server. This linked server is accessible only by the Accelario login. Source server name – the connection details of source server. The syntax is similar to SSMS connection, in form of host\instance,port , where the instance and port are optional. Remote user name – the sql server login on the source server. It should have full access to Accelario database that was used during source installation. Also, it should have read permissions to the databases that should be migrated. Remote password – the password for above login on source server. Press the “Change” button to recreate the link manually.

Switch to Databases Configuration Screen.


2.3 DATABASES CONFIGURATION This screen is used to configure migrated databases

Loading existing databases from the source To load all non-system databases from the source, use the “Load” button on the upper left corner of the screen.

Selecting databases to migrate Choose databases to migrate. Remapping of database names is supported by filling “Dest Database” column with new name. If filled then all objects from source database will be migrated into destination database with new name. If not filled then the destination database name will be the same as the source one (default). It is also allowed to set up location of datafile and logfiles on the destination server for every database. * In security mode the non-admin users can see only permitted databases

Switch to Tables Configuration Screen.


2.4 TABLES CONFIGURATION This screen is used to configure migrated tables

Loading existing Tables from the source To load all tables from source, use the “Load” button on the upper left corner of the screen. In case of AWS RDS as a source, it is required to grant access manually to the Accelario user.

1. Goto SSMS 2. Login to source SQL Server with master user 3. Goto Security-> Logins, locate the Accelario login, its name is started with “Acc…” 4. Open “User Mapping” 5. Locate the required database and set it as “db_owner”

Configuring Tables The following properties are available for every table: Database – the source database name

Schema – the source schema name

Table – the source table name

Partition – the source partition name is available

Masking – button to open masking configuration dialog box.

Priority – control the position of the table in processing queue. Tables with smaller priority are processed earlier (similar

to “priority number one”). Tables with the same priority are processed according to their size – larger tables are processed

earlier.

Where clause – a filter on the table data. Should be a valid sql condition, without the word “where”, for example: age >30

Threads – number of parallel threads to process the table. By default, every table is processed by a single thread (serial

execution).


Configuring Masking A masking configuration dialog box is opened when “Masking” button is clicked in tables’ configuration list.

The dialog box shows list of all columns of the table. Any column can be set up for data masking. If chosen, the column can be masked using various masking algorithms. In cases when built-in algorithms are not enough, you can contact us at [email protected] in order to build new one. * In security mode the non-admin users can only see the masking setup, without the ability to change it.

Switch to Admin Options Screen.

mailto:[email protected]


2.5 ADMIN OPTIONS This screen is used to setup various options for migration process.

* This screen is not allowed for non admin users if security mode is on.

The following options are available: Parallel source – number of parallel processes used to read source server. This is an initial value, can be changed on-the-fly during migration execution. Parallel dest – number of parallel processes used to create indexes on destination server. This is an initial value, can be changed on-the-fly during migration execution. Default diskgroup size – default configuration for any diskgroup that is created by Accelario. Domain source – the name of source domain. Used in domain remapping together with parameter “domain_dest”. Import users – how to handle logins. Available options:

From Dest – copy the logins from destination server From Source – copy the logins from source server Skip – do not handle logins at all

Migration type – how to handle existing object in destination. Available options:

Refresh – drop all existing objects and recreate from the source Clean – expect no existing objects. Fail the migration if any objects in destination found.

Trace flag 610 – whether to set flag 610. It optimizes performance in some versions. Recover model simple – whether to set the destination databases into simple recovery model. This model has the best performance for migration purposes. In addition, it minimizes the usage of log files and tempdb. Link source – the linked server name. it is set automatically during “Link to Source” configuration screen. Max create retries – maximum times to retry creation of objects. Useful in views creation, where there are dependencies between them. Domain dest – the name of destination domain. Used in domain remapping together with parameter “domain_source”. Script recreate database – how to build a script for database creation. Available options are:

From dest – build the database script from the destination server keeping all configured options. From source – build the database script exactly as it is in source server.


2.6 BASIC OPTIONS This screen is a simplified alternative to Admin Options. It is accessible to all users – admin and non-admin.

Overwrite – whether to overwrite destination objects. It is the same as “Migration type” parameter in “Admin options” screen.


Stage 3 - Monitoring

The monitor screens are used to watch the progress of a migration and to control it.

The main screen shows all the groups of a workflow.

The whole workflow can be run or specific group only. To control the whole workgroup, use buttons in the upper right corner. Starting the workflow will always perform all the groups from the beginning to the end. Stopping the workflow will stop any running process, regardless whether they were run individually or in a scope of workflow.

When running group individually use buttons located inside the blue box of the required group. The groups are: Prepare, Copy Data, Create Indexes, and Finalize. The groups should be run in correct order – as they appear on the screen from left to the right.

All the groups may be re-run. More details about rerunning are found later in every group's description. Clicking any group’s box will open lower panel with details. You may use a box refresh button to refresh this panel.

The general log screen may be opened by clicking “Log” link in the center of upper frame. The log screen is opened in another

tab.


3.1 PREPARE GROUP

This group is intended to prepare destination database for migration. It contains several modules that are run subsequently. Every execution of Prepare group will only execute modules that are not finished. This way the group may run incrementally, fixing any errors that come along. In case when everything should be run from scratch – use the “Clear all” button to reset modules’ statuses.


3.2 COPY DATA GROUP

The “General” section displays copy data progress. From this screen, you may change the parallel level in order to improve a workflow performance “on the fly.”

Every time this group runs, it chooses all segments with empty statuses and copies them. The segments are chosen ordered by priority and then by size – meaning that the largest segments are copied first. If a table is partitioned, the partitions are copied independently.

Improve a workflow performance on the fly

The work is done in parallel in number of sessions simultaneously. This method provides full utilization of all resources, like network bandwidth, storage capacity, and CPU allocation. It is crucial to find the optimal level of parallelism, since too small value does not use the systems at full extent and too large value causes overloading. Both cases result in poor performance.


Accelario allows you to monitor every table that is involved in the migration.

The "Segments" grid show following properties: • Clear all – button to reset status of all segments. • Clear Status – button to reset the status of the segment to empty. It is used when the user wants to run the copy of a

segment again. The user is responsible for making sure that the segment is empty. There is a check that verifies it.

• Status – may have next values:

o NOT RUN – not handled yet, it will be processed later

o FINISHED – successfully copied segment

o STARTED – currently being copied

o ERROR – failed to copy

• Database – database name at source server. • Schema – schema name at source server. • Table – table name at source server. • Partition – partition name of the segment at the source server. Empty if non-subpartitioned table. • Start – datetime when a copy has started. Empty if the segment is not handled yet. • End – datetime when a copy has finished (successfully or not). Empty if the segment is not handled yet or is still

running

• Rows handled – number of rows copied. Empty is the segment was not handled successfully.

• Columns masked – number of columns that were data masked.

• Priority – priority of a table in processing queue

• Table Size – size of the table in source server in KB.


3.3 CREATE INDEXES GROUP

The “General” section displays create indexes progress. From this screen, you may change the parallel level in order to improve a workflow performance “on the fly.”

Every time this group runs, it chooses all indexes with empty statuses and creates them. The indexes are chosen ordered by size – meaning that the largest indexes are created first.

Improve a workflow performance on the fly

The work is done in parallel in number of sessions simultaneously. This method provides full utilization of all resources, like network bandwidth, storage capacity, and CPU allocation. It is crucial to find the optimal level of parallelism, since too small value does not use the systems at full extent and too large value causes overloading. Both cases result in poor performance.


Accelario allows you to monitor every index that is involved in this migration. The "Indexes" grid show following properties:

• Clear all – button to reset status of all indexes.

• Clear Status – button to reset the status of the index. It is used when the user wants to run the creation of an index again. The user is responsible for making sure that the index does not exist in destination server.

• Status – may have next values:

o NOT RUN – not handled yet, it will be processed later

o FINISHED – successfully copied segment

o STARTED – currently being copied

o ERROR – failed to copy

• Database – database name at source server.

• Schema – schema name at source server. • Table – table name at source server. • Index – index name at the source server. • Start – datetime when a copy has started. Empty if the segment is not handled yet. • End – datetime when a copy has finished (successfully or not). Empty if the segment is not handled yet or is still

running

• Priority – priority of an index in processing queue

• Index Size – size of the index in source server in KB


3.4 FINALIZE GROUP

This group is intended to complete the migration. It contains several modules that are run subsequently. Every execution of Finalize group will only execute modules that are not finished. This way the group may run incrementally, fixing any errors that come along. In case when everything should be run from scratch – use the “Clear all” button to reset modules’ statuses.


Security users

This screen allows to manage Accelario internal users when it runs in security mode. * This screen is not allowed for non-admin users.

The list of users includes

Username – the login name of an end-user

Admin – Indicator for admin user

Max Parallel – maximum number of parallel processes

Password change – reset user’s password to new one

Delete – delete the user

Database Permission – choose the databases that the user can migrate

Workflow Permission – choose the workflows that the user has access to.

Notes – any text


Appendix 1 – Manually setup auto-login with SQL Server authentication

In case of SQL Server authentication it is supported to allow using Accelario without knowing database password. The use case for this is when end-users are not privileged to login to the SQL server directly, but they are allowed to use Accelario. Use this feature only combined with Accelario Security Logon. This procedure is done automatically by installation script. It may be also done manually. 1. Goto APP_DIR in Accelario server 2. Create hashed value

Goto “Password_auth” directory run : java MdaSha512

Enter the original value – can be any string, e.g. accelario The output is the hashed value, e.g. e0ccfe4d51aa3ad1d5d0c64bed7917f98e81f5f269122e1cc974fa4c20a30c0f05a52af958046ff440c6e727b549142fc923fb1a9b

63a1bb88ab4c52df4f5910

3. Change the password of Accelario login in destination SQL Server to the hashed value above. Make sure that the login is not required to change password at next login

4. Prepare config file Goto “app\conf” directory Create/edit “connection.conf” file Add a line with connection details as a prefix and the original value as suffix, e.g.: 172.45.23.12:1433:accrepo:acc_user:MSSQLSERVER,accelario

In the above example 172.45.23.12 is the address of destination server, 1433 is the port, accrepo is the database,

acc_user is the login, MSSQLSERVER is the instance and accelario is the original value from paragraph 2 above. All the details of connection should be copied exactly from the connection screen. All the strings are case-sensitive. Save the file

5. Refresh the login page in the browser (no need to restart the Accelario server). The connection should display the password field as disabled. Use “Select” button – you should be logged in without prompt for SQL Server password.


Contact Information

For any questions or support issues, please contact us: [email protected]

Company Information

Accelario

43 Brodezki St. Tel Aviv Israel

www.accelario.com

mailto:[email protected]

Date post:	06-Aug-2020
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

User guide - Accelario · Source SQL Server instance – host, port, instance name,...

Documents