How to successfully connect SchemaSpy to a MSSQL database. Certificate issues and parameter quirks can make the tool surprisingly stubborn.
⚠️ Note: This config disables security checks — intended for one-off exports only. For regular use, import and trust the SQL Server certificate properly.
sudo mkdir /opt/schemaspy
sudo mkdir /opt/schemaspy/drivers
cd /opt/schemaspy/drivers
sudo wget https://go.microsoft.com/fwlink/?linkid=2338543
cd /opt/schemaspy
sudo nano schemaspy.properties# ---- DB type ----
schemaspy.t=mssql08
# ---- Driver ----
schemaspy.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver
# Change filename if necessary!
schemaspy.dp=/opt/schemaspy/drivers/mssql-jdbc-13.2.1.jre11.jar
# ---- Connection ----
schemaspy.host=192.168.??.??
schemaspy.port=1433
schemaspy.db=mydbname
schemaspy.u=<mymssqlUser>
schemaspy.p=<mymssqlPassword>
# ---- Scope ----
schemaspy.s=dbo
schemaspy.all=true
sudo nano sqlserver.propertiesencrypt=false
trustServerCertificate=true
docker run --rm \
-u $(id -u):$(id -g) \
-v /opt/schemaspy:/opt/schemaspy \
-v /opt/schemaspy/output:/output \
-w /opt/schemaspy \
schemaspy/schemaspy:latest \
-dp /opt/schemaspy/drivers \
-configFile /opt/schemaspy/schemaspy.properties \
-connprops /opt/schemaspy/sqlserver.properties \
-o /output \
-debugH@ppy H@cking