Prerequisite setup for sources and targetsSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationPrerequisite setup for sources and targetsPrevNextPrerequisite setup for sources and targetsIn this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:


Connecting with sources and targets over the internetSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationPrerequisite setup for sources and targetsConnecting with sources and targets over the internetPrevNextConnecting with sources and targets over the internetThere are several ways to connect with sources and targets over the internet.... using cloud provider keysSome cloud sources and targets, such as Cosmos DB, secure their connections using keys. No additional configuration is required on your part, you simply provide the appropriate key in the source or target properties.... using an SSH tunnelSee Using an SSH tunnel to connect to a source or target.... by adding an inbound port rule to your firewall or cloud security groupIn your  subscription, go to the Services page.Next to the service, click ... and select Security.Copy StreamShift's IP address.In the firewall or cloud security group for your source or target, create an inbound port rule for that IP address and the port for your database (typically 3306 for MariaDB or MySQL, 1521 for Oracle, 5432 for PostgreSQL, or 1433 for SQL Server).... using port forwardingIn your router configuration, create a port forwarding rule for your database's port. If supported by your router, set the source IP to your database's IP address and the target IP to StreamShift's IP address (which you can get as described above).In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:


Using an SSH tunnel to connect to a source or targetSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationPrerequisite setup for sources and targetsUsing an SSH tunnel to connect to a source or targetPrevNextUsing an SSH tunnel to connect to a source or targetNoteThis feature is available only in Striim Cloud, not in Striim Platform.When you need to connect to a source or target through a jump server, set up an SSH tunnel as follows.In the Striim Cloud Console, go to the Services page. If the service is not running, start it and wait for its status to change to Running.Next to the service, click ... and select Security.Click Create New Tunnel and enter the following:Name: choose a descriptive name for this tunnelJump Host: the IP address or DNS name of the jump serverJump Host Port: the port number for the tunnelJump Host Username: the jump host operating system user account that Striim Cloud will use to connectDatabase Host: the IP address or DNS name of the source or target databaseDatabase Port: the port for the databaseClick Create Tunnel. Do not click Start yet.Under Public Key, click Get Key > Copy Key.Add the copied key to your jump server's authorized keys file, then return to the Striim Cloud Security page and click Start. The SSH tunnel will now be usable in the source or target settings.Give the user specified for Jump Host Username the necessary file system permissions to access the key.Under Tunnel Address, click Copy to get the string to provide as the host name.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:


Cosmos DB setupSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationPrerequisite setup for sources and targetsCosmos DB setupPrevNextCosmos DB setupCosmos DB is supported only as a target and only using the Core (SQL) API with provisioned throughput (see How to choose between provisioned throughput and serverless).In the Data Explorer for the target Cosmos DB account, click New Database. For simplicity, you may wish to use the source database's name as the Cosmos DB database ID.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

Cosmos DB setup


MySQL / MariaDB setupSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationPrerequisite setup for sources and targetsMySQL / MariaDB setupPrevNextMySQL / MariaDB setupSource setupIf the source and target are both MySQL and you are doing a "Lift and Shift only" migration, create a user for use by Striim and grant it SELECT privileges on all tables to be migrated.In all other cases (including when the source and target are both MariaDB), set up the source as described in MySQL / MariaDB setup.Target setupCreate the target database(s).Create a CHKPOINT table in one of the target databases.CREATE TABLE CHKPOINT (
  id VARCHAR(100) PRIMARY KEY,
  sourceposition BLOB,
  pendingddl BIT(1),
  ddl LONGTEXT);Create a user for use by Striim as follows, replacing ******** with a strong password. You may use any user name you wish.CREATE USER 'striim'@'%' IDENTIFIED BY '********';
GRANT ALTER, CREATE, DELETE, DROP, INSERT, SELECT ON *.* TO 'striim'@'%';If the source and target are both MySQL, add these additional privileges:GRANT ALTER ROUTINE, CREATE ROUTINE, CREATE VIEW, EVENT, LOCK TABLES, REFERENCES, RELOAD,
  REPLICATION CLIENT, TRIGGER, UPDATE ON *.* TO 'striim'@'%';In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

MySQL / MariaDB setup


Oracle setupSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationPrerequisite setup for sources and targetsOracle setupPrevNextOracle setupSource setupIf the source and target are both Oracle and you are doing a "Lift and Shift only" migration, create a user for use by Striim and grant it SELECT privileges on all tables to be migrated.In all other cases, set up the source as described in Basic Oracle configuration tasks, Creating an Oracle user with LogMiner privileges, and Creating the quiescemarker table. If your source database is PDB, also grant the Oracle user the ALTER SESSION privilege.Target setupCreate the target schema(s).Create a CHKPOINT table in one of the target schemas:CREATE TABLE CHKPOINT (
  ID VARCHAR2(100) PRIMARY KEY,
  SOURCEPOSITION BLOB,
  PENDINGDDL NUMBER(1),
  DDL CLOB);Create a role and user for use by Striim as follows, replacing ******** with a strong password. You may use any role or user name you wish.CREATE ROLE STRIIM_PRIVS;
