SQL Server

Supported Versions

• 2019
• 2017
• 2016
• 2014
• 2012

Driver

SQL Script Syntax

• Standard SQL syntax with statement delimiter GO
• T-SQL

Compatibility

• DDL exported by SQL Server can be used unchanged in a MigrateDB migration.
• Any SQL Server sql script executed by MigrateDB, can be executed by Sqlcmd, SQL Server Management Studio and other SQL Server-compatible tools (after the placeholders have been replaced).

Example

/* Single line comment */
CREATE TABLE Customers (
CustomerId smallint identity(1,1),
Name nvarchar(255),
Priority tinyint
)
CREATE TABLE Sales (
TransactionId smallint identity(1,1),
CustomerId smallint,
[Net Amount] int,
Completed bit
)
GO

/*
Multi-line
comment
*/
-- TSQL
CREATE TRIGGER dbo.Update_Customer_Priority
 ON dbo.Sales
AFTER INSERT, UPDATE, DELETE
AS
WITH CTE AS (
 select CustomerId from inserted
 union
 select CustomerId from deleted
)
UPDATE Customers
SET
 Priority =
   case
     when t.Total < 10000 then 3
     when t.Total between 10000 and 50000 then 2
     when t.Total > 50000 then 1
     when t.Total IS NULL then NULL
   end
FROM Customers c
INNER JOIN CTE ON CTE.CustomerId = c.CustomerId
LEFT JOIN (
 select
   Sales.CustomerId,
   SUM([Net Amount]) Total
 from Sales
 inner join CTE on CTE.CustomerId = Sales.CustomerId
 where
   Completed = 1
 group by Sales.CustomerId
) t ON t.CustomerId = c.CustomerId
GO

-- Placeholder
INSERT INTO ${tableName} (Name, Priority) VALUES ('Mr. T', 1);

Authentication

SQL Server supports several methods of authentication. These include:

• SQL Server Authentication
• Windows Authentication
• Azure Active Directory
• Kerberos

SQL Server Authentication works ‘out-of-the-box’ with MigrateDB, whereas the others require extra manual setup.

The instructions provided here are adapted from the Microsoft JDBC Driver for SQL Server documentation . Refer to this when troubleshooting authentication problems.

Note: These instructions may be incomplete. MigrateDB depends on Microsoft’s JDBC drivers, which in turn have many environmental dependencies to enable different authentication types. You may have to perform your own research to get the JDBC driver working for the different authentication types.

SQL Server Authentication

This uses a straightforward username and password to authenticate. Provide these with the user and password configuration options.

Windows Authentication

Windows Authentication, also known as Integrated Security , is enabled by amending your JDBC connection string to set integratedSecurity=true.

Example: jdbc:sqlserver://<i>host</i>:<i>port</i>;databaseName=<i>database</i>;integratedSecurity=true.

Azure Active Directory

Installing MSAL4J

You must add Microsoft’s MSAL4J library to your classpath. For instance, as a Maven or Gradle dependency.

For command-line users, MSAL4J is already included, so no extra installation is required.

Connecting

There are several types of Azure Active Directory authentication:

• Azure Active Directory with MFA
• Azure Active Directory Integrated
• Azure Active Directory MSI
• Azure Active Directory with Password
• Azure Active Directory Service Principal
• Access Tokens

To use the various authentication types, amend your JDBC URL to set the authentication parameter:

• For Active Directory Integrated set authentication=ActiveDirectoryIntegrated
  • e.g: jdbc:sqlserver://host:port;databaseName=database ;authentication=ActiveDirectoryIntegrated
• For Active Directory MSI set authentication=ActiveDirectoryMSI
  • e.g: jdbc:sqlserver://host:port;databaseName=database ;authentication=ActiveDirectoryMSI
• For Active Directory With Password set authentication=ActiveDirectoryPassword
  • e.g: jdbc:sqlserver://host:port;databaseName=database ;authentication=ActiveDirectoryPassword
  • You must also supply a username and password with MigrateDB’s user and password configuration options
• For Active Directory Interactive set authentication=ActiveDirectoryInteractive
  • e.g: jdbc:sqlserver://host:port;databaseName=database ;authentication=ActiveDirectoryInteractive
  • This will begin an interactive process which expects user input (e.g. a dialogue box), so it’s not recommended in automated environments
• For Active Directory Service Principal set authentication=ActiveDirectoryServicePrincipal
  • e.g: jdbc:sqlserver://host:port;databaseName=database ;authentication=ActiveDirectoryServicePrincipal

The Microsoft documentation has more details about how these work with JDBC URLs .

Connecting to a Named Instance

When connecting to a named instance, the JDBC URL must be of the form:

jdbc:sqlserver://<server_name>;instanceName=<instance_name>;databaseName=<database_name>

For example:

jdbc:sqlserver://test_server;instanceName=test_instance;databaseName=test_database

Note: If a named instance is used along with the <host>:<port> syntax in the JDBC URL, the driver will connect to the port over the named instance.

Limitations

• MigrateDB’s automatic detection for whether SQL statements are valid in transactions does not apply to CREATE/ALTER/DROP statements acting on memory-optimized tables (that is, those created with WITH (MEMORY_OPTIMIZED = ON)). You will need to override the executeInTransaction setting to be false, either on a per-script basis or globally.
• SQL Server is unable to change the default schema for a session. Therefore, setting the migratedb.defaultSchema property has no value, unless used for a Placeholder in your sql scripts. If you decide to use migratedb.defaultSchema, it also must exist in migratedb.schemas.
• By default, the migratedb schema history table will try to write to the default schema for the database connection. You may specify which schema to write this table to by setting migratedb.schemas=custom_schema, as the first entry will become the default schema if migratedb.defaultSchema itself is not set.
• With these limitations in mind, please refer to the properties or options mentioned here for descriptions/consequences.
• If using the JTDS driver, then setting ANSI_NULLS or QUOTED_IDENTIFIER in a script will cause an error. This is a driver limitation, and can be solved by using the Microsoft driver instead.

Azure Synapse ➡️