Commit f674e692 authored by Jeffrey Schlitt's avatar Jeffrey Schlitt

autocomplete, db support, lots of other

parent 47677365
Redshift,Hive,Netezza,Snowflake,Greenplum
Databases,Databases,Databases,Databases,Databases
Tables, Tables, Tables,Warehouses,Schemas
Views, Views, Views,Tables,Tables
Users,,Sequences,Views,Views
Groups,,Stored Procedures,Scalar Functions,Columns
Libraries,,Users,Roles,Users
Stored Procedures,,User Groups,,Groups
Users,,Server Configuration Variables,,Functions
User Groups,,,,Aggregates
,,,,Operators
,,,,Primary Keys
,,,,Foreign Keys
,,,,Partitions
,,,,External Tables
,,,,Sequences
\ No newline at end of file
Database Feature,Postgres,SQL Server,Azure SQL,Azure SQL DW,DB2,Redshift
,,,,,,
Tables,Yes,Yes,Yes,Yes,Yes,Yes
Views,Yes,Yes,Yes,Yes,Yes,Yes
Stored Procedures,No,No,No,No,No,Yes
External Libraries or User Defined Functions,No,No,No,No,No,Yes
Sequences,No,No,No,No,No,Yes
,,,,,,
,,,,,,
,,,,,,
Autocomplete Support,No,No,No,No,No,Yes
\ No newline at end of file
......@@ -21,31 +21,29 @@ Viewing the Database Data Dictionary
Once you have established a connection to a database you can browse the database dictionary catalogs. You can toggle to the **Database Explorer** browser by clicking on the tab as shown below. The database data dictionaries typically contains the tables, columns, views and other database objects available to query from the query panel.
.. image:: ../../Pro_Images/Pro_Browser_DB.png
:scale: 30
:scale: 50
:align: center
:alt: Browse the Database Catalog
Once you have selected the **Database Explorer** tab you can drill into each connection as shown below.
.. image:: ../../Pro_Images/pro_browser_navigate.png
:scale: 30
:scale: 50
:align: center
:alt: Browse the Database Catalog
The following table(s) will detail what objects are visible from the browser for Redshift, Netezza, Snowflake, Hive, Greenplum and Postgres.
.. _dbsupport:
.. csv-table::
:file: db_capabilities.csv
:header-rows: 1
:align: left
Database Object Support by Platform
=====================================
The following image details what objects are visible from the browser for all of our currently supported platforms. We do releases every two weeks with |var_product_name| so if there is a feature you need please contact us at support@aginity.com.
The following table(s) will detail what objects are visible from the browser for SQL Server, Azure SQL, Azure SQL DW and DB2
.. csv-table::
:file: db_capabilitiesPartII.csv
:header-rows: 1
:align: left
.. image:: ../../Pro_Images/AginityProDBSupport.png
:scale: 90
:align: center
:alt: Browse the Database Catalog
......@@ -54,11 +52,47 @@ Quick Actions from Explorer
Currently you can do the following quick actions from the **Database Explorer**
#. Drag and drop any object from the **Database Explorer** to the **Query Panel**
#. Copy the path of an object by right-clicking on the object and selecting **Copy Path**
SQL Statement Generation
------------------------
To generate typical SQL statements from tables or views you can right click on the object, navigate to scripts and choose the appropriate script as shown below.
.. image:: ../../Pro_Images/AginityProDBExplorerScripts.png
:scale: 60
:align: center
:alt: Browse the Database Catalog
Selective SQL Generation on a Set of Columns
----------------------------------------------
To generate SQL statements based on a selection of columns within a Table or View, multi-select the columns by holding Ctrl (Windows) or Command (Mac) and selecting the columns as shown below. Then generate the SQL statement.
.. image:: ../../Pro_Images/AginityProDBExplorerColSelect.png
:scale: 60
:align: center
:alt: Browse the Database Catalog
.. hint::
Make sure you don't have the table name selected and column names at the same time. If you do it will generate the SQL for the whole table.
Drag and Drop Capabilities
--------------------------
You can drag and drop any object from the DB Explorer into the Query Panel
.. note::
Double-clicking expands the DB Explorer tree
Copy JDBC Connection String
-----------------------------
If you select any Connection (Top level of the tree) and select "Copy Connection string to Clipboard" you will get the full JDBC URI which is helpful for debugging. See this `Knowledge Base Article <https://support.aginity.com/hc/en-us/articles/360035391473-Debugging-JDBC-Connectivity-Issues-with-Aginity-Pro-or-Team-Step-1>`_ for help with debugging your |var_product_name| connections.
.. image:: ../../Pro_Images/AginityProDBExplorerJDBC.png
:scale: 60
:align: center
:alt: Browse the Database Catalog
.. seealso::
* :ref:`Use Catalog Browser <usecat>`
* :ref:`Use Query Panel <querypanel>`
This diff is collapsed.
......@@ -336,7 +336,7 @@ Hit the **Import** button and your queries should be imported!
Aginity also maintains a Github repository of Catalog queries to be used. These queries are either administrative queries for specific platforms, data engineering queries that do powerful transformations against generic data or analytic queries showing how to do cool things in SQL.
Access the repositories `here<https://github.com/Aginity>`_
Access the repositories `here <https://github.com/Aginity>`_
.. seealso::
:ref:`Using Query Panel <querypanel>`
......@@ -61,13 +61,13 @@ Shortcut Key Reference
Frequently Asked Questions
=====================================
The table below are commonly asked questions that we compile and provide answers to. Over time as things change we will keep this table up to date.
The section below is dedicated to commonly asked questions that we compile and provide answers to. Over time as things change we will keep this table up to date.
.. csv-table::
:file: faq.csv
:header-rows: 1
:align: left
:widths: 45,45
What Control do I have with Row Limit Preference?
---------------------------------------------------
By default we cap the row limit preference to 100K rows to discourage users from spooling too much data across your network. Trust us your network infrastructure folks do appreciate it. Fear not though, you have options. First, if you set the preference to 0, it will spool as much as you want until either you run out of memory or your query completes. Alternatively, we recommend spooling the output to a file if you are doing returns greater than 100K rows. Refer to the documentation on :ref:`execute query to file. <exf>`
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment