...
Customers are, by default, provisioned a single user account for access to all data tables. A customer may request a single user account for each distinct data table in the environment.
By default, only the customer’s Square 9 hosted cloud resources will have the ability to connect to any cloud data source. The customer may request direct access from their environment to the cloud data source, and may request up to five static ip address to access the data sources. A customer requesting direct access MUST HAVE A STATIC IP ADDRESS.
A single cloud hosted database will be accessible from all requested IP addresses. If a single customer wishes to restrict datasources by IP address, multiple cloud hosted database will need to be purchased.
A customer’s cloud hosted database may host, at most, 5gb of data in total. If a customer needs more than 5gb of hosted data, additional cloud hosted database licensing is required.
Cloud Hosted Data Load
| Note |
|---|
I don’t know this will be necessary, and perhaps shouldn’t even be offered. Leaving it here for now, but customer’s can bulk load and manage their own data sources using a capture workflow. The SQL Node can facilitate CSV imports to the table. |
Customers who lack the means or desire to manage their own data loading tasks may opt-in to the Hosted Data Load feature. Sold in packs of 5, customers can load 5 unique data sources into 5 unique data tables of a cloud hosted database.
...
Straight data load
Load data from Set SQL Node (Updated to support PostgreSQL)
Read data from Set SQL Node (Updated to support PostgreSQL)
Load ABL data from data source (Currently SQL Connection String)
Load Data XChange from data source (Currently OLEDB Connection String)
Internal Notes
Customers will not need visibility into any of this provisioning, but the following setup considerations will be required:
SQL Node requires updates.
Implement Postgresql driver
Add the ability to bulk import from CSV
Data XChange - Has some setup challenges. It is understood these requirements are not ideal. Before we invest in making this easier with code, we should explore how much of this is going to be out there.
Requires a linked server to the customer Postgres database.
Requires a database the customer has a user with credentials to.
Requires a view be created for each table.
ABL
Leverages the same database/view setup required by DX