This is an overview video of Aqua Data Studio’s SQL History and SQL Archive feature. The SQL History window is found under the Query main menu, and it’s also an icon on the main toolbar represented here as well. You can launch the SQL history by clicking on this icon in the main toolbar or Query SQL history. The SQL History and Archive window is one of the most powerful features within Aquadata Studio where you can see a history of any SQL statements that you have executed. There are some settings at the top that influence the number of statements that are saved and when they are archived. Here you can see I’ve increased my history to 100 and the max number of statements per entry is 100. That means after I execute my 101st statement, that statement would become archived in the sequel archive. Let’s execute some SQL statements and then revisit the SQL history window.
If I open up a query analyzer and just start typing the SQL statement, I have some of the Intel Sense capabilities. Let me select a table and execute that SQL statement. Now if I visit the SQL history under Query SQL History, I can see that statement that I just executed. There are a number of other columns displayed as well as the SQL statement column. I can see the date, start and end time, the database platform, even more details on the number of rows selected the database. Also, what window within Aquadata Studio that SQL statement was executed? There’s also some other settings here within the main toolbar such as the Preview sequel that can be very helpful or beneficial. Let’s go back to the query analyzer and execute another statement or bring in another SQL statement just to see that history start to build. Again I can choose one or multiple tables from some of my pop up windows and then execute one or multiple statements and revisit the SQL history.
Okay, so here I can execute an individual SQL statement or multiple SQL statements. Now when we visit the SQL history, I can see that history being built for me. As I mentioned, the number of SQL statements that are saved and the setting there influences that. The archive allows me to form a history where I dan search previous saved sequel statements. Here are my current statements in that numbered setting. If I go to the SQL archive, this is a directory that is saving these statements, these archive statements. Here I have some search capabilities where I could search on, say, a keyword and see any database that had a sequel statement with that keyword. Or I could use say, a start and end time. This really allows you to keep an unlimited history of SQL statements. You can see thousands and thousands of statements have executed over time.
There are other settings here that allow you to manage this. You can select a sequel statement and that would bring that right into the query analyzer for you. Depending on where you left your cursor, you have that capability here. Here I could just select a statement and bring that back into my sequel history. Execute an individual statement here. If I was in, say, some different environments, it had the ability to open up one or multiple SQL statements from SQL history. I could multi, select and bring in multiple statements to my SQL history, or just double click and bring all the statements from a single script into my SQL history. There’s other settings that would be helpful for you. Here you have the ability to compare two different SQL statements, so that might be helpful for you where here let me select, say, a SQL statement from different environments.
Compare SQL Statements
Now I have the ability to do a copy, compare and do a side by side comparison of two different SQL statements. So, lots of benefits here in terms of keeping track of the SQL history, allowing you to preview previously executed SQL, and then the location of these are found in the file options where here I can drill into the general history and see where those are being saved to. The archive folder, but those are customizable and even shareable if you have other colleagues that need access to the same shared SQL statement directory. Thank you for joining this overview video of Aquadata studio SQL History and SQL Archive.