Here is the offer.
- Install ArcSQL.
- Let it run for a week or more, the longer the better.
- Export the SQL_LOG table to a spreadsheet.
- Send me the spreadsheet.
I will then analyze the results and send you a personal screen-cast letting you know what I find.
What’s the catch?
No catch. I need random data sets to make improvements and I make some connections.
Offer runs until Jan. 31, 2019. A good chance I will extend or make other offers. This date will move as needed.
The install instructions (there is a video) and more details on the offer (also in the same video) are easy to find in the description for the ArcSQL project here.
In this post I want to show you how I maintain my uninstall script for ArcSQL. You can do the same with your database based applications.
The system is simple. The arcsql_schema.sql file contains most of the objects that are created. I add a special comment called “– uninstall:” with the command to drop the object I am creating. See the image below.
The build_arcsql.sh script greps those lines out and puts them into uninstall_arcsql.sql. Uninstalling my application is as easy as running the script.
Maintaining a separate uninstall file is tedious and error prone. By keeping each drop statement as close to the creation code as possible I make my life easy.
You can see the current version of the code here.
Do you like these tips?
You can support me and ArcSQL by letting people know about me. I provide consulting expertise in the automation, monitoring, and data visualization space. I am always looking for interesting projects to work on.