The following prerequisites are applicable to all databases.
Ensure the common conditions are met before proceeding with the database-specific prerequisites listed below.
To import data from MSSQL into Zoho Analytics, refer this documentation.
The user account that is used to connect with MSSQL server should have the following roles associated in the respective database.
Database name | User role |
AMDB | Public, db_owner |
Master | Public, db_datareader |
msdb | Public, db_datareader |
If you would like to connect SQL Server using an SQL named instance, ensure that the 'SQL Browser Service' is running on the MSSQL host server, and provide View Database State permissions to the user.
To provide the View Database State permission,
Follow the steps below to enable remote connections:
host all all <IP address> trust
Replace <IP address> with the IP address of the Zoho Analytics server. The IP address must be mentioned along with the subnet mask. For example: 192.168.1.1/24.
listen_address = '<IP address>'
Replace <IP address> with the IP address of the Zoho Analytics server. For example: 192.168.1.1.
To import data from PostgreSQL into Zoho Analytics, refer this documentation.
Login to your MySQL database as a root user. Navigate to the <MySql_Home>\bin folder in terminal/command prompt, and run the following command.
mysql -u root -p
mysql> GRANT ALL ON <Database Name>.* TO <Username>@<IP address> IDENTIFIED BY <Password>;
Note:
To import data from MySQL into Zoho Analytics, refer this documentation.
To connect to an Oracle database, you must set the operating system environment variable.
On the Windows platform, environment variables are stored in the Windows registry, and are automatically set for you. You need not set them manually.
To set environment variables when connecting remotely from Oracle Database XE, enter one of the following commands in a terminal session at the remote computer.
For Bourne, Korn, or Bash shell:
source <Oracle_Home>/product/11.2.0/client/bin/oracle_env.sh
For C shell:
source <Oracle_Home>/product/11.2.0/client/bin/oracle_env.sh
To import data from Oracle into Zoho Analytics, refer this documentation.
Note: To connect to the Oracle database, a user with both CONNECT and SELECT_CATALOG_ROLE is required.
By default, the remote access is enabled when you install Adaptive Server. However you can enable remote access by running the following from command prompt/terminal on the Sybase database server host.
sp_configure "allow remote access",1
Allow remote access is dynamic and does not require your adaptive server to be restarted to take effect. Only a system security officer can set allow remote access.
Follow the below steps to grant user permissions to connect with a Sybase server.
These instructions assume that IBM InfoSphere DataStage has already been installed on your local machine and that the parallel engine is available on the remote machine.
Verify that the INFORMIX sqlhosts file on the remote machine has a TCP interface. A TCP interface is necessary to use the remote connection functionality.
Copy the INFORMIX etc/sqlhosts file from the remote machine to a directory on your local machine. Set the INFORMIX HPLINFORMIXDIR environment variable to this directory.
For example, if the directory on the local machine is /apt/informix, the sqlhosts file should be in the directory /apt/informix/etc, and the HPLINFORMIXDIR variable should be set to /apt/informix.
Set the INFORMIXSERVER environment variable to the name of the remote INFORMIX server.
Add the remote INFORMIX server nodes to your PX node configuration file located in $APT_ORCHHOME/../../config; and use a nodepool resource constraint to limit the execution of the Informix enterprise stage to these nodes.
In the example configuration file below, the local machine is fastname local_machine, and the INFORMIX remote server machine is fastname remote_machine. The nodepool for the remote nodes is arbitrarily named "InformixServer". The configuration file must contain at least two nodes, one for the local machine and one for the remote machine.
Go to the Stage page Advanced tab of the Informix enterprise stage. Select Node pool and resource constraints and Nodepool along with the name of the node pool constraint (i.e., "InformixServer" in the example configuration file above).
Set up environment variables. Remote access to an INFORMIX database requires the use of two HPLINFORMIXDIR environment variable settings, one for the local InfoSphere DataStage workstation which is set up in step 2 above, and one for the workstation with the remote INFORMIX database. The remote variable needs to be set in a startup script which you must create on the local workstation. This startup script is executed automatically by the parallel engine.
HPLINFORMIXDIR = /usr/informix/9.4
export INFORMIXDIR
INFORMIXSQLHOSTS=$HPLINFORMIXDIR/etc/sqlhosts
export INFORMIXSQLHOSTS
shift 2
exec $*
To connect to an IBM Informix database, a user requires Connect database-level privileges and access to sysmaster database.
To connect to IBM Informix DB, make sure that the ifxjdbc.jar file is found under the <Zoho Analytics home>/reports/lib folder. The jar file can be copied from the IBM Informix installation location, <IBM Informix Home>\jdbc\lib\jar. Restart Zoho Analytics after copying the file.
If you are still unable to connect to the IBM Informix database, try making the following changes to your sqlhosts file on the local workstation.
To access Pervasive database from a remote server, you need to register the server. Follow these instructions to register a remote server engine
To connect to Pervasive SQL, make sure the pervasiveJDBC jars (jpscs.jar, pvjdbc2.jar, pvjdbc2x.jar) are present in the <installation directory>/reports/lib folder, and restart Zoho Analytics.
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.