GRANT CREATE SESSION TO STRIIM_PRIVS;
GRANT CREATE USER TO STRIIM_PRIVS;
GRANT CREATE ANY TABLE TO STRIIM_PRIVS;
GRANT SELECT ANY TABLE TO STRIIM_PRIVS;
GRANT ALTER ANY TABLE TO STRIIM_PRIVS;
GRANT INSERT ANY TABLE TO STRIIM_PRIVS;
GRANT UPDATE ANY TABLE TO STRIIM_PRIVS;
GRANT DROP ANY TABLE TO STRIIM_PRIVS;
GRANT CREATE ANY INDEX TO STRIIM_PRIVS;
GRANT UNLIMITED TABLESPACE TO STRIIM_PRIVS WITH ADMIN OPTION;
GRANT SELECT_CATALOG_ROLE TO STRIIM_PRIVS;
CREATE USER STRIIM IDENTIFIED BY ******** DEFAULT TABLESPACE USERS;
GRANT STRIIM_PRIVS TO STRIIM;If the source is also Oracle, add these additional privileges:GRANT SELECT ANY DICTIONARY TO STRIIM_PRIVS;
GRANT DATAPUMP_IMP_FULL_DATABASE TO STRIIM_PRIVS;
GRANT EXECUTE ANY PROCEDURE TO STRIIM_PRIVS;In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

Oracle setup


PostgreSQL setupSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationPrerequisite setup for sources and targetsPostgreSQL setupPrevNextPostgreSQL setupSource setupIf the source and target are both PostgreSQL and you are doing a "Lift and Shift only" migration, create a user for use by Striim and grant it SELECT privileges on all tables to be migrated.In all other cases, set up the source as described in PosgreSQL setup.Target setupIf you are migrating only one schema and plan to use the default public schema, skip this step. Otherwise, create the target schema(s).Create a CHKPOINT table in one of the target schemas:create table chkpoint (
  id character varying(100) primary key,
  sourceposition bytea,
  pendingddl numeric(1),
  ddl text);Create a role for use by Striim as follows, replacing ******** with a strong password. You may use any role name you wish.CREATE ROLE striim WITH LOGIN PASSWORD '******';
GRANT CONNECT ON DATABASE <database name> TO striim;
GRANT CREATE ON DATABASE <database name> TO striim;
In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

PostgreSQL setup


SQL Server setupSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationPrerequisite setup for sources and targetsSQL Server setupPrevNextSQL Server setupSource setupIf the source and target are both SQL Server and you are doing a "Lift and Shift only" migration, create a user for use by Striim and grant it SELECT permission on all tables to be migrated.In all other cases, set up the source as described in SQL Server setup or, if the source is in an Azure virtual machine, Configuring an Azure virtual machine running SQL Server.Target setupIf you are migrating only one schema and plan to use the default dbo schema, skip this step. Otherwise, create the target schema(s).Create a CHKPOINT table in one of the target schemas:REATE TABLE CHKPOINT (
  id VARCHAR(100) PRIMARY KEY,
  sourceposition VARBINARY(MAX),
  pendingddl BIT,
  ddl VARCHAR(MAX));Create a user for use by Striim as follows, replacing ******** with a strong password. You may use any user name you wish.USE <database name>;
CREATE LOGIN striim WITH PASSWORD = '********';
CREATE USER striim FOR LOGIN striim;
EXEC sp_addrolemember @rolename=db_owner, @membername=striim;
In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

SQL Server setup


Migrating a database with StreamShiftSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftPrevNextMigrating a database with StreamShiftIn this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

Migrating a database with StreamShift


Subscribe to StreamShift in the AWS MarketplaceSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplacePrevNextSubscribe to StreamShift in the AWS MarketplaceIn the AWS Marketplace, search for StreamShift by Striim and click it.Click View purchase options.Select how long you want your contract to run, whether to automatically renew it, and which plan you want, then click Create contract > Pay now > Set up your account.In the Sign up for Striim Cloud dialog, enter your name, email address, company name, your desired sub-domain (part of the URL where you will access Striim Cloud), and password, then click Sign up.When you receive the Activate your account email, open it and click the activation link.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:


Subscribe to StreamShift in the Microsoft Azure MarketplaceSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftSubscribe to StreamShift in the Microsoft Azure MarketplacePrevNextSubscribe to StreamShift in the Microsoft Azure MarketplaceIn the Azure Marketplace, search for StreamShift and click it.Click Get It Now, check the box to accept Microsoft's terms, and click Continue.Select a plan, then click Subscribe.Select one of your existing resource groups or create a new one, enter a name for this subscription, and click Review + subscribe.Click Subscribe.When you receive an "Activate your Striim Cloud Enterprise" email from Microsoft AppSource, open it and click Activate now.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:


Subscribe to StreamShift in the Google Cloud MarketplaceSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftSubscribe to StreamShift in the Google Cloud MarketplacePrevNextSubscribe to StreamShift in the Google Cloud MarketplaceIn the Google Cloud Platform Marketplace, search for StreamShift and click it.Scroll down to Pricing, select a plan, and click Select.Scroll down to Additional terms, check to accept them all, and click Subscribe.Click Register with Striim Inc., then follow the instructions to complete registration. Make a note of the domain and password you enter.When you receive the Striim for BigQuery | Activate your account email, open it and click the activation link.Enter your email address and password, then click Sign up.You will receive another email with information about your subscription.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:


Create a StreamShift serviceSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftCreate a StreamShift servicePrevNextCreate a StreamShift serviceOn the Services page, click Create new, then under StreamShift click Create.Enter a name for your service, then click Create.Your new service will not be usable until its status is Running.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

Create a StreamShift service


Create a StreamShift projectSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftCreate a StreamShift projectPrevNextCreate a StreamShift projectOn the Services page, click Launch for your service, then click Create Project.Enter a name for your project, then click Create.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

Create a StreamShift project


Choose your migration typeSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftChoose your migration typePrevNextChoose your migration typeSee Lift and Shift versus Ongoing Synchronization. For most customers, the right choice is Lift and Shift with Ongoing Synchronization. After you have made your choice, click Next.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

Choose your migration type


Select and connect to your source databaseSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftSelect and connect to your source databasePrevNextSelect and connect to your source databaseAfter you create a new project, StreamShift will prompt you to select your source database type.If your source is running on your own hardware or your own virtual machine, select MariaDB, MySQL, Oracle, PostgreSQL, or SQL Server. If your source is in Amazon AWS, Microsoft Azure, or Google Cloud, select AWS, Azure, or Google, then the database type. For AWS, note that there are both Aurora and RDS versions of MySQL and PostgreSQL.StreamShift will prompt you to enter the connection details, including:Host name, IP address, or SSH tunnel name (see Connecting with sources and targets over the internet). If you are not using an SSH tunnel, StreamShift must be able to connect to the host over the public Internet, for example via port forwarding or IP allowlisting.port for the database host (not for the SSH tunnel)for Oracle, the SID or service name of the schema(s) to be migratedfor PostgreSQL or SQL Server, the name of the database containing schemas to be migratedusername and password (see Prerequisite setup for sources and targets)If the connection will use SSL, check Use SSL. See Configure SSL for more information.When done, click Next. If StreamShift is unable to connect to the source, correct any settings or perform any prerequisite tasks (see Prerequisite setup for sources and targets) as necessary, then click Next to try again. When you see the source profile, click Next.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:


Configure SSLSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftConfigure SSLPrevNextConfigure SSLIf you select Use SSL in source or target properties, set the options as follows.CautionIn all cases, replace mypassword with a secure password.... for Amazon RDS for MariaDBUsing SSL certificates is optional.Download the root certificate rds-ca-2019-root.pem.Import that certificate into a custom Java truststore file:keytool -importcert -alias MariaCACert -file rds-ca-2019-root.pem \
  -keystore clientkeystore.jks -storepass mypassword In Streamshift SSL UI:SSL - check this box to set to true ( The client must set this property in order to use encrypted connections )Verify Server Certificate - check this box or set to true. ( On setting it to true, all the ssl certificates mentioned below will be verified while establishing the connection. )Trust Certificate Key Store Url - upload the certificate key store file clientkeystore.jks created as part of step 2.Trust Certificate Key Store Type - provide the store type as specified (eg.JKS) in step 2.Trust Certificate Key Store Password - set the value specified in --storepass in step 2.Trust Certificate: if you selected Lift and Shift only and the source and target are both MariaDB, upload the rds-ca-2019-root.pem root certificate downloaded in step 1. Otherwise leave blank.... for MariaDB on premiseUsing SSL certificates is optional.To import the certificate (must be in .pem format) into a custom Java truststore file:keytool -importcert -alias MariaCACert -file server-ca.pem \
  -keystore truststore.jks -storepass mypassword Client Certificate Settings:Convert client keys/certificate files to PKCS#12 before creating a keystoreopenssl pkcs12 -export -in client-cert.pem -inkeyclient-key.pem \
  -name “mysqlclient” -passoutpass:mypassword -out client-keystore.p12Create a Java Keystore using the client-keystore.p12 filekeytool -importkeystore -srckeystore client-keystore.p12-srcstoretype pkcs12 \
  -srcstorepass mypassword-destkeystore keystore.jks -deststoretype JKS \
  -deststorepassmypasswordIn Streamshift SSL UI:SSL - check this box to set to true ( The client must set this property in order to use encrypted connections )Verify Server Certificate - check this box or set to true. ( On setting it to true, all the ssl certificates mentioned below will be verified while establishing the connection. )Trust Certificate Key Store Url - upload the certificate key store file truststore.jks created as part of step 1.Trust Certificate Key Store Type - provide the store type as specified (eg.JKS) in step 1.Trust Certificate Key Store Password - set the value specified in --storepass in step 1.Client Certificate Key Store Url - upload the certificate key store file keystore.jks created as part of step 2.Client Certificate Key Store Type - provide the store type as specified (eg.JKS) in step 2.Client Certificate Key Store Password- set the value specified in --deststorepass in step 2.If you selected Lift and Shift only and the source and target are both MariaDB, set these additional properties:Trust Certificate - Upload server-ca.pemClient Certificate - Upload client-cert.pemClient Certificate Key- Upload client-key.pem... for Amazon RDS for MySQLUsing SSL certificates is optional.Download root certificate rds-ca-2019-root.pem.To import the certificate into a custom Java truststore file:keytool -importcert -alias MySQLCACert -file rds-ca-2019-root.pem \
  -keystore clientkeystore.jks -storepass mypasswordIn Streamshift SSL UI:SSL - check this box to set to true ( The client must set this property in order to use encrypted connections )Verify Server Certificate - check this box to set it to true. ( On setting it to true, all the ssl certificates mentioned below will be verified while establishing the connection. )Trust Certificate Key Store Url - upload the certificate key store file clientkeystore.jks created as part of step 2.Trust Certificate Key Store Type - provide the store type as specified (eg.JKS) in step 2.Trust Certificate Key Store Password - set the value specified in --storepass in step 2.Trust Certificate: if you selected Lift and Shift only and the source and target are both MySQL, upload the rds-ca-2019-root.pem certificate downloaded in step 1. Otherwise leave blank.... for Azure Database for MySQLUsing SSL certificates is optional.Download BaltimoreCyberTrustRoot.crt.pem & DigiCertGlobalRootG2.crt.pem certificatesCreate truststore files:keytool -importcert -alias MySQLServerCACert -file /path...../BaltimoreCyberTrustRoot.crt.pem-keystore \
  truststore.jks -storepass password -noprompt
