Striim Migration Service for Google Cloud Documentation

Create and test the streaming integration application

The following instructions assume that you used SQL Server and Google Cloud SQL for SQL Server native tools to create the target tables. If you used some other method, see Create and test the initial load application.

Note that the source and target must both be online so the App Wizard can validate the connections.

  1. Go to the SMSGC deployment page, copy the admin password (this randomly generated "temporary" password should be quite secure), click Visit the site, and log in using the username admin and the password from the deployment page.

  2. Use Search Templates to find templates with SQL Server CDC sources.

  3. Click SQL Server CDC to Cloud SQL SQL Server.

  4. Enter a name for your application, such as StreamingIntegrationApp, and click Save.

  5. Enter the following source properties, then click Next::

    • Source Name: a descriptive name for the source, such as SQLServerCDCSource

    • Hostname: the IP address of the SQL Server souerce

    • Port: the port for the SQL Server source

    • Username: the login name for the user created as described in Set up the SQL Server source.

    • Password: the password for that login

    • Wildcard: to migrate all tables from the schema, enter <schema>.%

    • Database name: the name of the database containing the schema

  6. If SMSGC's checks show that all properties are valid (this may take a few minutes), click Next. Otherwise, click Back and correct the properties.

  7. Select the schemas to migrate, then click Next.

  8. Click Next to skip mapping and filtering.

  9. Enter the following target properties, then click Next:

    • SQL Server Connection URL: jdbc:sqlserver:// followed by the public IP address or connection name of the target Cloud SQL instance, a colon, the port number, a slash, and the database name, for example:

      jdbc:sqlserver://198.51.100.0 34.83.131.86:1433/mydb
    • SQL Server Username: the login name for the user created as described in Create a user for SMSGC in the SQL Server target

    • SQL Server Password: the password for that login

    • Tables: pairs of source and target tables separated by commas. This will be automatically set based on the source Tables setting. For example, if the source setting is myschema.%, this will be set to myschema.%,myschema.public.%. If the source setting is myschema.address;myschema.customer, this will be set to myschema.address,myschema.address;myschema.customer,myschema.customer. If the target schema or table names are not the same as those in the source, edit this to match. If you prefer, you may finish creating the application and edit the Tables setting later.

  10. You should see the application in the Flow Designer. Select Created > Deploy App > Deploy.

  11. If any of the tables in the target do not match the tables in the source, or if SMSGC does not recognize a column's data type, SMSGC will display the Table mapping validation dialog. If the entries are all of type INFO, and do not appear to represent an actual incompatibility, click Ignore. Otherwise, you may need to modify the target tables to make them compatible with the source.

  12. Select Deployed > Start App.

  13. Deployed should change to Running. At this point, you may test the streaming integration application by using myql or any other client to add some data to the source, then use Cloud Shell or any other client to verify that it is replicated to the target (this may take up to 60 seconds). When you are through testing, delete the test data from the source and it will automatically be deleted from the target.

  14. Select Running > Stop App, then when the stopping completes select Stopped > Undeploy App.