Windocks delivers containers with all SSIS, SSAS, SSRS, Agent and engine.docker run -d mssqlall-2019
There are several options for which service accounts are used to run the various SQL Server services. Open the file windocks\config\node.conf to set this. After changes to node.conf, you MUST restart the Windocks service.
If these service specific logins and user names are specified then Windocks will use these. Uncomment these lines and put in the login and encrypted password. If there is no password for the account such as for gSMA then leave the comment # as is
If you do not want to specify individual accounts as above, then add or uncomment the line:
# GENERATE_LOCAL_ACCOUNTS_WITH_PASSWORD="Encrypted password here"
This will generate machine accounts to run the services, a different account for each service.
If you do not want to specify generated machine accounts with passwords as above, then add or uncomment the line:
This will generate service accounts for the services
The standard and community Windocks editions deliver SQL Server containers with the SQL engine running as a command line. To run SSIS, SSRS, SSAS, Agent and also to support linked servers or distributed transactions, the enterprise Windocks edition is required. The enterprise editions include three additional base images
Integration services (SSIS) are delivered running with the container SQL Server engine. Unlike the other services, SSIS cannot be connected to with a port since the standard SSIS installation is one per machine. Windocks allows multiple SSIS instances of the same version to run on the same machine and you can connect to them by making a separate REST API call specifying which SSIS port you want to connect to. Instructions are below and you will also need to see the sample in windocks\samples\ssis
# These are the curl commands to make the calls to Windocks to specify which SSIS container (port) is the active one
# You will need the json as well in windocks\samples\ssis
# Create a token such as ssistest191 below and encrypt it using windocks\bin\encrypt.exe
# Put the encrypted token in windocks\config\node.conf as follows:
SSIS_ENCRYPTED_TOKEN="Put encrypted token here"
Also uncomment or add the line in node.conf
Restart the Windocks service
# Use this curl call to specify which SSIS container will receive SSIS connections to the host machine
# This call will lock all SSIS usage from any other client, so be sure to call the letgo curl after you are done with
# making the connection and doing your work on the SSIS container
curl -H "Content-Type: application/json" -email@example.com -X POST http://localhost:3000/windocksdashboard?token=ssistest191
# Use this curl call to let go of the lock on SSIS usage
curl -H "Content-Type: application/json" -firstname.lastname@example.org -X POST http://localhost:3000/windocksdashboard?token=ssistest191
SSAS in the container is like any SSAS instance and you can connect to the container SSAS in Management Studio by specifying the SSAS port in the container. This port is available as part of the return string when you create the container.
SSAS is pre-configured to run against the container SQL engine. The config and logs are as in any SQL Server install and are available in windocks\container\