A family of Microsoft relational database management systems designed for ease of use.
Flagging for weekend review. Thanks for the bump.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have an mdb application which uses a DSN-less connection to link to tables in SQL Server 2016. The app has been getting more and more frequent hangs. Looking at the server logs, it shows that every time the app needs to access data on the server it is logging on again and not maintaining a persistent connection.
I did some searching, and I cannot find a switch with the ODBC to make it a persistent connection. I am using NCLI11 with the ODBC. I have tried opening a hidden bound table as was suggested by some sites but that did not seem to have any effect.
As it is currently, each user is registering logon events thousands of times a day. How can I create the persistent connection to the back-end SQL database so Access will hold that connection open?
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Flagging for weekend review. Thanks for the bump.
Flagging for weekend review. Thanks for the bump.
Bumping thread.
Server is on-prem, connection is utilizing windows authentication with an active directory domain.
I am seeing the logon events by opening SSMS, going to Management, SQL Server Logs, and looking at the logs. For yesterday (12-12-2017) it recorded 397,291 logon events.
I'm interested in this issue.
> Looking at the server logs
Can you please be more explicit? Where are you seeing many logon events?
Also:
* Is this using SQL Server on-prem?
* Windows Authentication or SQL Server Authentication?