Running or scheduling a SQL Server Integration Services package in SQL Server big data cluster
About this sample
This is a sample SQL Server Integration Services (SSIS) app, which shows how to run a SSIS package as a scheduled service. This sample creates an app that is called each minute that executes an SSIS package. It also shows you how to run the SSIS package on demand. The SSIS package creates a backup of the
DWConfiguration database on the master SQL instance to disk. Also, the package cleans any backup files for the
DWConfiguration database that are older than one hour, making sure that maximum 60 backup files will be on disk at any moment.
Before you begin
To run this sample, you need the following prerequisites.
- SQL Server big data cluster CTP 2.3 or later.
mssqlctl. Refer to installing mssqlctl document on setting up the
mssqlctland connecting to a SQL Server big data cluster.
- Optional: to see the SSIS package itself, install Visual Studio 2017 if you don't have it already. After that download and install SSDT.
- Optional: install SSMS if it is not already installed.
Run this sample
Clone or download this sample on your computer.
Log in to the SQL Server big data cluster using the command below using the IP address of the
endpoint-service-proxyin your cluster. If you are not familiar with
mssqltctlyou can refer to the documentation and then return to this sample.
mssqlctl login -e https://<ip-address-of-endpoint-service-proxy>:30777 -u <user-name> -p <password>
spec.yamlfile with the password for SQL user
Deploy the application by running the following command, specifying the folder where your
back-up-db.dtsxfiles are located:
mssqlctl app create --spec ./SSIS
Check the deployment by running the following command:
mssqlctl app list --name back-up-db --version [version]
Once the app is listed as
Readythe job should run within a minute. You can check if the backup is created by running:
kubectl -n [your namespace] exec -it mssql-master-pool-0 -c mssql-server -- /bin/bash -c "ls /var/opt/mssql/data/*.DWConfigbak"
You should see a backup being created for every run of the job, with a maximum of 60 backups since the SSIS package cleans up backups older than one hour. You can use any of the
.DWConfigbakfiles to restore the database.
You can clean up the sample by running the following commands:
# delete app mssqlctl app delete --name back-up-db --version [version] # delete backup files kubectl -n [your namespace] exec -it mssql-master-pool-0 -c mssql-server -- /bin/bash -c "rm /var/opt/mssql/data/*.DWConfigbak"
Please open to Visual Studio solution to see the SSIS package.
Here is the spec file for this application. This sample uses the
SSIS runtime and does not specify any
outputs. Next to that, the spec file in this example specifies
|options||Specifies any command line parameters passed to the execution of the SSIS package|
|schedule||Specifies when the job should run. This follows cron expressions. A value of '*/1 * * * *' means the job runs every minute. If omitted the package will not run automatically and you can run the package on demand using
name: back-up-db version: v1 runtime: SSIS entrypoint: ./back-up-db.dtsx options: /REP V /CONN "MasterSQL"\;"\"Data Source=service-master-pool;User ID=sa;Initial Catalog=master;Password=[SA_PASSWORD]\"" schedule: "*/1 * * * *"
For more information, see these articles: