This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 66%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
What is the best way to script to achieve the following on the client Windows 10 computer at a scheduled set time (Windows Task)...
To detect specific ODBC connection, if opens, close it.
batch file or console app?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
Powershell would be my choice. But I'm curious what you mean by a specific ODBC connection as that is per process. So you wouldn't see it from another process unless you were doing this from a database server and querying the database itself. In that case it would depend upon your DB.
"specific ODBC" is restricted on this type of connection only on the client computer. The problem is the SAS users connecting to the SQL database with the specific SAS ODBC connection and not closing the SAS app overnight ie SAS ODBC, connection , as a result the SQL database is locked by the SAS ODBC connection and SQL database is failed in a scheduled refresh.I can't implement anything on the server side for reasons and need a solution on the client's computer.
You're not going to be able to solve it on the client side unless you own the code that is doing it. Connections are per process and your process cannot see another process'es connections. Even if it could it would have no way of knowing what is going on.
Traditionally I've seen this problem solved by writing a SQL script on the server that drops sessions that are inactive. This would be the workaround (as only it knows which connections there really are) until the problem code is fixed.
Yes, I am thinking to have a batch file or a console app that all SAS users to execute it at a set time which is scheduled daily in the Windows Task Scheduler on their Windows 10 workstation. By the way, all SAS users have the same naming on the SAS ODBC connection to the SQL server. Thanks.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 23%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
You can try ODBC Test Connection Using PowerShell or, using a DQY File.
https://blog.devart.com/4-ways-to-test-an-odbc-connection.html