Environments and Data Sources

Environments and Data sources are a critical configuration component to manage data accessibility.

Each data source contains the configuration information necessary to connect to and access one or several schemas within a database on a specific server.

Note

Every Data Model in Nectari is based upon one Data Source.

Tip

Users can easily change between environments for the active view using the Environment drop-down in the toolbar. It will be applied to open views.

To access the Environments and Data Sources:

In the Administration section , click on Env. & Data Sources in the left pane.

An Environment can contain several Data Sources.

Add an Environment (Button):: Use this to add a new Environment. Add as many environments as required.
Set as Default:: Defines selected environments as the default environment when users connect.
Set as Data Warehouse:: Set a data source as warehouse, so it is used to build the cubes. Only one data source can be set as data warehouse.
Add a Data Source (Button):: Use this to add a new data source. The data source will be added in all the existing environments automatically. The data source needs to be configured in each environment.

When defining a Data Source the following fields must be completed:

Description:: Indicates the name that will be displayed in the Data Source list.
Type:: Indicates which type of database connection the data source is using. The available options are SQL Server, Access, ISeries, Oracle, OLEDB and ODBC for MySQL, Excel, Pervasive and Teradata. To access another type of database, either create an OLEDB connection, or create an SQL linked server.
Server:: Contains the server instance name.
Database Name:: Contains the database name. (e.g, For Oracle it will be SID).
Database Schema Name:: Contains all the database schemas which should be accessible by a Data Model based on this particular data source. It is possible to add as many schemas as desired.; Take care to enter the schemas in the correct order in case the same table or view name exists in more than one schem (the first schema in the list will be placed at the top of the list).; The schemas should be entered in the following format:; SQL, OLEDB: Database name and schema name (ex: databasexyz.schemaxyz).; Oracle: User name and schema name (ex: userabc.schemaabc).; DB2: Library Name only.; Access: Not Required.
Transaction With (No Lock) (SQL and iSeries only):: Use this option when you want to read the transaction without waiting for the lock on the tables to be released. Be careful, you may read transactions that will not be accurate as some of these transactions could be uncommitted.
Force Translation (iSeries only):: Activate this option to use the connector property Force Translate.
Port (Oracle only):: Contains the port number of the Oracle instance.
Path (Access only):: Contains the path of the Access database.
Pooling (Oracle only):: Activate then define the Pooling parameters (Min and Max pool size, Increase and Decrease numbers).
Authentication Strategy:: A drop-down indicates how Nectari is supposed to connect to the database. The available options are Windows Authentication (when Nectari runs on the same server as the database being accessed and if the local host account under which the Nectari account runs has access to the database) and Use Specific (if using a specific server user to access the data).
User Name and Password:: Contains the information required if the Use Specific option was chosen for the credentials.

In the data source used for the OLAP cube (pointing to the NectariCube database), after clicking on Set as Data Warehouse, two new fields will appear.

Env. & Data Sources - Data Warehouse

Data Warehouse Schema:: The schema to use for the OLAP Cubes (it is usually the same than the custom schema).
Use MARS during the cube loading (SQL Server only):: Checking this box will activate Multiple Active Result Sets (see below).