Import from SQL Server¶
Use SQL Server when the data already lives in a Microsoft SQL Server spatial database.
You need to be signed in. Saving the connection once is the usual path.
SQL Server appears only when GeoJibe's GDAL runtime includes the MSSQLSpatial driver.
Before you start¶
You'll need:
- Host, port (usually
1433), and database name - A SQL Server username and password
- A spatial table or view GeoJibe can read
- Encryption is Required by default (Microsoft ODBC Driver 18). For a self-signed server certificate, keep encryption required and enable Trust server certificate
The saved Source is the database connection. You choose the schema and table each time you import or save a Job.
1. Save the SQL Server Source¶
Open Sources → Add Source → SQL Server.
Fill in host, port, encryption, database, username, and password. Click Test, then Save. Name it something like Production GIS.
Leave Trust server certificate unchecked unless the server uses a self-signed certificate. The connection stays encrypted either way.
2. Add SQL Server on the Canvas¶
Add SQL Server, choose the saved Source or enter the connection, then Connect.
Choose a schema, then a table or view. Click Import. GeoJibe copies the table into the job workspace and inspects it.
After Import, Transform sees the real field names. Convert offers the same formats as an uploaded file.
You can also fill the connection in manually for a one-off run. You do not have to save a Job.
3. Process and deliver¶
Add Transform, Convert, or Python if you need them. Then choose a Destination — Download, PostGIS, another SQL Server table, GeoServer, GeoNode, and the rest work as usual.
Example: SQL Server → Transform → PostGIS.
Click Run.
Saved Jobs¶
When you save as a Job, GeoJibe stores the connection plus the schema and table you selected. The next run imports that table again using the current saved password.