1. Connect to an External Database

Open the Command Prompt on the computer where MySQL Community Server is installed and navigate to the MySQL installation folder (for example, C:\Program Files\MySQL\MySQL Server 5.7\bin)

Connect to your MySQL server using the following command:

mysql.exe -uroot

In this example, the username is root.In a new MySQL instance, root is the default user and can be logged in without a password. If you are using an existing MySQL Server instance, the username and password may be different.

Create a new user whose credentials Zephyr will use to connect to the database and set a user password. To do that, use the following command:

CREATE USER 'zephyrDBuser@'localhost' IDENTIFIED BY 'zephyrDBuserPass';

Type the command below to make the database accessible remotely:

grant all on *.* to zephyrDBuser@'127.0.0.1' identified by 'zephyrDBUserPass';

where zephyrDBuser is the username and ZephyrDBuserPass is the password of the user created at step 2.

The "*.*" in the command above grant permissions to all databases. Replace 127.0.01 with the IP address of the node where Zephyr will be installed. This command will grant access to all databases for the given IP addresses. The minimum permission requirement is the privilege to create and populate tables.

When installing a database for a Data Center cluster, you need to grant permissions for each node in the cluster.

Now you an access your MySQL database remotely from the designated IPs.

Open the my.ini file (Windows) or my.cnf (Linux). The default location is the MySQL root folder.

Set the following values for the parameters:

If no lines contain these parameters, then create new lines for them.

In Object Explorer, expand the folder of the server instance in which you want to create a new login.

Right-click Security > Logins and select New Login…:

In the Login – New dialog box, on the General page, enter the name of a user in the Login name box.

To create a login that is saved on a SQL Server database, select SQL Server authentication. In the Password box, enter a password for the new user. Enter that password again in the Confirm password box:

From the Default database list, select a default database for the login. Master is the default for this option.

From the Default language list, select a default language for the login.

Click OK.

View the newly created login in the Security > Logins folder:

Next, you need to set permissions for this login. Right click the user and select Properties:

In the Properties window, grant permissions for the user to Alter any database:

The Effective tab will show the minimum permissions that must be provided:

You have created a new Login user with the appropriate permissions.

In this step, we will enable remote connections on the SQL Server instance that you want to connect to from a remote computer.

Staying within SQL Server Management Studio, right-click the server name in the left pane and select Properties:

Select Connections in the left pane and make sure that check-box Allow remote connections to this server is selected:

Now, you need to enable the TCP/IP protocol. To do that, open SQL Server Configuration Manager, expand SQL Server Network Configuration and click Protocols for SQLEXPRESS. Check the status to ensure that the TCP/IP protocol is enabled. If it is disabled right-click on TCP/IP and select Enable:

Select Properties from the same pop-up menu.

On the Protocol tab, make sure that Listen All has a value of Yes:

Now, click the IP Addresses tab, scroll-down to the APAll section, and enter the port 1433 for TCP Port:

Now you can start the SQL Server service.

Open SQL Server Configuration Manager, click SQL Server Services in the left pane, right-click SQL Server Browser service and select Properties.

In the subsequent window, switch to the Service tab, click Start Mode, and select Automatic from the drop-down menu:

Switch to the Log On tab and click Start to start the SQL Browser service.

Make sure the state of the SQL Server Browser service is Running:

Configure the firewall to allow network traffic related to the SQL Server and to the SQL Server Browser service.

The following port exceptions should be set:

A port exception for TCP port 1433:

In the New Inbound Rule Wizard of your firewall, do the following to create a port exception:

A port exception for UDP port 1434:

Click New Inbound Rule again and do the following:

In SQL Server Management Studio, right-click the server name in the left pane and select Properties.

In the subsequent window, select Security in the pane on the left, then select SQL Server and Windows Authentication mode in the Server authentication section, and click OK:

Your database is ready to be used.

In SQL Server Management Studio, right-click on the server name in the left pane and select Properties.

In the subsequent dialog, select Memory in the pane on the left and specify the desired values in the Minimum server memory and Maximum server memory fields. The recommended minimum is 8 GB:

Log files may help you troubleshoot issues. To view the logs in SQL Server, expand Management > SQL Server Logs, right-click any log file, and click View SQL Server Log:

The default collation is binary for Oracle, and the one that is supported. The following query can be used to validate the collation for the user (database):

SELECT COALESCE(value, (SELECT value
             FROM nls_database_parameters
             WHERE parameter = 'NLS_SORT'))
FROM nls_session_parameters
WHERE parameter = 'NLS_SORT'

SELECT * FROM v$nls_parameters WHERE parameter LIKE '%CHARACTERSET%';

Create a table space:

CREATE tablespace jilo
DATAFILE 'jilo.dbf'
SIZE 2120M
AUTOEXTEND ON;

Create an Oracle user:

create user ITCC identified by zephyr default tablespace <tablespace_name> quota unlimited on <tablespace_name>;
grant connect to ITCC;
grant create table to ITCC;
grant create sequence to ITC;
grant create trigger to ITCC;
grant create session to ITCC;
grant create view to ITCC; 

***** If user was created on a default table space of not know , execute following to give unlimited space on current user table space *********
grant unlimited tablespace to ITCC;
***********--------------------------------************
create user DVERSION identified by zephyr default tablespace <tablespace_name> quota unlimited on <tablespace_name>;
grant connect to DVERSION;
grant create table to DVERSION;
grant create sequence to DVERSION;
grant create trigger to DVERSION;
grant create session to DVERSION;
---------------------------------
Internal note: if there are any issues in permissions, use grant all for now.
---------------------------------
CREATE USER itcc IDENTIFIED BY zephyr;
GRANT ALL PRIVILEGES TO itcc;
CREATE USER dversion IDENTIFIED BY zephyr;
GRANT ALL PRIVILEGES TO dversion;

If you face issues with the table space, try doing the following: for data files below, find the path of data files and use path value and replace the value "<example>/u01/app/oracle/oradata/XE/system.dbf<example>" below.

SELECT * FROM DBA_DATA_FILES;

ALTER DATABASE DATAFILE '<example>/u01/app/oracle/oradata/XE/system.dbf<example>' 
AUTOEXTEND ON MAXSIZE UNLIMITED;