Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Preconditions:

InfoTo be able to run a query in third-party-tool User need permission “SQL Cloud Share“ which gives access to SQL Cloud Server, through which he can share queries usingJDBC/ODATA. More information about permissions you will find here.

Step 1. Download the library above and install it on your PC

Step 2.

Step 1. Install the OData Local Server

Since SQL for Cloud is a JavaScript database sunning in the browser, it needs some extra help to listen for connections. Hence we have developed a OData Local Server to connect the browser with the analytics tools of your choice (like MS PowerBI, Tableau, etc.) running on your PC.

Please download the library below and install it on your PC to get it working:

View file
nameinstall_sqlc_odata_server_1.0.0.jar

(Java 1.8 or above required)

Open a console from your desktop (you might run it as an administrator) and run the installer:

C:\ .. > java -jar install_sqlc_odata_server_1.0.0.jar

Image Added

and complete the assistant:

Image Added

Step 2. Ask your Jira Administrator for permissions to connect

Only uses with the SQL Cloud Connect global permission can connect and share data with third parties.

This is controlled by Jira Administrators, so if you do not see the SQL Cloud - Query Server option under the Apps menu, please ask your Jira administrator grant you. (Read more about the global permission here)

Image Added

Step 3. User credentials

As most databases, SQL for Cloud requires the user credentials before sharing any data with third parties, including the OData Local Server above.

Open the SQL Cloud Query Server page and set your password:

Image Added

  • Username: Must match It is read only and it matches the name of the Jira Cloud instance (https:<instance>.atlassian.net)

  • Password: Each time you open SQL Cloud Query Server - the new A random password is generated automatically. To check the password or change it - Click the button , but you can change it by clicking Edit passwordlink and set your own.

Image Removed Below the STATUS SELECT
  • Never use the Jira password here as this is instated to control to the SQL Cloud database access and not for Jira login.

Step 4. Enable the Server feature

Furthermore the Jira Administrator grant as described above, the server feature is disabled by default and it will not accept any third-party connection until the Jira user enables it explicitly:

Please, select the checkbox “ENABLED”, so the local server could connect to it.

Info

More information about server Status you will find here.

Your server is disabled and no one can connect to it

Now your server is ready to be connected

Step

3. Open the installed driver and copy the URL from there.

5. Start the OData Local Server

The installer created a quick access in the Windows start menu:

Image Added

The OData Local Server will open a console window at the start up.

Copy the URL from the console:

Step

4.

6. Login the OData Local Server

Insert copied URL into the search bar in your Browser and press enter. It will ask you to insert the login and password that you have already set in SQL Cloud Query Server (look at Step 24)

If the password and login are set correctly, you will see this message in your browser

Step 5. Now you can go back to SQL Cloud Query Server. In the right upper corner will appear a button that will bring you to OData feed builder, where you can insert Query, select primary key (it's not required), and build feed URL

The action button appears in the right upper corner of SQL Query Server window

Insert your SQL query and press “Build Feed URL”

Now you can Copy URL and connect third-party tool through it (example below)

Example

Let's connect it to Power Bi

1. Select the type of Data (ODATA Feed)

2. Insert copied URL from ODATA feed Builder (look at Step 5)

3. Insert the login and password that you previously set in your SQL Cloud Query Server (look at Step 2) and select the name of your local host (look at Step 3)

DONE!!!

Now your query is transformed into tables that are ALREADY interconnected and you can build your best report!