keytool -importcert -alias MySQLServerCACert2 -file /path...../DigiCertGlobalRootG2.crt.pem-keystore \
  truststore.jks -storepass password -nopromptIn Streamshift SSL UI:SSL - check this box to set to true ( The client must set this property in order to use encrypted connections )Verify Server Certificate - check this box to set to true. ( On setting it to true, all the ssl certificates mentioned below will be verified while establishing the connection. )Trust Certificate Key Store Url - upload the certificate key store file truststore.jks created as part of step 2.Trust Certificate Key Store Type - provide the store type as specified (eg.JKS) in step 2.Trust Certificate Key Store Password - set the value specified in --storepass in step 2.Trust Certificate: if you selected Lift and Shift only and the source and target are both MySQL, upload the BaltimoreCyberTrustRoot.crt.pem certificate downloaded in step 1. Otherwise leave blank.... for Google Cloud SQL for MySQLUsing SSL certificates is optional.Download server-ca.pem, client-cert.pem & client-key.pem from GCP.To import the certificate into a custom Java truststore file:keytool -importcert -alias MySQLCACert -file server-ca.pem -keystore truststore.jks \
  -storepass mypasswordClient certificate settings:Convert client keys/certificate files to PKCS#12:openssl pkcs12 -export -in client-cert.pem -inkeyclient-key.pem \
  -name “mysqlclient” -passoutpass:mypassword -out client-keystore.p12Create a Java Keystore using the client-keystore.p12 file:keytool -importkeystore -srckeystore client-keystore.p12-srcstoretype pkcs12 \
  -srcstorepass mypassword-destkeystore keystore.jks \
  -deststoretype JKS-deststorepass mypasswordIn Streamshift SSL UI:SSL - check this box to set to true ( The client must set this property in order to use encrypted connections )Verify Server Certificate - check this box to set it to true. ( On setting it to true, all the ssl certificates mentioned below will be verified while establishing the connection. )Trust Certificate Key Store Url - upload the certificate key store file truststore.jks created as part of step 2.Trust Certificate Key Store Type - provide the store type as specified (eg.JKS) in step 2.Trust Certificate Key Store Password - set the value specified in --storepass in step 2.Client Certificate Key Store Url - upload the certificate key store file keystore.jks created as part of step 3.Client Certificate Key Store Type - provide the store type as specified (eg.JKS) in step 3.Client Certificate Key Store Password- set the value specified in --deststorepass in step 3.If you selected Lift and Shift only and the source and target are both MySQL, set these additional properties:Trust Certificate - Upload server-ca.pemClient Certificate - Upload client-cert.pemClient Certificate Key- Upload client-key.pem... for MySQL on premiseUsing SSL certificates is optional.To import the certificate (must be in .pem format) nto a custom Java truststore file:keytool -importcert -alias MariaCACert -file server-ca.pem \
  -keystore truststore.jks -storepass mypassword Convert client keys/certificate files to PKCS#12:openssl pkcs12 -export -in client-cert.pem -inkeyclient-key.pem \
  -name “mysqlclient” -passoutpass:mypassword -out client-keystore.p12Create a Java Keystore using the client-keystore.p12 file:keytool -importkeystore -srckeystore client-keystore.p12-srcstoretype pkcs12 \
  -srcstorepass mypassword-destkeystore keystore.jks \
  -deststoretype JKS-deststorepass mypasswordIn Streamshift SSL UI:SSL - check this box to set to true (The client must set this property in order to use encrypted connections )Verify Server Certificate - check this box to set it to true. ( On setting it to true, all the ssl certificates mentioned below will be verified while establishing the connection. )Trust Certificate Key Store Url - upload the certificate key store file truststore.jks created as part of step 2.Trust Certificate Key Store Type - provide the store type as specified (eg.JKS) in step 2.Trust Certificate Key Store Password - set the value specified in --storepass in step 2.Client Certificate Key Store Url - upload the certificate key store file keystore.jks created as part of step 3.Client Certificate Key Store Type - provide the store type as specified (eg.JKS) in step 3.Client Certificate Key Store Password- set the value specified in --deststorepass in step 3.If you selected Lift and Shift only and the source and target are both MySQL, set these additional properties:Trust Certificate - Upload server-ca.pemClient Certificate - Upload client-cert.pemClient Certificate Key- Upload client-key.pem... for Amazon RDS for OracleAn SSL certificate is required.Download root certificate rds-ca-2019-root.pem.To import the certificate into a custom Java truststore file:keytool -importcert -alias OracleCACert -file rds-ca-2019-root.pem \
 -keystore clientkeystore.jks -storepass mypasswordIn Streamshift SSL UI:SSL - check this box to set to trueTrust store - upload this certificate key store file clientkeystore.jks created as part of step 2.Trust store type - JKSTrust store password - set the value specified in --storepass in step 2.Trust Certificate: if you selected Lift and Shift only and the source and target are both Oracle, upload the rds-ca-2019-root.pem root certificate downloaded in step 1. Otherwise leave blank.... for Oracle on premiseAn SSL certificate is required.To import the certificate(.pem format) into a custom Java truststore file:keytool -importcert -alias OracleCACert -file server-ca.pem \
  -keystore truststore.jks -storepass mypasswordConvert client keys/certificate files to PKCS#12 before creating a keystore:openssl pkcs12 -export -in client-cert.pem -inkey client-key.pem \
  -name “mysqlclient” -passout pass:mypassword -out client-keystore.p12Create a Java Keystore using the client-keystore.p12 file:keytool -importkeystore -srckeystore client-keystore.p12 -srcstoretype pkcs12 \
  -srcstorepass mypassword -destkeystore keystore.jks -deststoretype JKS \
  -deststorepass mypasswordIn Streamshift SSL UI:SSL - check this box to set to trueTrust store - upload this certificate key store file truststore.jks created as part of step 1.Trust store type - provide the store type as specified (eg.JKS) in step 1.Trust store password - set the value specified in --storepass in step 1.Key Store - upload this certificate key store file keystore.jks created as part of step 3.Key Store Type - provide the store type as specified (eg.JKS) in step 3.Key Store Password- set the value specified in --deststorepass in step 3.Additional properties for Lift and Shift Only from Oracle to Oracle (homogenous migration):... for Amazon RDS for PostgreSQLUsing SSL certificates is optional.Download root certificate rds-ca-2019-root.pem.In Streamshift SSL UI:SSL - check this box to set to true ( The client must set this property in order to use encrypted connections )SSL Mode - disable / allow / prefer / require /verify-ca, based on the type of encryption and validation required for the user (verify-full is not supported)SSL Root Certificate - upload the downloaded root certificate mentioned in step 1... for Azure Database for PostgreSQLUsing SSL certificates is optional.Download BaltimoreCyberTrustRoot.crt.pem certificate.In Streamshift SSL UI:SSL - check this box to set to true ( The client must set this property in order to use encrypted connections )SSL Mode - disable / allow / prefer / require /verify-ca , based on the type of encryption and validation required for the user (verify-full is not supported)SSL Root Certificate - upload the downloaded root certificate mentioned in step 1... for Google Cloud SQL for PostgreSQLUsing SSL certificates is optional.Download server-ca.pem, client-cert.pem & client-key.pem from GCP.Convert client-key.pem to .pk8 format:openssl pkcs8 -topk8 -inform PEM -outform DER -inclient-key.pem -out client.root.pk8 \
  -nocryptIn Streamshift SSL UI:SSL - check this box to set to true ( The client must set this property in order to use encrypted connections )SSL Mode - disable / allow / prefer / require /verify-ca , based on the type of encryption and validation required for the user (verify-full is not supported)SSL Certificate - upload the downloaded certificate client-cert.pem mentioned in step 1.SSL Certificate Key (in .pk8 format) - upload the certificate key file client.root.pk8 specified in step 1.SSL Root Certificate - upload the downloaded root certificate server-ca.pem mentioned in step 1Client Certificate Key: if you selected Lift and Shift only and the source and target are both PostgreSQL, upload the client-key.pem file downloaded in step 1. Otherwise leave blank.... for PostgreSQL on premiseUsing SSL certificates is optional.Convert client-key.pem to .pk8 format:openssl pkcs8 -topk8 -inform PEM -outform DER -in client-key.pem -out client.root.pk8 \
  -nocryptIn Streamshift SSL UI:SSL - check this box to set to true ( The client must set this property in order to use encrypted connections )SSL Mode - disable / allow / prefer / require /verify-ca , to match the type of encryption and validation required for the user (verify-full is not supported)SSL Certificate - upload the created SSL certificate client-cert.pemSSL Certificate Key (in .pk8 format) - upload the certificate key file client.root.pk8 specified in step 1.SSL Root Certificate - upload the created root certificate server-ca.pemClient Certificate Key: if you selected Lift and Shift only and the source and target are both PostgreSQL, upload the client-key.pem file downloaded in step 1. Otherwise leave blank.... for Amazon RDS for SQL ServerUsing SSL certificates is optional.Download the root certificate rds-ca-2019-root.pem.Import that certificate into a custom Java truststore file:keytool -importcert -alias MSSQLCACert -file rds-ca-2019-root.pem \
  -keystore clientkeystore.jks -storepass mypassword In Streamshift SSL UI:SSL - check this box to set to true (The client must set this property in order to use encrypted connections)Use Trust Server Certificate - check this box or set to trueIntegrated Security - check this box or set to true (If “true”, it indicates that Windows credentials are used by SQL Server on Windows OS. The JDBC driver searches the local computer credential cache for credentials that were provided when a user signed in to the computer or network. If "false", the username and password must be supplied)Trust Store - upload the certificate key store file clientkeystore.jks created as part of step 2.Trust Store Password - set the value specified in --storepass in step 2.Certificate Host Name - Host name of the server used to validate the SQL Server TLS/SSL certificate. (Eg : *.database.windows.net )... for Azure SQL Database or Azure SQL Managed InstanceUsing SSL certificates is optional.Download BaltimoreCyberTrustRoot.crt.pem & DigiCertGlobalRootG2.crt.pem certificatesCreate truststore files:keytool -importcert -alias MSSQLServerCACert \
  -file /path...../BaltimoreCyberTrustRoot.crt.pem-keystore truststore.jks \
  -storepass password -noprompt
