+ New Ticket

How can I open a standard sql file in Agenity Pro?



  • Official comment
    Sergey Polshvedkin

    Hello Lazloo,


    This feature is slotted in a development queue.

    Forecast for it - is the end of September.


    Right now you can copy text and paste into query editor.





    Comment actions Permalink
  • Avatar
    Sergey D

    Aginity Developers, please, refer this post:

    Invest effort into Github integration. 


    Comment actions Permalink
  • Avatar
    Sergey Polshvedkin

    Hi Sergey,

    We appreciate your time and comments.

    Our engineering team has some ideas and tickets related to integration with GitHub (already in backlog).

    Not sure if it appears soon but will see how it goes.


    Comment actions Permalink
  • Avatar
    Eric M

    Want to add my vote to this functionality. I am a data engineer that builds/maintains many Data Lake and Data Mart databases. The SQL that builds an individual table is contained in it's own .sql file. With no ability to open/edit that file there is no way for us to utilize this tool.

    The process would have to be a combination of copying the code to an aginity pro tab for running/testing, then modifying the actual file in a text editor. This workflow is not manageable.

    And speaking frankly, this gap in functionality makes using aginity pro a non-starter for us.

    Comment actions Permalink
  • Avatar
    George L'Heureux

    Hi Eric,

    Thanks for making your voice heard - we're glad you're part of the Aginity community.

    First thing first - we hope that this functionality will be present in a very near-future release, perhaps even our next one around 11/11. Hang tight!

    Next thing I'd like to mention, though, is that our Aginity Catalog does allow you to save your work into catalog items and open and edit them inside the tool. There's no need to extract the SQL to another tool for editing - you can edit it within Aginity Pro and save it to your personal catalog, then run it later with just a few clicks.

    Additionally, because of the way the Aginity Catalog stores not just SQL files and scripts, but smaller snippets too, you can isolate the parts of your script that change, parameterize them, and use them as building blocks for other catalog items, so that you can edit just the part of the script that's going to change, and leave the rest untouched.

    I'm shooting you a private message with an offer to walk you through that workflow one-on-one.

    George from Aginity

    Comment actions Permalink

Please sign in to leave a comment.