It’s probably no surprise to you that a large portion of algorithms developed today are done in SQL. And SQL is not going away no matter how much others try to kill it off. In the last decade there have been attempts to push the market towards NoSQL platforms, data science notebooks, etc. Yet SQL seems to be coming back even stronger as more modern distributed cloud database come to the market. SQL is stronger than ever as a language for analysis.
The algorithms that we create today are typically saved to individual files or on our desktop. We recreate them each time, unless we can hunt down some code saved—who knows where—on our desktop, in email, shared files, and so-on. And who’s to say that code is up-to-date with any standard business rules/definitions. Very little reuse of algorithms, if any, takes place today since there is no “place” nor way we can “trust” prior work. Instead we waste tons of time building it from scratch causing a lot of inconsistencies and overall loss of analytic knowledge across the organization.
We need to be able to easily find our code and put it into action without all this extra work. Treating SQL as object-oriented allows us to build algorithms on standardized code snippets. These code snippets can be parameterized, giving us more flexibility and consistency in reuse.
This motivated us to build new products that allow individuals and teams to easily reuse and collaborate on their SQL code.
We love Workbench. But….
We love Workbench very much. There has been a lot of Community love expressed for Workbench, and we certainly understand the attachment. As much as we love Workbench, it is not able to truly meet the demands of what is needed for the analytic movement. The underlying technology is getting outdated, limiting our innovation, and it has accumulated a lot of technical debt. This makes doing something—even the simplest things—far costlier than they should be. So, we needed to build you the next-generation SQL analysis tool, Aginity Pro.
Bringing enterprise capabilities to individuals
To give analytics the love it deserves, we’ve created a new way to treat individual analytics as assets. Weaving together our experience in building of the best SQL IDE’s on the market and analytic management tools for large enterprise, we give you Aginity Pro.
As analytic developers, and more specifically SQL developers, we need to start thinking like software developers in the way they treat their IP.
- To have a shared repository
- Capabilities of composability (libraries, object-oriented characteristics, etc.)
- Lifecycle management
- CI/CD capabilities
The software industry has long used these practices and it’s time to begin embracing them as SQL developers.
Right now, in Aginity Pro this is being established using the Catalog, an Active Catalog. You can save SQL code—snippets, whole SQL statements, multi-step SQL scripts, etc. —for reuse in different ways. Once in the Catalog, you can reference it as an object in your SQL or have it quickly expanded. Check out this 2-minute video showing this reference capability.
This “Active Catalog” feature still young, but the backlog and roadmap are quite robust. There is lots more to the vision and roadmap than just the Catalog.
Aginity Pro, along with a soon-to-be coming Aginity Team, is in the early days of bringing all that to life. We are working tirelessly to bring all the enhancements to market as fast as possible. We are moving fast and releasing updates to the software every two weeks.
We want to collaborate with you as we continue to build out Aginity Pro and Aginity Team. If you have special feature request, drop us a line at firstname.lastname@example.org.
Stay tuned and watch how, together, we can change the way people think about and treat their SQL code, giving analytics the love that it deserves.