Think of docker as a tool that creates software installers, similar to .msi files.  This “installer” includes both an operating system and a copy of your application.  The operating system within the “installer” is a minimally viable OS, containing only the essential components needed to run your application.

Kubernetes takes the "installer" (known as a Docker image) and can install it to a server.  It can also install the docker image multiple times on a single server or multiple times across multiple servers.  You don't need to worry about the specifics of hard drive space, RAM, or CPU requirements—Kubernetes manages all of this for you.

Hope this clears up the confusion.

Yes.  All you need to do is issue 8 command line commands.

After you install the software(no registration required) and setup the data governance tables , here are the commands you need to issue to set up the database.  These examples run from windows command line.  They need to be modified slightly to run on linux.

If you have any questions or issues please contact us or setup a no cost one on one zoom meeting.  

Let me guess, you've tried docker prune, optimize-vhd or disk part  but that didn't work.  You've read tons of blog posts and watched a bunch of YouTube video's but to no avail.  It seems to be a big mystery as to why docker doesn't release all of the hard drive space that it uses.

There is a reason for this.  Docker uses up a lot of RAM.  It uses far more RAM than you have available.  And will do this for long periods of time.  When this happens your C:\Windows\Temp folder gets full.  So what you must do is periodically empty your temp folder and that will give you back all the space it used.

Hope this helps and reduces someone's frustration.

According to chat gpt a dry run :

"Refers to a rehearsal or practice session conducted in a simulated or controlled environment to test the execution of a process, system, or event without actually implementing it in its full operational capacity. It involves going through the motions and steps of a particular activity, such as a presentation, procedure, or software implementation, to identify potential issues, assess readiness, and familiarize participants with the expected workflow. Dry runs are typically employed to uncover and rectify any flaws, ambiguities, or inefficiencies before the actual implementation or live performance takes place, allowing for adjustments and improvements to be made, thereby enhancing the overall outcome and reducing the likelihood of errors or disruptions."

To verify if your SQL scripts will execute and that those SQL scripts are doing what you think they will do.

SQL Simulator makes performing dry runs easy with just the click of a button.

The setup process can take as little as 5 minutes.  Here is what you need

1. Download the software
2. Unzip the software(There is no installer)
3. Create a blank/empty schema in a non production database
4. Configure data sources

A "hello world" tutorial can be found by clicking here

It is similar in concept to Redgate SQL Clone or Windocs.  If you are not familiar with these tools they make clones of your database.  The key difference with SQL Simulator is, it only makes a clone of the database objects affected by your sql script not the entire database.  Nor does it copy the entire table (if your sql has  where clauses).  Once those database objects have been cloned, SQL Simulator then executes your script against the cloned database it created.

For a more in-depth technical overview click here

Here you go