Officially, AugSQL is still in beta, but there are over 20 people in the beta program at this point and AugSQL has been working smoothly.
Before we launch officially and drop “beta” from the description, we will be introducing a feature that allows you to control what users in Acumatica are able to use AugSQL. But the security will be done here on AugForums.com so it can’t be circumvented within Acumatica. This will allow VARs to put AugSQL in a Customer environment without worrying about the Customer doing bad stuff with SQL. It will also allow Customers to put AugSQL in their environment without worrying about their VAR doing bad stuff with SQL 😀
In the meantime, you’re welcome to join the beta program using the button below. You can also checkout the videos below to learn more about AugSQL.
Here are 3 blog posts about AugSQL:
acuCONNECT 2024 – Creative SQL Views for Reporting in Acumatica
September 13, 2024
Why Reporting is Better with SQL in Acumatica
July 17, 2024
acuCONNECT 2023 – Acumatica SQL View Examples with Generic Inquiries
September 14, 2024
Here’s the recording from the AugSQL Beta Launch Webinar
(demo included) on
Thursday, July 06 2023 @ 04:00pm Eastern Time
And here’s a short demo video
Got questions or comments about AugSQL?
Please ask them below, just make sure that you login first.
Can you write SQL insert and delete statements into AUGSQL?
Yes, you can write Insert and Delete statements in AugSQL.
My license anniversary is approaching. How will we renew?
We are using AUGSQL but have an issue with getting “406” errors. Basically any time we try to do an aggregate or Group query, and when doing “*” queries that contain any further clauses (i.e. Select * from Customer WHERE CustomerID=’2′ throws “ErrorCode: 406”. Any tips for this? I can define which columns I want and it works, but sometimes I just want the whole table but filtered by SQL. Also, Anytime I put in a “MAX” or “SUM” or “AVG” etc. it throws the same error.
Mark, even though I’m working through this with Mike on your team via email, I’ll post the solution in the AugSQL Forum at AugForums.com/AugSQLForum (currently only available to customers) once we have it figured out. So far, we’re trying to reproduce it since I’m able to run the same queries in my local build (same build number) without any errors, but Mike gets errors in your environment. The current theory is that it might have something to do with the other Customization Projects that are published in your environment.
How do I download the AUGsql Software?
Hi Mark,
If you go into My Info -> My Courses, then go into the AugSQL course, you will see that there are several lessons to go through, including a lesson on downloading the AugSQL Customization project and how to install it.
Tim, this is great. One has to be very cautious. I would definitely take a snapshot of the tenant or a SQL DB backup if customizations would be impacted by the AUGSQL commands. AUGSQL is a must if one wants to show data across tenants. Correct?
Thanks again for this and for a very clear presentation.
Toon Six
Ya, I definitely wouldn’t recommend AugSQL for tons of UPDATEs because of the potential for data corruption. The main use case is reporting.
And yes, you can use AugSQL to do consolidated reporting across Tenants.
Can we use AugSQL in our sandboxes?
Yes you can! The license only kicks in when you try to use AugSQL in an Instance that has a licensed Tenant in it.
If you’re using AugSQL in a licensed Acumatica environment and you haven’t registered the Installation ID in the AugSQL Course, then, when you press a button on the AugSQL screen, you’ll get a pop-up that looks like this:
Regarding which versions of Acumatica are supported, we haven’t tested to see how far back AugSQL works, but it likely works going back many Acumatica versions.
As far as the versions of Acumatica that we are actively supporting, we are supporting whatever versions that Acumatica is currently supporting. At the moment, that includes the following versions: