Create Data Sources in Nectari

A data source defines how Nectari connects to a database. Each data model connects to one data source, and you can assign multiple data sources to a single environment. Nectari supports multiple connectors (SQL Server, Oracle, Snowflake, Sage Intacct, Acumatica, and more) with different authentication methods depending on the connector and your security requirements. The setup fields and options change from one connector to another, so not every property applies to every database type.

important

Make sure to create an environment before you can create a data source.

When to create data sources

• Connect to multiple systems when your reporting environment pulls data from more than one database.
• Separate connections by purpose to keep reporting, analytics, and integration databases organized and easier to manage independently.

Supported connectors

Acumatica

iSeries (IBM DB2)

Microsoft Access

ODBC Excel

ODBC for MySQL

ODBC Pervasive

ODBC Teradata

Oracle

Sage Intacct (Finance)

Snowflake

SQL Server

note

The supported connectors page covers all available options across Nectari and DataSync.

Create a data source

1. In the navigation panel, select the gear icon to open the Administration section.
2. Select Env. & Data Sources.
3. Select the environment where you want to add the data source.
4. In the Data Sources panel, select the + icon.
5. Fill in the required fields in the Data Source Definition panel.
6. Select Validate, then Save.

Data source definition fields

Not all fields appear for every connector type. The fields shown depend on the type you select. If it applies to a specific, its shown in the thirs column of the table.

Field	What to enter	Connector
Data Source Description	A unique name for this data source. Pick something clear and recognizable. For example: SAGE100_CONSO.
Type	The database type you are connecting to. For database types not listed, use an OLEDB connection or a SQL linked server.
Server	The database server name, hostname, or network address. For example: W2K16S100DS\SQL2016.
Database Name	The name of the database or warehouse. This field is case sensitive. For Oracle, enter the Oracle SID.
Extra connection string properties	Optional. Any additional connection string parameters required by your database provider.
Transaction With (No Lock)	Reads data without waiting for locks to be released, which can improve performance on busy systems. Note that this may return uncommitted or incomplete data.	SQL Server, iSeries
Database Schema Name	Defines which schemas are available to data models. You can add more than one. Use the following format: SQL, OLEDB – database name + schema name (e.g., databasexyz.schemaxyz) Oracle – user name + schema name (e.g., userabc.schemaabc) DB2 iSeries – library name only Access – not required If more than one schema contains the same table or view name, the first one listed takes priority.
Force Translation	Enables the connector's Force Translate property when required by your environment.	iSeries
Port	The port number used by the Oracle instance.	Oracle
Path	The full file path to the Access database file.	Access
Pooling	Enables connection pooling to improve performance. Default values are: Min. Pool Size: 1 Max. Pool Size: 100 Decr. Pool Size: 1 Incr. Pool Size: 5 The Oracle server must support more connections than the Max Pool Size value.	Oracle
Nectari Schema	The schema used by Nectari components. This defines where the application stores and reads its internal objects.
Authentication Strategy	How to authenticate with the database.

Authentication strategy

The authentication strategy controls how Nectari identifies itself to the database. The available options depend on the connector type.

Windows Authentication

Windows Authentication

Connects using the Windows service account that runs Nectari. No credentials are stored or entered manually.

• When to use it: when Nectari and the database server are on the same domain and the service account already has read access to the database.
• What to configure: nothing. The connection authenticates automatically using the service account identity.

Use Specific (Basic)

Use Specific (Basic)

Connects using a username and password that you enter in the data source definition.

• When to use it: when the database has its own credentials or when the Nectari service account does not have direct access to the database server.
• What to configure: the username and password of a database account with read access to the target database.

Key Pair Authentication

Key Pair Authentication

Connects using a private key file instead of a password. The database server validates it against a registered public key.

• When to use it: when connecting to cloud databases like Snowflake or when your security policy requires certificate based authentication instead of passwords.
• What to configure: the username, the private key file path on the Nectari server, and the passphrase if the key is encrypted.

OAuth 2.0

OAuth 2.0

Connects using token based authentication. Nectari requests an access token using registered application credentials instead of a static password.

• When to use it: when connecting to Acumatica, which recommends OAuth 2.0 for API access. This is the only connector that supports this method.
• What to configure: the OAuth endpoint URL, client ID, and client secret from the OAuth application registered in your Acumatica instance.

note

For the full setup steps, see the Acumatica data source page.