Getting started steps
SQL Server and Oracle images, containers, clones
Machine learning (ML) datasets on demand
SQL Server specific topics
Azure SQL, AWS RDS, Storage Systems (SANs)
Config settings, Dockerfile
Put the backup files or dumps in a directory on the Windocks server or on a network share. If the backups or dumps are on a network share, provide full permissions for the Windocks machine name to read and write from BOTH the network share AND the directory. For example if your Windocks machine name is PC1, then provide permissions to the account PC1$. In Computer management / Network shares, find the network share on which the backup lives and provide permissions to PC1$. Also in File Explorer, provide full permissions on the highest parent directory to PC1$. Windocks service runs as LOCALSYSTEM, do not change that.
If you will be using transaction log backups to incrementally update the image, then put those in a separate directory with the proper permissions for the Windocks machine account.
If you are working with a storage system (SAN), to do the cloning, you do not need the backups or dumps. The SAN will provide the clones.
Run SQL scripts for masking sensitive data, release (upgrade and rollback), migration, etc. Run scripts either at image build time or at container create time. If the scripts are in a git repo, then running them at container create time applies the latest scripts to the container database clone. By default, scripts in the dockerfile are applied at image build time. To apply them at container create time, put the line ENV USE_DOCKERFILE_TO_CREATE_CONTAINER=1 in the dockerfile and the line RUN somescript.sql after this line. Scripts can be stored and copied into the container in one of the following ways:
Apply masking scripts at image build time for all situations except if you plan to update the image incrementally with transaction log backup files. In the exceptional case, the image must be in the same state at production to receive transaction log backups.
Make sure you have Windocks installed and you have the samples in windocks\samples. Then based on your type of database source, choose the right method below:
All global configurations are in windocks\config\node.conf and documented in that file. Each time you change node.conf, you must restart the Windocks service.Some of the settings in the file include the following:
There are three ways to build the image
There are three ways to create containers and / or clones - command line on the Windocks machine, web application or REST API (see below for details). You may view logs in the web application by clicking Containers and clones on the top menu and Log next to your container / clone.
For SQL Server, the standard and community Windocks editions deliver SQL Server containers with the SQL engine running as a command line. To run linked servers, Distributed transactions, the enterprise Windocks edition is required. The enterprise editions include three additional base images
There are a few processes to automate
The following logs are useful for troubleshooting: