Sign inSign up

advantys/workflowgen-sql

By advantys

•Updated 7 days ago

Pre-configured SQL Server for WorkflowGen. v10 & v9 Linux production-ready. Windows dev/test only.

Image
0

10K+

advantys/workflowgen-sql repository overview

⁠WorkflowGen SQL Server Database Docker Image

Pre-configured Microsoft SQL Server for supported WorkflowGen versions.

⁠Platform Support & Production Readiness

PlatformSQL Server EditionProduction StatusUse Case
v10 LinuxSQL Server 2025✅ Production-ReadyProduction and development
v10 Windows (ltsc2019/ltsc2022)SQL Server 2025 Express⚠️ Development/Testing OnlyDevelopment and testing only
v9.3.1+ LinuxSQL Server 2022✅ Production-ReadyProduction and development
v9.3.0 and earlier LinuxSQL Server 2019✅ Production-ReadyProduction and development
v8 LinuxSQL Server 2019✅ Production-ReadyProduction and development
v9 Windows (ltsc2019/ltsc2022)SQL Server Express 2017⚠️ Development/Testing OnlyDevelopment and testing only
v8 Windows (ltsc2019)SQL Server Express 2017⚠️ Development/Testing OnlyDevelopment and testing only

⁠⚠️ Version Matching is Critical

Use a database image version that matches your WorkflowGen application version.

⁠Version Compatibility Matrix
WorkflowGen VersionRecommended Database Tag (Linux)Windows TagStatus
10.5.010.5.0-ubuntu-24.0410.5.0-express-win-ltsc2019 or 10.5.0-express-win-ltsc2022✅ Production (Linux)
9.3.1+9.7.0-ubuntu-22.049.7.0-express-win-ltsc2019 or 9.7.0-express-win-ltsc2022✅ Production (Linux)
9.3.0 and earlier{version}-ubuntu-18.04{version}-express-win-ltsc2019✅ Supported
8.x{version}-ubuntu-18.04{version}-express-win-ltsc2019✅ Supported

⚠️ WorkflowGen v7.x is unsupported. Legacy images remain available; upgrade to a supported version.


⁠Requirements

  • Docker Engine on any Linux distribution
  • Minimum 2GB RAM (4GB+ recommended for production)
  • Docker for Windows or Docker Desktop (with Linux containers mode)
  • Docker for Mac
⁠Windows Containers
  • On Windows 10 Pro or Enterprise, install Hyper-V and Docker Desktop⁠, switch to Windows containers, and use an ltsc2019 image. Windows 10 does not support Windows Server 2022 container images.
  • Use Windows 11 or Windows Server 2022 or later for ltsc2022 images. Consult Microsoft's Windows container version compatibility⁠ matrix when the host and container versions differ.
  • On Windows Server, use the image tag matching the host version for process isolation. A newer compatible host can run an older image with Hyper-V isolation.
  • Minimum 4GB RAM recommended for v10 (SQL Server 2025)

⁠Quick Start

⁠v10 Linux (SQL Server 2025)
docker volume create wfgen-sql-data
docker run -d --name wfgen-sql --env-file ./database.env \
  -v wfgen-sql-data:/var/opt/mssql -p 1433:1433 \
  advantys/workflowgen-sql:10.5.0-ubuntu-24.04
⁠v10 Windows (SQL Server 2025 Express - Dev/Test Only)

⚠️ NOT FOR PRODUCTION - Express Edition limits: 50GB database, the lesser of 1 socket or 4 cores, 1.4GB RAM. Use Linux image for production.

Choose the tag that matches the Windows container host: ltsc2022 for Windows Server 2022 or ltsc2019 for Windows Server 2019.

docker volume create wfgen-sql-data
docker run -d --name wfgen-sql --env-file .\database.env `
  -v wfgen-sql-data:C:\wfgen\sql -p 1433:1433 `
  advantys/workflowgen-sql:10.5.0-express-win-ltsc2022

For Windows Server 2019, use advantys/workflowgen-sql:10.5.0-express-win-ltsc2019.

⁠v9 Linux (SQL Server 2022 - Production-Ready)
docker volume create wfgen-sql-data
docker run -d --name wfgen-sql --env-file ./database.env \
  -v wfgen-sql-data:/var/opt/mssql -p 1433:1433 \
  advantys/workflowgen-sql:9.7.0-ubuntu-22.04

Other versions: 9.2.11-ubuntu-18.04 (v9 SQL 2019), 8.3.5-ubuntu-18.04 (v8 SQL 2019)

⁠v8, v9 Windows (Development/Testing - SQL Server Express 2017)
# Create volume for database persistence
docker volume create wfgen-sql-data

# Run container (examples: 9.7.0 or 8.3.5)
docker run -d `
  --name wfgen-sql `
  --env-file .\database.env `
  -v wfgen-sql-data:C:\wfgen\sql `
  -p 1433:1433 `
  advantys/workflowgen-sql:9.7.0-express-win-ltsc2019
  
# Or, for Windows Server 2022:
# advantys/workflowgen-sql:9.7.0-express-win-ltsc2022
  
# Or for v8:
# advantys/workflowgen-sql:8.3.5-express-win-ltsc2019

⁠Configuration

⁠Required Environment Variables

Required for all images:

VariableDescriptionRequired
ACCEPT_EULAAccept SQL Server EULA⁠ (Y or N)✅ Yes (Linux only)
SA_PASSWORDSQL Server SA account password (see password requirements⁠)✅ Yes
WFGEN_DATABASE_USER_PASSWORDWorkflowGen database user password✅ Yes
MSSQL_PIDSQL Server edition (see edition table⁠)⚠️ Recommended for v10 Linux

Notes:

  • ACCEPT_EULA is required for Linux images only (Microsoft requirement). Windows images have SQL Server pre-installed.
  • SA_PASSWORD is required for both Linux and Windows images.
  • MSSQL_SA_PASSWORD is also supported as an alias for SA_PASSWORD.
⁠Optional Environment Variables
VariableDescriptionDefault
WFGEN_DATABASE_NAMEWorkflowGen database nameWFGEN
WFGEN_DATABASE_CONTAINMENTEnable contained database users (Y or N)Y
WFGEN_DATABASE_USER_USERNAMEWorkflowGen database user usernameWFGEN_USER
WFGEN_DATABASE_FILE_PATHPath to database files inside containerWindows: C:\wfgen\sql
Linux: /var/opt/mssql
WFGEN_ADMIN_USERNAMEWorkflowGen admin usernamewfgen_admin
WFGEN_ADMIN_PASSWORDWorkflowGen admin password(none)
WFGEN_AUTH_APPLICATIONUse WorkflowGen applicative auth (Y or N)Y
⁠SQL Server Edition Selection

For v10 Linux only - Choose your SQL Server edition based on your use case:

EditionValueUse CaseCostProduction
DeveloperDeveloperDevelopment & TestingFREE❌ Not licensed
ExpressExpressProductionFREE✅ Yes
EnterpriseEnterpriseProductionRequires license✅ Yes

Important Notes:

  • Default: If MSSQL_PID is not specified, SQL Server defaults to Developer edition (Microsoft default⁠)
  • Developer Edition: FREE for dev/test, but NOT licensed for production use
  • For production, specify Express (free) or Enterprise (requires license)
  • For development/testing, Developer is recommended (it's the default)
  • Windows containers have the edition fixed at build time (Express Edition)

Example for Linux v10:

# database.env for Linux
SA_PASSWORD=yourStrong(!)Password
WFGEN_DATABASE_USER_PASSWORD=myStrong(?)Password
ACCEPT_EULA=Y
# Free for production use
MSSQL_PID=Express

⁠Connection Strings

⁠For WorkflowGen Application

Use these connection strings in your WorkflowGen container (works on both Linux and Windows):

Recommended (WFGEN_USER account):

WFGEN_DATABASE_CONNECTION_STRING=Data Source=wfgen-sql;Initial Catalog=WFGEN;User ID=WFGEN_USER;Password=<your-password>;TrustServerCertificate=True

Using SA account (not recommended for production):

WFGEN_DATABASE_CONNECTION_STRING=Data Source=wfgen-sql;Initial Catalog=WFGEN;User ID=sa;Password=<SA-password>;TrustServerCertificate=True

Note: TrustServerCertificate=True is required for SQL Server 2025 (both Linux and Windows) due to enforced SSL encryption with self-signed certificates.

⁠For External Database Tools

To connect with SQL Server Management Studio, Azure Data Studio, or other tools:

  • Server: localhost,1433 or 127.0.0.1,1433
  • Authentication: SQL Server Authentication
  • Username: sa (or WFGEN_USER)
  • Password: (your SA_PASSWORD or WFGEN_DATABASE_USER_PASSWORD value)
  • Database: WFGEN

⁠Secrets Management

Protect production credentials with Docker Secrets or Kubernetes Secrets.

⁠Docker Secrets Example (Linux)
# Create secrets
echo "yourStrong(!)Password" | docker secret create SA_PASSWORD -
echo "myStrong(?)Password" | docker secret create WFGEN_DATABASE_USER_PASSWORD -

# Create service with secrets
docker service create \
  --name wfgen-sql \
  --secret SA_PASSWORD \
  --secret WFGEN_DATABASE_USER_PASSWORD \
  -e SA_PASSWORD_FILE=/run/secrets/SA_PASSWORD \
  -e WFGEN_DATABASE_USER_PASSWORD_FILE=/run/secrets/WFGEN_DATABASE_USER_PASSWORD \
  -e ACCEPT_EULA=Y \
  advantys/workflowgen-sql:9.7.0-ubuntu-22.04
⁠Docker Secrets Example (Windows - v8, v9)
# Create secrets
"yourStrong(!)Password" | docker secret create SA_PASSWORD -
"myStrong(?)Password" | docker secret create WFGEN_DATABASE_USER_PASSWORD -

# Create service with secrets
docker service create `
  --name wfgen-sql `
  --secret SA_PASSWORD `
  --secret WFGEN_DATABASE_USER_PASSWORD `
  -e SA_PASSWORD_FILE=C:\ProgramData\Docker\secrets\SA_PASSWORD `
  -e WFGEN_DATABASE_USER_PASSWORD_FILE=C:\ProgramData\Docker\secrets\WFGEN_DATABASE_USER_PASSWORD `
  -e ACCEPT_EULA=Y `
  advantys/workflowgen-sql:9.7.0-express-win-ltsc2019

Important: Environment variables ending with _FILE and their non-_FILE counterparts are mutually exclusive. If both are defined, the container will fail to start.


⁠Environment File Example

Create database.env:

# Required
SA_PASSWORD=yourStrong(!)Password
WFGEN_DATABASE_USER_PASSWORD=myStrong(?)Password

# Required for Linux only
ACCEPT_EULA=Y

# Recommended for v10 Linux (specify SQL Server edition)
MSSQL_PID=Developer

# Optional
WFGEN_DATABASE_CONTAINMENT=Y
WFGEN_DATABASE_USER_USERNAME=WFGEN_USER
WFGEN_ADMIN_USERNAME=wfgen_admin
WFGEN_ADMIN_PASSWORD=admin123
WFGEN_AUTH_APPLICATION=Y

Then use it with --env-file:

# v10 Linux
docker run -d --env-file ./database.env advantys/workflowgen-sql:10.5.0-ubuntu-24.04

# v9 Linux
docker run -d --env-file ./database.env advantys/workflowgen-sql:9.7.0-ubuntu-22.04

# v8/v9 Windows
docker run -d --env-file .\database.env advantys/workflowgen-sql:9.7.0-express-win-ltsc2019

⁠Data Persistence

⁠Linux Container Volumes
Container PathDescription
/var/opt/mssqlSQL Server data directory (includes all databases)

Example:

# Using named volume (recommended)
docker volume create wfgen-sql-data
docker run -d -v wfgen-sql-data:/var/opt/mssql advantys/workflowgen-sql:10.5.0-ubuntu-24.04

# Using bind mount
docker run -d -v /host/path/to/mssql:/var/opt/mssql advantys/workflowgen-sql:9.7.0-ubuntu-22.04
⁠Windows Container Volumes (v8, v9, v10)
Container PathDescription
C:\wfgen\sqlWorkflowGen database files (WFGEN.mdf and WFGEN_Log.ldf)

Example:

# Using named volume (recommended)
docker volume create wfgen-sql-data

# v10 (SQL Server 2025)
docker run -d -v wfgen-sql-data:C:\wfgen\sql advantys/workflowgen-sql:10.5.0-express-win-ltsc2022

# v9 (SQL Server 2017/2022)
docker run -d -v wfgen-sql-data:C:\wfgen\sql advantys/workflowgen-sql:9.7.0-express-win-ltsc2019

# Using bind mount
docker run -d -v C:\host\path:C:\wfgen\sql advantys/workflowgen-sql:9.7.0-express-win-ltsc2019

⚠️ Important: Always map volumes to persist your data. Without volume mapping, all data will be lost when the container is removed.


⁠Accessing the Container

⁠PowerShell Access
⁠Linux Container
# Interactive PowerShell session
docker exec -it wfgen-sql pwsh

# Execute single command
docker exec wfgen-sql pwsh -Command "Get-Date"
⁠Windows Container (v8, v9, v10)
# Interactive PowerShell session
docker exec -it wfgen-sql powershell

# Execute single command
docker exec wfgen-sql powershell -Command "Get-Date"
⁠Bash Access (Linux Only)
# Interactive bash session
docker exec -it wfgen-sql bash

# Execute single command
docker exec wfgen-sql bash -c "ls -la /var/opt/mssql"

⁠Accessing SQL Server with External Tools

⁠Expose Port 1433

The Quick Start⁠ commands publish port 1433. See connection settings⁠ above.

Note: If SQL Server is already running on the host on port 1433, map to a different port:

docker run -d -p 1434:1433 ... advantys/workflowgen-sql:10.5.0-ubuntu-24.04

Then connect to localhost,1434


⁠Container Lifecycle

⁠Starting and Stopping
# Stop container (preserves data if volumes are mapped)
docker stop wfgen-sql

# Start existing container
docker start wfgen-sql

# Restart container
docker restart wfgen-sql

# Remove container (data persists in volumes)
docker rm wfgen-sql
⁠Viewing Logs
# View container logs
docker logs wfgen-sql

# Follow logs in real-time
docker logs -f wfgen-sql

# View last 100 lines
docker logs --tail 100 wfgen-sql
⁠Health Check
# Check container status
docker ps --filter name=wfgen-sql

Open a container SQL session from your host:

# Linux container
docker exec -it wfgen-sql pwsh -NoLogo -NoProfile
# Windows container
docker exec -it wfgen-sql powershell -NoLogo -NoProfile

Set up inside the session: Linux uses startup password aliases/_FILE secrets; Windows uses container-account Express access. Trust is local to these diagnostics.

$sqlParams = @{ ServerInstance = 'localhost'; TrustServerCertificate = $true }
if ($PSVersionTable.PSVersion.Major -le 5 -or $IsWindows) {
    $sqlParams.ServerInstance = '.\SQLEXPRESS'
} else {
    Import-Module /usr/local/lib/Utils.psm1 -Function Get-EnvVar -Prefix WFG
    $sqlParams.Username = 'sa'
    $sqlParams.Password = Get-WFGEnvVar 'MSSQL_SA_PASSWORD' -TryFile -DefaultValue (Get-WFGEnvVar 'SA_PASSWORD' -TryFile)
    if (-not $sqlParams.Password) { throw 'Set the SQL password or its _FILE secret first.' }
}
# Verify database is accessible
Invoke-Sqlcmd -Query 'SELECT DB_NAME()' -Database WFGEN @sqlParams

# Verify WorkflowGen tables exist (should return 64 tables)
Invoke-Sqlcmd -Query "SELECT COUNT(*) AS TableCount FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA = 'dbo'" -Database WFGEN @sqlParams

# Check admin user
Invoke-Sqlcmd -Query 'SELECT TOP 1 USERNAME FROM USERS WHERE ID_USER = 1' -Database WFGEN @sqlParams

Run docker on the host after exit. Repeat setup in each new session.


⁠Database Backup & Restore

⁠Backup

In the container SQL session⁠, generate a unique backup filename. Windows uses an unmounted directory for host copies:

$backupDirectory = if ($PSVersionTable.PSVersion.Major -le 5 -or $IsWindows) { 'C:\wfgen\backup' } else { '/var/opt/mssql/backup' }
New-Item -ItemType Directory -Path $backupDirectory -Force | Out-Null
$backupName = 'WFGEN_' + [guid]::NewGuid().ToString('N') + '.bak'
$backupPath = Join-Path $backupDirectory $backupName
$backupQuery = "BACKUP DATABASE [WFGEN] TO DISK = N'$backupPath'"
if ($backupDirectory -eq '/var/opt/mssql/backup') {
    $backupQuery += " WITH NOFORMAT, NOINIT, NAME = 'WFGEN-full', SKIP, NOREWIND, NOUNLOAD, STATS = 10"
}
Invoke-Sqlcmd -Query $backupQuery @sqlParams
$backupName
exit

On the host, set backupName to the complete filename printed above:

Windows copies require maintenance downtime: stop applications and automatic container restarts/replacements first. Stop the database container around each copy for Hyper-V compatibility; restart it only if the copy succeeds.

# Linux container
backupName='WFGEN_<id>.bak'
docker cp "wfgen-sql:/var/opt/mssql/backup/$backupName" "./$backupName"
# Windows container
$backupName = 'WFGEN_<id>.bak'
docker stop wfgen-sql
if ($LASTEXITCODE -ne 0) { throw 'Container stop failed.' }
docker cp "wfgen-sql:C:\wfgen\backup\$backupName" ".\$backupName"
if ($LASTEXITCODE -ne 0) { throw 'Copy failed; keep the container stopped.' }
docker start wfgen-sql
if ($LASTEXITCODE -ne 0) { throw 'Container start failed.' }

After verifying the host copy and database/container readiness, resume applications and restart policies. Keep the host backup; delete its container copy if unneeded:

# Linux host
docker exec wfgen-sql rm -- "/var/opt/mssql/backup/$backupName"
# Windows host
docker exec wfgen-sql powershell -NoProfile -Command "Remove-Item -LiteralPath 'C:\wfgen\backup\$backupName'"
⁠Restore

Stop applications and automatic restarts/replacements for maintenance. On the host, set backupName to the selected filename, then copy:

# Linux container: prepare the directory, then copy from your host
docker exec wfgen-sql pwsh -NoLogo -NoProfile -Command "New-Item -ItemType Directory -Path /var/opt/mssql/backup -Force | Out-Null"
docker cp "./$backupName" "wfgen-sql:/var/opt/mssql/backup/$backupName"
docker exec -u 0 wfgen-sql chown mssql "/var/opt/mssql/backup/$backupName"
docker exec -u 0 wfgen-sql chmod u+r "/var/opt/mssql/backup/$backupName"
# Windows container: prepare the directory, then copy
docker exec wfgen-sql powershell -NoProfile -Command "New-Item -ItemType Directory C:\wfgen\backup -Force | Out-Null"
if ($LASTEXITCODE -ne 0) { throw 'Backup directory creation failed.' }
docker stop wfgen-sql
if ($LASTEXITCODE -ne 0) { throw 'Container stop failed.' }
docker cp ".\$backupName" "wfgen-sql:C:\wfgen\backup\$backupName"
if ($LASTEXITCODE -ne 0) { throw 'Copy failed; keep the container stopped.' }
docker start wfgen-sql
if ($LASTEXITCODE -ne 0) { throw 'Container start failed.' }

Wait for database/container readiness; keep applications and automatic restarts stopped. Repeat setup in a new container SQL session, then run the block. Health checks fail while WFGEN is offline; errors stop later commands.

$backupName = 'WFGEN_<id>.bak' # Use the same complete filename.
$backupDirectory = if ($PSVersionTable.PSVersion.Major -le 5 -or $IsWindows) { 'C:\wfgen\backup' } else { '/var/opt/mssql/backup' }
$backupPath = Join-Path $backupDirectory $backupName
& {
    Invoke-Sqlcmd -Database master -Query 'ALTER DATABASE [WFGEN] SET OFFLINE WITH ROLLBACK IMMEDIATE' -ErrorAction Stop @sqlParams
    Invoke-Sqlcmd -Database master -Query "RESTORE DATABASE [WFGEN] FROM DISK = N'$backupPath' WITH FILE = 1, RECOVERY, NOUNLOAD, REPLACE, STATS = 5" -ErrorAction Stop @sqlParams
    Invoke-Sqlcmd -Database master -Query 'ALTER DATABASE [WFGEN] SET MULTI_USER WITH ROLLBACK IMMEDIATE' -ErrorAction Stop @sqlParams
}
exit

On failure, keep applications stopped and diagnose/retry; do not blindly bring the database online. After success, verify WFGEN and container health before resuming applications/restart policies. Keep the host backup; delete the restored container copy using the cleanup commands above when no longer needed.


⁠Image Tags

