It’s been a long time coming, but now SQL Server Integration Services is in Public Preview on Azure!
I’ve written about it elsewhere in greater depth, but here are the headlines:
- It makes use of SSIS Scale Out, which was released as part of SQL Server 2017.
- Although it is based on SSIS Scale Out, you can’t actually configure SSIS Scale Out to run on the instance. If this confuses you then read my in-depth post.
- SSISDB is installed in either SQL Azure or on a Managed Instance.
- You don’t have to create Integration Services Catalog/SSISDB yourself; it is done for you. So that annoying key management is no longer a problem.
- You don’t have exposure to the worker agents; you define how many you want and the deployment process does the rest.
- The aim was for it to be a “lift and shift” process – that you can take your ispac and deploy it to the Integration Services Catalog and configure the Environments exactly how you have on premise.
- You’ll need to set up a VNET to connect back to your domain (ie out of Azure.)
- Similarly, there is extra set up to connect using domain accounts.
I’ve had a play around with it and am impressed how easy it is to move a project from on premise to Azure, and the familiarity with SSISDB is great. Using SQL as an API has proven to be useful as we are able to make use of the same views, reports and stored procedures installed as part of Integration Services Catalog as we do on premise.
If I haven’t already made it clear – go and read my in-depth post!