keytool -importcert -alias MSSQLServerCACert2 \
  -file /path...../DigiCertGlobalRootG2.crt.pem-keystore truststore.jks \
  -storepass password -nopromptIn Streamshift SSL UI:SSL - check this box to set to true (The client must set this property in order to use encrypted connections)Use Trust Server Certificate - check this box or set to trueIntegrated Security - check this box or set to true (If “true”, it indicates that Windows credentials are used by SQLServer on Windows OS. The JDBC driver searches the localcomputer credential cache for credentials that were providedwhen a user signed in to the computer or networkIf "false", the username and password must be supplied.)Trust Store - upload the certificate key store file truststore.jks created as part of step 2.Trust Store Password - set the value specified in --storepass in step 2.Certificate Host Name - Host name of the server used to validate the SQL Server TLS/SSL certificate. ( Eg : *.database.windows.net )... for Google Cloud SQL for SQL ServerUsing SSL certificates is optional.Download server-ca.pem from GCP.To import the certificate into a custom Java truststore file:keytool -importcert -alias MSSQLCACert -file server-ca.pem-keystore truststore.jks \
  -storepass mypasswordIn Streamshift SSL UI:SSL - check this box to set to true (The client must set this property in order to use encrypted connections )Use Trust Server Certificate - check this box or set to trueIntegrated Security - check this box or set to true (If “true”, it indicates that Windows credentials are used by SQLServer on Windows OS. The JDBC driver searches the localcomputer credential cache for credentials that were providedwhen a user signed in to the computer or networkIf "false", the username and password must be supplied.)Trust Store - upload the certificate key store file truststore.jks created as part of step 2.Trust Store Password - set the value specified in --storepass in step 2.Certificate Host Name - Host name of the server used to validate the SQL Server TLS/SSL certificate. ( Eg : *.database.windows.net )... for SQL Server on premiseUsing SSL certificates is optional.Create server-ca.pemTo Create truststore file, use the following command:keytool -importcert -alias MSSQLCACert -file server-ca.pem-keystore truststore.jks \
  -storepass mypasswordIn StreamShift SSL UI:SSL - check this box to set to true ( The client must set this property in order to use encrypted connections )Use Trust Server Certificate - check this box or set to trueIntegrated Security - check this box or set to true (If “true”, it indicates that Windows credentials are used by SQLServer on Windows OS. The JDBC driver searches the localcomputer credential cache for credentials that were providedwhen a user signed in to the computer or networkIf "false", the username and password must be supplied.)Trust Store - upload the certificate key store file truststore.jks created as part of step 2.Trust Store Password - set the value specified in --storepass in step 2.Certificate Host Name - Host name of the server used to validate the SQL Server TLS/SSL certificate. ( Eg : *.database.windows.net )In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

Configure SSL


Select and connect to your target databaseSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftSelect and connect to your target databasePrevNextSelect and connect to your target databaseSelect your target database type as described in Select and connect to your source database.Optionally, to preserve case-sensitive table names in the target, check Retain case sensitivity of object names.CautionIf you are migrating source tables with the same names except for the case (for example, employees and Employees), you must check Retain case sensitivity of object names to avoid errors in migration.If your target is Cosmos DB:for the Service endpoint, enter the URI from your Azure Cosmos DB account's Keys tab.for the Access key, enter the Primary Key from your Azure Cosmos DB account's Keys tab.For other targets, enter your connection details as described in Select and connect to your source database.When you have entered the connection properties, click Next.If any of the prerequisite checks fail, correct any settings or perform any prerequisite tasks as necessary, then click Next to try again.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:


Select what to migrateSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftSelect what to migratePrevNextSelect what to migrateSelect the schema(s) or database(s) to migrate, then click Assess schemas.For PostgreSQL sources, the database may have only the default schema, in which case, select public.For SQL Server sources, the database may have only the default schema, in which case, select dbo.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

Select what to migrate


Understanding the assessment and compatibility reportsSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftUnderstanding the assessment and compatibility reportsPrevNextUnderstanding the assessment and compatibility reportsAfter you select the schema(s) to migrate and click Assess, StreamShift will analyze the complexity of the source data and its compatibility with the target database.The Assessment report may be helpful in planning multiple migrations, or a single migration so large that it may take days or weeks. This report will be displayed in the right-hand panel during the Customize phase. See How the assessment score is calculated for more information.The Compatibility report shows which source tables have data types or other attributes that can not be read or are incompatible with the target. Click Customize to resolve these issues. See How the compatibility score is calculated for more information.When the target is Cosmos DB, which does not have data types, there are no incompatible data types, but source tables may still be shown as incompatible because they cannot be read.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:


