Peliqan Satellite is used to connect on-prem business applications and databases to the Peliqan data cloud. Install Peliqan Satellite on your on-prem Windows server, in order to sync data from an on-prem SQL Server database to your Peliqan data warehouse. Once the data is synced, you can use it for BI/reporting, MCP access to your business data, to build Data Apps and publish APIs.
- Installation of the agent
- How to use
- Configuration for specific data sources
- Expert/M
- Adsolut
- Plenion
- Exact Venice
- Sage Bob 50
- Winbooks
- Other
- Limitations
- Configuration
- Follow the steps in the installer
- Configure the Source
- Configure the Target
- Configure settings
- View logs
- FAQ
- Releases
Installation of the agent
Download the latest version of the installer: https://peliqan.io/winagent/latest/PeliqanSatellite-win-x64.msi
Follow the steps in the Windows installer.
How to use
Install the Peliqan Satellite agent on a Windows server with access to your SQL Server database.
Make sure TCP/IP is enabled in SQL Server.
Use a SQL Server user for authentication on your databases, to avoid issues with the Peliqan Service running under a different user (this can happen when using Windows authentication).
In case new databases are created and the Windows agent needs to sync that data as soon as the database appears, make sure to grant access to all databases (including new databases created in the future):
GRANT CONNECT ANY DATABASE TO [peliqan];
GRANT SELECT ALL USER SECURABLES TO [peliqan];CONNECT ANY DATABASE lets Peliqan Satellite connect to every database on the SQL Server instance, present and future. SELECT ALL USER SECURABLES lets Peliqan Satellite select from all tables/views in any database it can connect to.
Configuration for specific data sources
Use Peliqan Satellite to sync data from your on-prem software, for example accounting software installed on your own computer.
Expert/M
Add a SQL Server user for Peliqan, on the SQL Server used by your Expert/M accounting software.
Select “SQL Server” as the source type and fill in all the details.
Enable the option “Sync all databases” and “Merge all source tables based on name” since Expert/M will create a separate DB for each end-customer (dossier).
Adsolut
Add a SQL Server user for Peliqan, on the SQL Server used by your Adsolut accounting software.
Select “SQL Server” as the source type and fill in all the details.
Enable the option “Sync all databases” and “Merge all source tables based on name” since Adsolut will create a separate DB for each end-customer (dossier).
Plenion
Add a SQL Server user for Peliqan, on the SQL Server used by your Plenion ERP software.
Select “SQL Server” as the source type and fill in all the details.
Exact Venice
Add a DB user for Peliqan, on the Actian Zen DB used by Exact Venice.
Select “Actian Zen DB” (ODBC) as the source type and fill in all the details.
Sage Bob 50
Coming soon.
Winbooks
Coming soon.
Other
Add a DB user for Peliqan, on the DB used by your on-prem software.
Limitations
- No incremental sync: the agent applies truncate & full resync on each run.
- Only SQL Server and ODBC are supported as source (including DBs from on-prem accounting software and ERPs such as Expert/M, Adsolut, Plenion, Exact Venice…).
- Only Postgres and Bigquery are supported as target data warehouse.
- No support for composite PKs in source tables.
Configuration
Follow the steps in the installer
Once the installation completed, configure Source, Target and Settings.
Configure the Source
Enter the details to connect to your on-prem SQL Server. Make sure to create a SQL user first for Peliqan.
Configure the Target
Configure a target data warehouse from your Peliqan account).
Get all details from your data warehouse from the connection card in your Peliqan account under Connections. Example:
For optimal security, create a new DB user specifically for the Windows agent. For dedicated data warehouses: create a new DB user, with write permissions on one target schema. For shared data warehouse instances: contact Peliqan support to request an additional data warehouse DB user.
Example for a Postgres DWH:
Example for a Bigquery DWH:
Configure settings
View logs
FAQ
What are alternatives for on-prem connectivity ?
You can also use a VPN connection.
Can Peliqan Satellite write to the on-prem database ?
No, only read data and send that data to the Peliqan cloud data warehouse.
Do I need to open my firewall ?
You only have to make sure that the agent can make an outbound database connection to the Peliqan cloud (Postgres or Bigquery data warehouse). No inbound connections are needed from the public internet to your on prem environment.
Can Peliqan Satellite create conflicts with other database users (e.g. backup software) ?
No, Peliqan Satellite will only read data using “SELECT” queries, and it will not create locks on tables.
Releases
v1.3: Multiple pipelines and faster syncs at large scale
Performance improvements for large multi-database syncs:
- Discovering and mapping tables now happens in one batch per source database instead of per table.
- Copying data now streams each table over a single connection instead of reconnecting for every batch, which improves speed.
Reliability & visibility:
- The sync log now streams to the target's log table incrementally during table discovery, not just at the end — so a long-running sync is visible in progress instead of appearing silent for hours.
- Fixed a bug where a table that failed during discovery could make the whole run silently report "0 failed" even though something genuinely went wrong.
v1.2: Generic ODBC source support
- Added support for connecting to Actian Zen DB via ODBC (using DSN or DSN-less connection string), including primary-key discovery, view listing, and paged reads adapted to Zen's SQL dialect.
- Fixed an issue affecting sync timing accuracy and a BigQuery key-field handling bug.
v1.1: Support for composite keys
- Support added for composite keys
- UI improvements
v1.0: Initial release
- Support for SQL Server as source DB
- Support for Postgres and Bigquery as target DWH
v0.x: Beta versions