Send data to SQL Server¶
GeoJibe can write the result of a workflow straight into a SQL Server table.
You need to be signed in. Download is not involved — SQL Server is the Destination.
SQL Server appears only when GeoJibe's GDAL runtime includes the MSSQLSpatial driver.
Before you start¶
You'll need:
- A SQL Server database you can write to
- Host, port (usually
1433), database name, username, and password - A table name for this delivery
Save the connection once, then reuse it.
1. Save a SQL Server Destination¶
Open Destinations → Add Destination → SQL Server.
Fill in Host, Port, Encryption, Database, Username, and Password. Default schema is optional (often dbo).
Leave Trust server certificate unchecked unless the server uses a self-signed certificate. The connection stays encrypted either way.
Click Test, then Save. Name it something like Production GIS.
The saved Destination is the database login. Schema, table, and write mode belong to each workflow.
2. Add your data and any changes¶
Upload or import a vector dataset. Add Transform or Convert if you need them.
SQL Server is for vector data.
If you used Convert to reproject, SQL Server receives that CRS. GeoJibe does not reproject again at the Destination.
3. Choose SQL Server¶
Add SQL Server and select the saved Destination.
Then set:
| Field | Typical value |
|---|---|
| Schema | dbo, or another schema you are allowed to use |
| Table | neighborhoods |
| Write mode | See below |
4. Choose a write mode¶
| Mode | What it does |
|---|---|
| Create | Creates a new table. Fails if the table already exists. |
| Replace | Overwrites the table if it exists. |
| Append | Adds rows to an existing table. Fails if the table is missing. |
Warning
Replace mode can overwrite an existing destination table.
5. Run¶
Click Run, or Send to SQL Server in Classic.
You should see a successful delivery to schema.table.
What happens next?¶
GeoJibe writes the converted layer into that table (geometry column geom, SQL Server geometry type). Open it in QGIS or your database tool to confirm.
This is a one-off unless you save a Job.
Example: HTTP/API → Transform → SQL Server.
Having trouble?¶
See SQL Server connection failed.