We have an application that wraps around the Sage 100 data base using the Sage 100/Providex 64-bit ODBC driver as a linked server to an instance of MS SQL Server 2014 Express 64-bit.  Various views are then defined against the S100 tables in the SQL Server instance which are then in turn queried via different parts of the application.  Sometimes over night or over the weekend when there is a period of no activity in either our application or S100 the S100 ODBC driver appears to go to sleep as a request just hangs with no I/O or CPU being registered in the Windows Resource Monitor tool.  The only way to recover the link is to restart the SQL Server instance.  Is there a log, trace file, or other debugging data that could be enabled or viewed to determine the cause of this hang?