Commit fe0bf6bd authored by Jeffrey Schlitt's avatar Jeffrey Schlitt

Added import export doc

parent 03ec9942
Redshift,Hive,Netezza,Snowflake,Greenplum,Aginity Enterprise
Databases,Databases,Databases,Databases,Databases,Workspaces
Tables, Tables, Tables,Warehouses,Schemas,Projects
Views, Views, Views,Tables,Tables,Tables (Sources)
Users,,,Views,Views,Views (Notebooks or Views)
Groups,,,Scalar Functions,Columns,Columns
Libraries,,,Roles,Users,
,,,,Groups,
,,,,Functions,
,,,,Aggregates,
,,,,Operators,
,,,,Primary Keys,
,,,,Foreign Keys,
,,,,Partitions,
,,,,External Tables,
,,,,Sequences,
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
......@@ -32,12 +32,20 @@ Once you have selected the **Database Explorer** tab you can drill into each con
:align: center
:alt: Browse the Database Catalog
The following table will detail what objects are visible from the browser for each database connection type.
The following table(s) will detail what objects are visible from the browser for Redshift, Netezza, Snowflake, Hive, Greenplum and Postgres.
.. csv-table::
:file: db_capabilities.csv
:header-rows: 1
:align: center
.. csv-table::
:file: db_capabilities.csv
:header-rows: 1
:align: left
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
......
......@@ -276,8 +276,67 @@ When adding a new folder you will be presented with a basic text box to create y
Import and Export Items from Catalog
===========================================
**Coming Soon**
You have the ability to Import and Export both your full catalog as well as any folder selected within the catalog.
.. note::
We highly recommend taking regular exports of your catalog to disk to prevent accidental loss of queries.
Export Steps
----------------
To Export your catalog start by either **Right Clicking** on a Catalog Folder or Using the Aginity Pro -> Export Catalog menu as shown below.
.. image:: ../../Pro_Images/AginityPro-ExportMenu.png
:scale: 60
:align: center
:alt: ExportMenu
Your first step is to save either an entire folder or a selection of items within a folder.
.. image:: ../../Pro_Images/AginityPro-ExportItems.png
:scale: 60
:align: center
:alt: ExportMenu
The final step in exporting is to name the file and location you will save to as shown below.
.. image:: ../../Pro_Images/AginityPro-ExportDirectory.png
:scale: 60
:align: center
:alt: ExportMenu
Import Steps
--------------
Importing is valuable for several reasons. One is to restore SQL catalog items you may have lost or more importantly the ability to collaborate with other SQL developers and share your SQL making your a more efficient and consistent SQL developer.
The first step is to **Right Click** on a folder you want to import to and Chooose Import Catalog as shown below.
.. image:: ../../Pro_Images/AginityPro-ImportRightClick.png
:scale: 60
:align: center
:alt: ExportMenu
.. note::
You can also use the Aginity Pro Menu -> Import Catalog. The main difference between using these two capabilities is the context of where you are importing items. If you choose to import from the Aginity Pro menu you must set the context where to import. If you **Right Click** on a folder the context is set to that folder.
After choosing to import you will choose the file to import. By default Aginity catalog files have the extension **.aginitypkg**.
After choosing your file you can specify the folder to import to and what to import as shown below.
.. image:: ../../Pro_Images/AginityPro-ImportFolders.png
:scale: 60
:align: center
:alt: ExportMenu
Hit the **Import** button and your queries should be imported!
.. seealso::
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>`_
.. seealso::
:ref:`Using Query Panel <querypanel>`
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