Scheduling a SQL Server Integration Services package in SQL Server big data cluster
Contents
About this sample
Before you begin
Run this sample
Sample details
Related links
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. 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.
Refer to installing mssqlctl document on setting up the mssqlctl and connecting to a Aris cluster.
Before you begin
To run this sample, you need the following prerequisites.
Software prerequisites:
1.SQL Server big data cluster CTP 2.3 or later. 2. Optional: to see the SSIS package itself, install Visual Studio 2017 if you don't have it already. After that download and install SSDT. 3. 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 withmssqltctlyou 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> -
Replace
[SA_PASSWORD]in thespec.yamlfile with the password for SQL usersa. -
Deploy the application by running the following command, specifying the folder where your
spec.yamlandback-up-db.dtsxfiles are located:mssqlctl app create --spec ./SSIS -
Test the deployment by running the following command:
mssqlctl app listOnce 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 v1 # 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"
Sample details
What is in the spec.yaml file
Apart from regular settings, the spec.yaml file in this example specifies options and schedule:
| Setting | Description |
|---|---|
| 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. |
Related Links
For more information, see these articles:
How to deploy and app on SQL Server 2019 big data cluster (preview)