Skip to main content
Installation Progress
  1. Create the source connections
  2. Create the destination connection
  3. Import the extractions
  4. Schedule the extractions
  5. Set up the data sources in Nectari
  6. Import the template
  7. Build and load the OLAP cubes

Data Source

A data source defines how Nectari connects to your Sage 100 NA data warehouse. When you create a data source, its description is used across all your environments. Before starting, create a SQL or Oracle user if not already in place. You will then need to add two data sources: the ERP data source and the OLAP cube data source.

Data sourceDescription
ERP data sourceConnects to your main ERP data warehouse for transactions and records.
OLAP cube data sourceConnects to the OLAP cube for analytics and reporting.

Before configuring a data source, make sure you have your database server details—such as the server name, instance, and authentication strategy—as well as the main ERP database name and schema ready.

Create a SQL or Oracle user

A dedicated database user is required to allow Nectari to access the Sage 100 NA data warehouse.

Most Sage 100 NA templates use SQL for the data warehouse, and this is the recommended setup for partners. However, Oracle is also supported if your organization already uses it as a data warehouse platform.

UserWhen to choose
SQLUse if your data warehouse is hosted on Microsoft SQL Server. (Recommended)
OracleUse if your data warehouse is hosted on Oracle Database.

Manage data sources

Rename the Production environment (optional)

  1. Log in to Nectari.
  2. In the navigation panel, select the gear icon to open Administration.
  3. Select Env. & Data Sources. By default, an environment named Production appears under Environments.
  4. Select the pen icon next to the environment name.
  5. Enter a new name and click Confirm.

Create the ERP data source

  1. Log in to Nectari if you're not already connected.
  2. In the navigation panel, select the gear icon to open Administration.
  3. Select Env. & Data Sources.
  4. In the Data Sources panel, click + to create a new data source.
  5. Fill out the ERP data source configuration, entering all required properties in the Data Source Definition panel.
  6. Click Validate and then Save to complete the setup.

Data Source Definition properties

PropertyDescription
Data Source DescriptionEnter a name such as Sage 100 NA Data Source.
TypeSelect SQLSERVER or Oracle.
ServerEnter the database server name where the Sage 100 NA data warehouse is hosted (from DataSync).
Database NameFor SQL Server only. Enter the warehouse database name (from DataSync). It is case sensitive.
SIDFor Oracle only. Enter the warehouse database name (from DataSync). It is case sensitive.
PathFor Oracle only. Enter the port number of the Oracle instance.
Extra connection string propertiesLeave blank unless otherwise instructed.
Transaction With (No Lock)For SQL Server only. Leave checked.
PoolingFor Oracle only. Activate and define pooling parameters to improve performance.

You can keep the default values or adjust as needed: Min. Pool Size 1, Max. Pool Size 100, Decr. Pool Size 1, Incr. Pool Size 5.
Database Schema NameAdd two entries using +:
For both, make sure you replace DatabaseName by the actual value.

  • DatabaseName.dbo – The default schema.
  • DatabaseName.NEC_CUSTOM_SCHEMA – The Nectari custom schema (replace CUSTOM_SCHEMA with the schema name).
    Use this naming convention: start with NEC, use all capitals, and separate words with underscores.
    Use a unique custom schema name for each environment.
Nectari checks schemas in the listed order and uses the first match found.
Nectari SchemaEnter the custom schema name as above NEC_CUSTOM_SCHEMA.
Authentication StrategySelect UseSpecific from the dropdown list.
User NameEnter the SQL or Oracle username created in Create a SQL or Oracle user.
PasswordEnter the password for that user.

Create the OLAP cube data source

  1. In the Data Sources panel, click + to create another data source.
  2. Fill out the ERP data source configuration, entering all required properties in the Data Source Definition panel.
  3. Click Validate and then Save to complete the setup.
  4. Select the data source you just created and click Set as Data Warehouse.
    An icon appears next to the data source name and some new fields appear in the Data Source Definition panel.
  5. In Data Warehouse Schema, enter the same custom schema name NEC_FOLDER.
  6. Leave Use MARS during the cube loading unchecked.
  7. Leave Columnstore indexes checked.
  8. Click again Validate and then Save.

Data Source Definition properties

PropertyDescription
Data Source DescriptionEnter a name such as Sage 100 NA OLAP CUBE Data Source.
TypeSelect SQLSERVER or Oracle.
ServerEnter the database server name where the Nectari OLAP for SQL Server component is installed.

If you select Oracle in Type, the OLAP component is not provided and must be installed manually.
Database NameFor SQL Server only. Enter the warehouse database name (from DataSync). It is case sensitive.
SIDFor Oracle only. Enter the warehouse database name (from DataSync). It is case sensitive.
PathFor Oracle only. Enter the port number of the Oracle instance.
Extra connection string propertiesLeave blank unless otherwise instructed.
Transaction With (No Lock)For SQL Server only. Leave checked.
PoolingFor Oracle only. Activate and define pooling parameters to improve performance.

You can keep the default values or adjust as needed: Min. Pool Size 1, Max. Pool Size 100, Decr. Pool Size 1, Incr. Pool Size 5.
Database Schema NameAdd two entries using +:

  • OLAPCube.NEC_ERP_SCHEMA – The ERP schema (replace ERP_SCHEMA by the folder name).
  • OLAPCube.NEC_CUSTOM_SCHEMA – The Nectari custom schema (replace CUSTOM_SCHEMA with the schema name).
    Use this naming convention: start with NEC, use all capitals, and separate words with underscores.
Nectari SchemaEnter the custom schema name as above NEC_FOLDER.
Authentication StrategySelect UseSpecific from the dropdown list.
User NameEnter the SQL or Oracle username created in Create a SQL or Oracle user.
PasswordEnter the password for that user.