How the assessment score is calculatedSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftUnderstanding the assessment and compatibility reportsHow the assessment score is calculatedPrevNextHow the assessment score is calculatedIn database migrations scenarios, the assessment score is primarily relevant for the source database since the target database is usually empty and new.The score is calculated based on multiple factors including the type, object structure, schema diversity, cardinality and data characteristics of the underlying database.In general, given a database migration scenario for a specific source and target combination, the higher the source database assessment score, the larger is the effort to migrate this database with respect to another source database with a lower assessment score.For example, In an Oracle to PostgreSQL database migration scenario:Given two Source Oracle Databases SALES, and FIN with the following assessment scores:Source Database SALES : Score 50000Source Database FIN : Score 25000And a target database Azure PostGreSQL, it would require more effort to migrate database SALES to the target PostgreSQL database, as compared to database FIN using the same migration technique.As you plan, customize and undertake your migration activities, you can run multiple assessments and see how this score iteratively changes. For example, excluding certain tables or schemas from migration and rerunning the assessment should lower the assessment score, and in turn the migration effort.Score calculationThere are various factors to be considered when planning for a migration. Specifically these factors affect migration in terms of duration, requiring more migration compute resources and special handling of the migration application.When migrating a specific table, Streamshift has identified following factors affecting the migration:Table sizeTotal number of tablesTotal number of columnsTotal number of rows in a tablesPresence of primary and unique keysTable containing special column types.Rather than looking at the above factors individually and evaluating the total cost involved(in terms of duration, migration resources), Streamshift will assign a specific score to each factor and the total value of all these factors are presented as a score. For example, higher the Assessment score results in higher cost of migration in terms of longer duration, higher migration compute resources.Also migration complexity can be evaluated when comparing the assessment score for a table against its source and target database type. To compute such migration complexity involving various factors such as data types, primary keys, no of columns, a simple representation of total assessment score involving such factors will help us to compute such complexity rather than evaluating complexity against various criteria (or factors) of a given table.Streamshift assignment of scores are documented in the following link - Assessment Calculation Matrix.Examples1. table containing simple data typesHere are the characteristics of the table:Table containing three columns - ID int, Name VARCHAR2(50), AGE intTable containing ID being a primary key columnTotal number of total rows - 1,000,000Total size of the table is 100 MBFrom the Assessment Calculation Matrix, let us consider the various factors associated with the table:FactorsValueCategoryScoreColumn count3Narrow Table100Size100 MBSmall table100Row Count1,000,000Ultra long table400Primary key Column110Data types3Simple3Total6132. table containing complex data typesHere are the characteristics of the table:Table containing columns id int, name VARCHAR2(50), age int , resume BLOB, hiring_date DATETable containing ID being a primary key columnTotal number of total rows - 1,000,000Total size of the table is 10 GBFrom the Assessment Calculation Matrix, let us consider the various factors associated with the table:FactorsValueCategoryScoreColumn count5Narrow Table100Size10 GBLarge table10000Row Count1,000,000Ultra long table400Primary key Column110Data types3Simple3Date types2Complex (Blob, Date)13Total105263. Wide table containing simple and complex data typesHere are the characteristics of the table:Table containing 50 columns: 30 of simple data types, 10 of date, 10 of XMLTable containing three columns being a primary key columnTotal number of total rows - 1,000Total size of the table is 1000 MBFrom the Assessment Calculation Matrix, let us consider the various factors associated with the table:FactorsValueCategoryScoreColumn count50Wide Table200Size1 GBMedium table1000Row Count1000Long table200Primary key Column330Data types30Simple30Date types10Complex (Blob, Date)230 (200 for XML, 30 for Date)Total1690Computing Migration CompatibilityComputing Migration CompatibilityIn this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

How the assessment score is calculated


How the compatibility score is calculatedSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftUnderstanding the assessment and compatibility reportsHow the compatibility score is calculatedPrevNextHow the compatibility score is calculatedMigration compatibility (expressed in terms of %) helps to find out how easy to move a given table from one source database type to target database type.Take the example of ‘Wide table containing simple and complex data type’ and compatibility has to be calculated between Oracle source and Postgres target database.Here are the characteristics of the table:Table containing 50 columns30 columns of simple data types, 10 columns of date, 10 columns of XMLTable containing three columns being a primary key columnsTotal number of total rows - 1,000Total size of the table is 1000 MBAgain, analysing each factor of the table and its compatibility with the source and target database and adjusting the score based on the supported factors will help us to find out the migration compatibility.FactorsValueTarget Postgres compatibilityOracle ScoreTarget ScoreColumn count50Postgres supports table with 50 columns200200Size1 GBPostgres supports table of 1 GB size10001000Row Count1000Postgres supports table with 1000 rows200200Primary key Column3Postgres supports table with PK3030Data types30Postgres supports all simple data types3030Data types - Date10Postgres supports Date datatype3030Data types - XML10Postgres does not supports XML datatype200-Total16901490Total migration compatibility (computed as % of Target score/Source score) = 1490/1690 = 88.1%In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:


Customize the migration and migrate the schemaSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftCustomize the migration and migrate the schemaPrevNextCustomize the migration and migrate the schemaIf you skipped configuring your target database connection in the Configure phase, click the Configure button to do so now.If the target schema(s) or database(s) do not have the same name as the source schema(s) or database(s), click Edit and adjust as necessary. When the mapping is correct, click Next.NoteFor PostgreSQL targets, the database may have only the default public schema. For SQL Server targets, the database may have only the default dbo database.In this phase, StreamShift shows three categories of compatibility:Compatible: can be migrated to target. Optionally, select Edit SQL to modify the DDL for the target, for example if you disagree with the Striim Intelligence data type mapping detailed in the Compatibility report.Incompatible, Edit SQL enabled: can not be migrated to target without modification. For example, StreamShift might not have been able to determine a compatible data type. For these tables, you have the following options:Select Edit SQL to modify the DDL for the target table, for example, to replace <source data type>_STRIIM_UNKNOWN with a compatible target data type.Select ... > Exclude columns to select incompatible columns to exclude from the migration.Select ... > Exclude table to omit the table from the migration.Incompatible, Edit SQL disabled: can not be migrated to target. For example, the source table may have attributes that make it incompatible with change data capture. Select ... > Exclude table to omit the table from the migration. Alternatively, abandon the StreamShift project, alter the source database to eliminate the compatibility, and start over with a new project.The process is similar for making foreign keys compatible.KNOWN ISSUE (SMS-1373): if a table is excluded, foreign keys that require it still show as compatible.NoteFor Cosmos DB targetsDuring customization, only Exclude table is available, not Exclude column or Edit SQL.Foreign keys are not migrated as they do not exist in Cosmos DB.StreamShift will create a Cosmos DB database for each schema to be migrated, and a container for each source table to be migrated.Containers default to Shared throughput. If that is not appropriate for your Cosmos DB account, change it to Autoscale or Manual.You must define a partition key for each container (see Choosing a partition key).Primary key updates in the source are handled as a delete followed by an insert in the CosmosDB target.When you have dealt with all the incompatibilities, click Migrate Schema. When the migration is complete StreamShift will display a summary.KNOWN ISSUE (SMS-1863): StreamShift may attempt to migrate foreign keys in the wrong order, resulting in some that were reported as compatible failing to migrated. If this happens, click Retry all failed schemas.When schema migration is complete, click Configure CDC Capture.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:


