Aqua Data Studio Documentation

[Hetty Calin]

Thisguide requires you to already have access to Aqua Data Studio and be familiar with how to navigate its interface. More information about Aqua Data Studio can be found in the official Aqua Data Studio documentation.

To acquire the necessary credentials for connecting Aqua Data Studio to Experience Platform, you must have access to the Queries workspace in the Platform UI. Please contact your organization administrator if you do not currently have access to the Queries workspace.

After installing Aqua Data Studio, you must first register the server. See the official Aqua Data Studio documentation for instructions on how to launch the Register Server dialog and register the server.

To find your credentials, log in to the Platform UI and select Queries from the left navigation, followed by Credentials. For complete directions to find your login credentials, host, port, and database name, please read the credentials guide.

Query Service also offers non-expiring credentials to allow for a one-time setup with third-party clients. See the documentation for full instructions on how to generate and use non-expiring credentials.

Next, you must set the SSL mode value as ?sslmode=require. This is done from the Driver tab of the Edit Server Properties dialog. See the official Aqua Data Studio documentation for instructions on how to edit driver properties and configure SSL for PostgreSQL. Use the search bar to find the sslmode property.

After inputting your connection details, from the same tab, select Test Connection to ensure your credentials work properly. If your connection test is successful, select Save to register your server. A confirmation dialog appears confirming the connection and the connection icon appears on the dashboard. You can now connect to the server and view its schema objects.

Now that you have connected to Query Service, you can use the Query Analyzer within Aqua Data Studio to execute and edit SQL statements. For more information on how to write and run queries, please read the running queries guide.

Welcome to Aqua Data Studio Documentation - Below you will find 6 quick steps to getting you started with Aqua Data Studio. Once you have your database query tool up and running, you may continue into the documentation to understand the different features of Aqua Data Studio.

Using the Tools available in Aqua Data Studio 20.0 - Once you have connected to a server, use all the different tools available to automate your most complex tasks, including Query Analyzer, Query Builder, Visual Analytics, Debuggers, Editors, ER Modeler and Version Control. Detailed documentation is provided for each.

Now in the Servers Panel find database/schema which documentation you want (if you want to have all schemas in the documentation you can change it in next step). Right-click on any element which belongs to that schema/database and select Tools -> ER Diagram Generator from the context menu.

In the new window, you can specify what objects your documentation should contain. Make sure to check the Include Comments option to have your comments in the documentation. Here you can select to generate documentation for all schemas by selecting in Schema field option.

In the new window select path to save your documentation. Aqua Data Studio generates HTML files and compresses it to zip file, so you need to decompress it to continue. To see your documentation, open the index.html file.

AD Studio server registrations are in [USER_HOME]/.datastudio/connections directory. You can copy your existing connections from one machine to another.AquaFold's documentation about copying registrations from one computer to another is here:

-Connection-files#copy

I initially only copied the connections folder and found none of my passwords worked anymore. Then I added the pfiles.properties file. That fixed the password problem, but when I tried to open a Query Analyzer window on any of my many MS SQL Server registered servers, I got an error: Id 18456, Level 14, State 1, Line 1 Login failed for user ''.

By copying the rest of the files and subfolders in the .datastudio folder (except for the history which I didn't need and the license files as I had to renew my license anyway), the error was cleared. Bottom line, copy the entire .datastudio folder to transfer your configuration to the new machine, as is documented in the aquaclusters Wiki link: "Copying this directory to a new computer copies all of your current ADS customizations and server registrations."

I am following the Vertica 7.1 documentation Administrators Guide/Implementing Security/Client Authentication. I have followed documentation to create server certificate, private key, and root certificate. I use admin tools to distribute to each node in my 3 node cluster. My cluster is Centos 6.5 and has the VMart schema installed. After the configuration parameter EnableSSL is set, the documentation then says to restart the database. This is where I encounter problems. I am using admin tools to stop/start database. It won't start.

There are two modes related to SSL/TLS: SSL Server Mode, and SSL Mutual Mode. The log forwarded indicates that the server side is expecting a client certificate to be passed to it, but there is no indication that you are using SSL Mutual Mode. If you were using SSL Mutual mode, you would need to create and install a client certificate on the client side. As a fix, if you are not using SSL mutual mode, do not set the SSLCA configuration parameter.

Thank you for your quick response. However, I should mention that I am Vertica Community Edition - Vertica Analytic Database v7.0.2-1. Your suggestion isn't possible as that appears to be a Vertica 7.1 feature. There are no such configuration parameters in 7.0.

I can confirm that the certificates are in the correct location; the databases' catalog directory on each node in the cluster. I can confirm that the certificates have the correct permission as well; they are owned by the dbadmin user and only the owner has rw permission on the files.

I manually edit vertica.conf and set "EnableSSL =0" and tried to start database from admin tools but still I could not make it up and running. After restarting database I checked the vertica.conf and still the value is "EnableSSL = 1". Strange issue. Please help.

In my checkered past I've been in charge of a lot of differentRelational Database Management Systems (RDBMS). I've worked on everythingfrom COBOL systems to Oracle, from PostgreSQL to Sybase, and MySQL to SQLServer. Most of the time I've used only one of them at a time, and on theplatform for which they were written, such as VM on a 3270 terminal, Unix,Zenix, Ultrix, HP-Unix, Linux and others, CPM, DOS, OS/2, Mac OS, OS X andWindows of all flavors. In all of those platforms and RDBMSs I normally stayedaway from using third-party tools to manage the systems or the databases. I justlearned the tools that came with the product and supplemented anything I hadtrouble with by writing scripts or programs.

As I moved further in my career, I began to be involved with larger slices ofthe company. In my current position, I'm a "database architect,"responsible for finding the best data solution for multiple requirements. Assuch we're running DB2, Oracle, MySQL and yes, SQL Server. We'rerunning our production systems on large clusters for a pretty substantial userbase.

I also use several operating systems in my work, and at home. I run WindowsXP on one system at work, and Redhat Linux on another. Here at home I use twosystems to write these tutorials: An x64 system running Windows 2003 Enterprise,and a Mac G5 running OS X. I use the Terminal Services client for OS X toconnect to the SQL Server systems running in a Virtual Server on the x64.

So when it comes to managing all of the systems I use, I have one of twochoices. I can either learn all of the different management interfaces andoperating systems, or I can use a tool to manage the systems using oneinterface. Although I keep up-to-date on the systems we have a large footprinton (Oracle and SQL Server, Linux and Windows), from time to time I need to jumpin to a system and run a quick query or reverse-engineer a database schema fromone product to recreate it in another. For that I've found a single tool isbest.

Enter Aqua Data Studio, from Aquafold. Although I'mnot much of a "tool guy," I've been thoroughly impressed with howwell this product does what it says. After working with so many platforms andlearning how they do things differently, I'm even more impressed with thejob Aquafold has done with this tool. In this tutorial I thought I'd sharemy experiences using this tool with you. I'll focus on themultiple-platform to SQL Server part of how I use it.

Working with SQL Server in version 2000, you're familiar with bothEnterprise Managerand Query Analyzer. In version 2005, those tools are replaced with theSQL Server Management Studio.The Aqua Data Studio does much of the same work, and from just about anywhere.Here's a quick feature list:

To get the software, just navigate the Aquafold's site: the "Downloads" section you'll find everything you need basedon the operating system you're working on. The licensing is free forpersonal use and for educational institutions, and it's around 150.00 U.S.as of this writing for everyone else. They have an older version (2.0.7) that isalso free for everyone, but I haven't used that version. I downloaded thelatest version (4.5) and told the company that I planned to do a review on it.

The Windows download comes in two flavors: one without the Java Engine andone with. On the system I tested the product with I used the "withJava" version, since the virtual machine I set up to test with didn'thave Java.

On Linux the install downloaded as a gzipped file, which I decompressed intothe /var directory on my test Redhat Linux install. Once there I justdouble-clicked on the .sh file to load it and hit that same 64-bit SQL Server2000 system, and ran a quick query:

3a8082e126