...
With the SQL Connector it is possible to use SQL Server to import data into SuperOffice from a SQL Database or export data from SuperOffice to a SQL Database.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This feature is in a pilot fase, so it is placed behind a feature toggle. If you want to participate in the pilot, please send a request to support@infobridge.com |
Requirements
Specific features, functionalities, and limitations are dependent on the type of subscription plan. For a comprehensive overview, please refer to the following subscription overview page.
Supported SQL versions
SQL Server 2016 (aka SQL Server 12) and newer
Azure SQL Database
...
We advise, for security reasons, to only whitelist the IP addresses that DataBridge uses. These are listed here: Requirements and checklist before use .
Additional requirements
A database needs to be set up before you connect DataBridge to your SQL instance.
...
Select “Microsoft Azure SQL & Microsoft SQL Server” as Location when importing or as Destination when exporting.
...
Configure profile
...
CONNECTION | |
|---|---|
Authentication mode | Select the authentication type for connecting to SQL Server (SQL Server Authentication or Active Directory) |
Server name | Enter the name of your database engine and port number, seperated by a comma. The server name can be an ip-address or DNS name and port number is only necessary if it is different than the default port (1433) |
Database name | Enter the name of the database |
Username | Enter username |
Password | Enter password |
Configure Source
When exporting to SQL
When exporting the “configure source” step is the same as default.
When importing from SQL
...
CONFIGURE SOURCE | |
|---|---|
Source table | Select the table or view you want to import data from |
Delete Imported rows | When set to “Yes”, DataBridge will delete the records in the source table after importing. This is only possible when importing from a table that has a primary key and does not apply to views. |
Destination Settings
When exporting to SQL
...
TABLE | |
|---|---|
Table Schema | The schema name of the target table |
Table name | The name of the target table. If this table does not exist, it will be created |
Table action | Wat should be done if the target table already exists. There are 3 options:
|
Duplicate match | Select the column that will be used for duplicate checking |
Duplicate action | Select what action that has to done when duplicates are found |
Skip if not found | If set to “Yes“, only the records that already exist will be processed. No new records will be created |
COLUMNS | |
|---|---|
Use display name as column name | If set to “Yes”, the friendly display name will be added between parentheses to the column name |
Remove unmatched columns | If set to “Yes”, columns in the target table that do not exist in the source data will be removed |
When importing from SQL
When importing the “configure source” step is the same as default.
...