Migrate the dataSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftMigrate the dataPrevNextMigrate the dataTypically you will not need to make changes on the Configure CDC Capture page unless instructed to by StreamShift support. Click Configure CDC Apply to continue.On the Configure CDC Apply page, you may be able to speed up data migration by creating table groups to allow StreamShift to migrate them in parallel. For example, if one table contains 50% of the data, moving it to its own table group could reduce migration time by up to half.Typically you will not need to make other changes on this page unless instructed to by StreamShift support. Click Migrate Data to continue. Since data may be written out of order, to avoid errors StreamShift will not apply the foreign keys yet.At the same time StreamShift starts initial load, it starts capturing insert, update, and delete operations in the source database using change data capture (CDC) and stores those events in the integrated Kafka instance. In the event this data consumes 60% of Kafka's available disk space, you will receive an email alert, and Striim operations staff will expand the virtual disks.When initial load is complete, StreamShift starts applying the captured change data to the target database. This ongoing synchronization picks up where initial load stopped, and there should be no missing or duplicate transactions. Synchronization continues until you stop the migration manually.When the migration of existing source data is complete, continuous synchronization from source to target using CDC starts automatically (see Lift and Shift versus Ongoing Synchronization).At this point, for sources other than SQL Server, you may click Apply Constraints to restore the foreign keys.If the source is SQL Server, Apply Constraints is disabled, and constraints will be applied when migration is stopped.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

Migrate the data


Stop migrationSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMigrating a database with StreamShiftStop migrationPrevNextStop migrationWhen you no longer require ongoing synchronization, click Stop Migration. This may take a few minutes. If you did not previously apply constraints, they will be applied.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

Stop migration


Adding users to a StreamShift serviceSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationAdding users to a StreamShift servicePrevNextAdding users to a StreamShift serviceIn your Striim subscription, go to the Users page and click Invite User.Enter the new user's email address, select the appropriate role (see the text of the drop-down for details), and click Save.The new user will receive an email with a signup link. Once they have signed up, their status will change from Pending to Activated. Once the new user is activated, select ... > Edit, add the service(s) you want them to have access to, and click Save.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

Adding users to a StreamShift service


Monitoring a StreamShift serviceSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationMonitoring a StreamShift servicePrevNextMonitoring a StreamShift serviceIn your  subscription, go to the Users page and click ... > Monitoring for the service.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

Monitoring a StreamShift service


StreamShift 1.0.0 release notesSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationStreamShift 1.0.0 release notesPrevNextStreamShift 1.0.0 release notesThe following are limitations in this release:Make sure there is no active change data flowing from the source before stopping synchronization. Otherwise some events might not be applied to the target.MySQL source and target: when doing "Lift and Shift only" migration between two MySQL databases, triggers are migrated automatically to the target database during schema migration. Streamshift drops the triggers before doing the initial data load and recreates them after initial load. Any triggers that refer to tables in a different database will not be recreated properly after initial load.Oracle sources: when migrating XMLType columns from Oracle, exclude the column from the migration during the customization process to avoid errors during the data migration phase.SQL Server source and target: when doing "Lift and Shift only" migration between two SQLServer databases, with the target is SQLServer 2019, Streamshift may wrongly report that the foreign key migration has failed. This can be ignored. Streamshift actually migrates foreign keys in this setup.SQL Server source or target: when both an SSH tunnel and SSL are specified, you may encounter the error Connection Not Made: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Failed to validate the server name in a certificate during Secure Sockets Layer (SSL) initialization."The following are known issues for this release:Oracle sources: StreamShift does not flag schemas or tables with names of more than 30 characters as incompatible (SMS-2233). (Names longer than 30 characters are not supported by LogMiner, the Oracle tool StreamShift uses to capture Oracle CDC.)In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.PrevNext © 2021 Striim, Inc. Publication date:

StreamShift 1.0.0 release notes


Contact StreamShift supportSkip to main contentToggle navigationToggle navigation Getting Started with StreamShiftUnderstanding database migration and replicationLift and Shift versus Ongoing SynchronizationSupported sources and targetsStreamShift workflow overview Prerequisite setup for sources and targetsConnecting with sources and targets over the internetUsing an SSH tunnel to connect to a source or targetCosmos DB setupMySQL / MariaDB setupOracle setupPostgreSQL setupSQL Server setup Migrating a database with StreamShiftSubscribe to StreamShift in the AWS MarketplaceSubscribe to StreamShift in the Microsoft Azure MarketplaceSubscribe to StreamShift in the Google Cloud MarketplaceCreate a StreamShift serviceCreate a StreamShift projectChoose your migration typeSelect and connect to your source databaseConfigure SSLSelect and connect to your target databaseSelect what to migrate Understanding the assessment and compatibility reportsHow the assessment score is calculatedHow the compatibility score is calculatedCustomize the migration and migrate the schemaMigrate the dataStop migrationAdding users to a StreamShift serviceMonitoring a StreamShift serviceStreamShift 1.0.0 release notesContact StreamShift supportStreamShift DocumentationprintToggle navigationStreamShift DocumentationContact StreamShift supportPrevContact StreamShift supportTo contact StreamShift support, email streamshift-support@striim.com.In this section: Search resultsNo results foundWas this helpful?YesNoWould you like to provide feedback? Just click here to suggest edits.Prev © 2021 Striim, Inc. Publication date:

Contact StreamShift support