Change odbc timeout10/31/2023 ![]() ![]() Change the path as needed.ī) If LS points to a connect string in Provider String field, then after the last semi-colon add LogFile=C:\Temp\PVXODBC. In Remote Query Timeout change it to your desired value or specify 0 to set no limit. In the new tab, click on Connections node. In Object Explorer, right-click on the server name and then select Properties. If LS points to a DSN in Data Source field, then in 64-bit ODBC Administrator on Tracing tab you can click the box to ODBC trace.Ī) If LS points to a DSN in Data Source field, then in System DSN tab where presumably your (silent connect) DSN lives, go to the Debug tab and click Enable Debug. Connect to MS SQL server via SQL Management Studio. Here are 2 ways to do logging but I don't think either will help you troubleshoot and both will slow you down: Click the App Servers icon on the left tree menu. Click the group in which you want to define the ODBC server (for example, Default). You can see this thru Ctrl Panel / Power / Advanced ("turn off hard drives after xxx min/hrs" and similar settings) and Ctrl Panel / Network / adapter properties / Power Mgmt tab. To create a new server, complete the following steps: Click the Groups icon in the left tree menu. Depending on how you setup the LS this change is done either in the DSN you setup of the 64-bit ODBC Administrator or in the Provider String of the LS.Īnother possibility and I've run into this several times is your SQL Express machine has a power saver kicking in after a period of inactivity. Is Sage server on a different box / VM than SQL Express? If so, in the Linked Server (LS) are you connected to the \mas90 folder via mapped drive? Mapped drives are known to timeout after inactivity so UNC path could be better. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |