Home Applications SQLgateway-migration-MSsql-IRIS

SQLgateway-migration-MSsql-IRIS

InterSystems does not provide technical support for this project. Please contact its developer for the technical assistance.
0
0 reviews
0
Awards
3
Views
0
IPM installs
0
0
Details
Releases (1)
Reviews
Issues
Show connection to MSsqlServer from SQLgateway with JDBC

What's new in this version

Initial Release

SQLgateway-migration-MSsql-IRIS

Sample repository to show how to migrate from MSsqlserver to InterSystems IRIS
using SQLgateway in contrast to using an external tool as DBeaver or CloudBeaver or similar.

Warning

This is just JDBC/Java and IRIS with ISOS and SQL

  • no AI, no Python, no other magic

Credits

Git>Hub package migration-mssql-iris
provided by YURI MARX PEREIRA GOMES
- Special thanks as this was an excellent base to start off.
And the official documentation on SQLgateway

Prerequisites

Make sure you have git and Docker desktop installed.

Installation

Clone/git pull the repo into any local directory

git https://github.com/r-cemper/SQLgateway-migration-mysql-IRIS.git
  1. Build
docker-compose build
  1. Run it in foreground. Sometimes container start is slower than estimated.
docker-compose up
  • Wait for confirmation from your containers container: ready to accept connections
  1. Connection to MSsql:
    • host: container mssql
    • database: msdb
    • port: 1433
    • username: SA
    • password: MSSQLServer@2019
  2. Connection to IRIS:
    • host: localhost
    • namespace: user
    • port: 41773
    • username: _SYSTEM
    • password: SYS
  3. SQLgateway
    is installed during Docker build and the required
    jdbcdriver for Linux is included in this repo

How to test

SMP is available here
http://localhost:42773/csp/sys/UtilHome.csp

All migration actions can be executed directly from SMP.

  1. Verify the gateway connection in
    SMP> Administration> Configuration> Connectivity> SqlGateway_Configuration

    • To test Connection click edit for cnection mysql
    • verify Connection successful
    • Be patient at this point. Some DB containers take quite some time to talk to you.
      wait a little bit, reload the page in browser and try the test again.
    • as you tsl to SQLserver you may access also other available DBs
      by modifying parameter databaseName=anyDB;
      The previously described database AdventureWorks seems not to be available anymore.
  2. Identifying the source tables. In SMP > Change to Namespace USER
    then step to SMP >Explorers >SQL >Wizards > Data Migration

  3. Set required import parameters

  • Destination Namespace
  • Type = TABLE
  • Select a SQL Gateway connection: = mssql ; now the first connection is established and you select
  • Schema = [null schema]
  • Tables to migrate = all
  1. Identify target but you may change the schema to whatever you like
  • don’t forget to click change all
  • we migrate Definitions and Data so both sides are selected
  1. Skipping special settings, we use defaults to start the task in background

  2. Now we check the results and see everything was working without Errors
    You might see errors if tables depend on content not yet migrated.
    And wait for completions until the status shows Done

  3. We terminate the Migration Wizard and return to normal table view filtered by dc*

All 8 tables are visible and show meaningful columns

  1. Selecting a table and clicking on OpenTable shows reasonable contents

  2. A look into the related generated Class Definitions confirms the result and successful completion.

Article on DC

Version
1.0.004 Jul, 2026
Ideas to the app
Category
Technology Example
Works with
InterSystems IRISInterSystems IRIS for Health
First published
04 Jul, 2026
Last edited
04 Jul, 2026