⁠Tagging Convention
  • Linux: {version}-ubuntu-{ubuntu_version}
    • v10: ubuntu-24.04 (e.g., 10.5.0-ubuntu-24.04)
    • v9.3.1+: ubuntu-22.04 (e.g., 9.7.0-ubuntu-22.04)
    • v9.3.0 and earlier: ubuntu-18.04 (e.g., 9.2.11-ubuntu-18.04, 8.3.5-ubuntu-18.04)
  • Windows: {version}-express-win-ltsc2019 or {version}-express-win-ltsc2022 where available
    • v10: Uses Express Edition (for example, 10.5.0-express-win-ltsc2022 or 10.5.0-express-win-ltsc2019)
    • v8, v9: Uses Express Edition (e.g., 9.7.0-express-win-ltsc2019, 9.7.0-express-win-ltsc2022, 8.3.5-express-win-ltsc2019)
⁠Available Tags

Current v10 and v9 examples are in the version compatibility matrix⁠.

Earlier examples follow the tag conventions above: versions 9.2.11, 9.1.1, 9.0.7, 8.3.5, 8.2.4, 8.1.3 and 8.0.12 use Linux ubuntu-18.04 or Windows express-win-ltsc2019.

Default Tag:

  • latest follows the latest published v10 Linux image (SQL Server 2025).

Recommendation: Always use specific version tags (e.g., 10.5.0-ubuntu-24.04, 9.7.0-ubuntu-22.04) for reproducibility.

Browse all image tags⁠.


⁠SQL Server 2025 Information (v10 only)

SQL Server 2025 provides native vector data and configured Full-Text Search for v10.

⁠Editions Used
PlatformEditionLicensingNotes
LinuxDeveloper (default)FREE for dev/testConfigurable via MSSQL_PID env var
LinuxExpressFREE for productionSet MSSQL_PID=Express
LinuxEnterpriseRequires licenseSet MSSQL_PID=Enterprise
WindowsExpressFREEFixed in image, cannot be changed

Note:

  • Linux images are production-ready with SQL Server 2025. Use MSSQL_PID=Express (free) or MSSQL_PID=Enterprise (requires license) for production.
  • Windows images use Express Edition (50GB database, the lesser of 1 socket or 4 cores, 1.4GB RAM) for development/testing only.
  • PostgreSQL⁠ is also supported for v10 production.

Managed databases such as Azure SQL Database or Amazon RDS are also production options.


⁠Password Requirements

SQL Server enforces password complexity requirements:

  • At least 8 characters
  • Contains characters from three of the following categories:
    • Uppercase letters (A-Z)
    • Lowercase letters (a-z)
    • Numbers (0-9)
    • Special characters (!@#$%^&*()_+-=[]{}|;:,.<>?)

Example strong passwords:

  • yourStrong(!)Password
  • MyP@ssw0rd2024
  • Secure#Pass123

⁠Troubleshooting

⁠Container Exits Immediately

Check logs:

docker logs wfgen-sql

Common causes:

  • ACCEPT_EULA not set to Y
  • SA_PASSWORD doesn't meet complexity requirements
  • Insufficient memory (minimum 2GB required, 4GB+ recommended)
  • Port 1433 already in use on host
⁠Cannot Connect to SQL Server

Verify container is running:

docker ps --filter name=wfgen-sql

Check if port is exposed:

docker port wfgen-sql

Test inside the configured container SQL session⁠:

Invoke-Sqlcmd -Query 'SELECT @@VERSION' @sqlParams

Common issues:

  • Firewall blocking port 1433
  • Wrong password or username
  • SQL Server still initializing (wait 30-60 seconds)
  • TrustServerCertificate=True missing from connection string
⁠Database Not Initialized

Wait for initialization message:

docker logs -f wfgen-sql

Look for: Workflowgen database is ready.

Initialization typically takes 30-90 seconds on first start depending on system performance.

Verify inside the configured container SQL session⁠:

# Should return 64 tables
Invoke-Sqlcmd -Query "SELECT COUNT(*) FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA = 'dbo'" -Database WFGEN @sqlParams
⁠Performance Issues (Windows - v8, v9)

The Windows image uses SQL Server Express 2017 which has limitations:

  • Max 1410 MB memory
  • Single socket/4 cores max
  • 10 GB database size limit

Solution: Migrate to the Linux image for better performance and no limitations.


⁠Support and Documentation


⁠License

By using this image, you agree to the:

For SQL Server licensing information, visit Microsoft SQL Server Licensing⁠.

Tag summary

Content type

Image

Digest

sha256:f3e912953…

Size

1.7 GB

Last updated

7 days ago

docker pull advantys/workflowgen-sql