Reputation: 1
I'm admittedly fairly new at SQL and learning organically through project requests and reviewing my predecessor's previous processes. One issue I am encountering is the once-per-year password reset rules my company has in place. All current queries have a Database schema being referenced (6 potential options depending on the query, most referencing the same user and password), and hard-coded user login information. So once per year, every single query has to be changed to the updated encrypted password.
I have been testing a login sql file that AQT references prior to running the query, allowing it to login to the necessary database for the data. The goal is to only have to change the password in 5 or 6 places instead of 300 since I was unsuccessful in being omitted from the reset rules. We use AQT v10 if that helps. All of our queries are run via Windows Task Scheduler on a virtual Windows 10 machine.
I am able to get the login sql file to work properly, and the query to run and export the data to the correct csv. The issue I am encountering is the task realizing the end of the query and closing AQT all together. Most of our processes are individual queries run in order to compile the data required for whatever the task is at hand. So with AQT remaining open, the machine does not know to begin the next step of the task.
Below is the link that helped point toward the login sql file and 'include' in the initial scripting of the query https://www.querytool.com/help/329.htm
Autorun with AQT remaining open
Thanks! Andy
Upvotes: 0
Views: 55