ODBC from Access to SQL Server

%3CLINGO-SUB%20id%3D%22lingo-sub-1341131%22%20slang%3D%22en-US%22%3EODBC%20from%20Access%20to%20SQL%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1341131%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EOur%20Access%20ODBC%20to%20SQL%20server%20used%20to%20take%2015%20minutes%20to%20do%20a%20re-query%20(query%20button%20allows%20for%204%20date%20ranges%20to%20be%20entered).%26nbsp%3B%20It%20seems%20after%20the%20recent%20updates%20in%20both%20Windows%20and%20MS%20Office%2C%20the%20re-query%20to%20the%20server%20now%20takes%203-4%20hours.%26nbsp%3B%20Our%20Access%20developer%20doesn't%20think%20it's%20and%20Access%20issue%2C%20but%20a%20SQL%20Server%20issue.%26nbsp%3B%20Can%20anybody%20offer%20suggestions%20as%20to%20why%20things%20changed%20all%20of%20a%20sudden%3F%26nbsp%3B%20Do%20we%20need%20to%20update%20anything%20in%20the%20SQL%20Server%3F%26nbsp%3B%20I%20believe%20we%20are%20running%20SSMS%202016.%26nbsp%3B%20Thanks%20in%20advance!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1346074%22%20slang%3D%22en-US%22%3ERe%3A%20ODBC%20from%20Access%20to%20SQL%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1346074%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20you%20calling%20Open%3F%20Or%20are%20you%20calling%20Requery%20with%20the%20changing%20parameter%20values%3F%20The%20query%20speed%20is%20significantly%20faster%20with%20the%20changing%20parameter%20values.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1347141%22%20slang%3D%22en-US%22%3ERe%3A%20ODBC%20from%20Access%20to%20SQL%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1347141%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F639138%22%20target%3D%22_blank%22%3E%40UVUKurtle%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20reply.%26nbsp%3B%20We%20re-query%20Access%20with%204%20different%20date%20parameters%2C%20each%20with%20a%20Start%20and%20End%20date%20field%2C%20so%208%20fields%20in%20total.%26nbsp%3B%20There%20are%20approx%2014%2C000%20records%20and%20230%20columns.%26nbsp%3B%20The%20re-query%20always%20took%20about%2015%20minutes%20(to%2Ffrom%20SQL%20server).%26nbsp%3B%20Did%20a%20re-query%20yesterday%20at%20end%20of%20day%2C%20it%20took%202.5%20hours%20to%20finish.%26nbsp%3B%20I%20installed%20the%20latest%20ODBC%20Driver%20(17.5)%20-%20released%20in%20March%202020%20on%20the%20client%20side%2C%20and%20my%20re-queries%20seem%20to%20run%20a%20bit%20faster%20than%20everyone%20else%20in%20the%20office%20(who%20are%20still%20running%20with%20previous%20driver%2C%20dated%202019).%26nbsp%3B%20I%20don't%20know%20much%20about%20SQL%2C%20but%20I'm%20wondering%20if%20SQL%20needs%20the%20same%20ODBC%20driver%20installed%20on%20that%20computer%3F%26nbsp%3B%20Thanks!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1348469%22%20slang%3D%22en-US%22%3ERe%3A%20ODBC%20from%20Access%20to%20SQL%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1348469%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F638662%22%20target%3D%22_blank%22%3E%40lyeomans2160%3C%2FA%3E%26nbsp%3BSo%20based%20off%20what%20you%20told%20me%2C%20I%20found%20two%20areas%20that%20could%20possibly%20help%20you%20out.%20Yes%2C%20absolutely%20try%20the%20new%20ODBC%20driver%20that%20you%20downloaded%20on%20a%20different%20client%20computer%2C%20which%20yielded%20great%20results.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETwo%3A%20I'm%20assuming%20you're%20operating%20on%20Windows%2010%3F%20I've%20read%20all%20sorts%20of%20performance%20issues%20expanding%20across%20many%20different%20pieces%20of%20software%20with%20the%20latest%20March%202020%20update.%20If%20the%20ODBC%20driver%20does%20not%20increase%20the%20performance%2C%20I'd%20try%20uninstalling%20the%20latest%20updates%20of%20Windows.%20Not%20sure%20if%20that's%20the%20case%20but%20it's%20worth%20a%20mention.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hello,

Our Access ODBC to SQL server used to take 15 minutes to do a re-query (query button allows for 4 date ranges to be entered).  It seems after the recent updates in both Windows and MS Office, the re-query to the server now takes 3-4 hours.  Our Access developer doesn't think it's and Access issue, but a SQL Server issue.  Can anybody offer suggestions as to why things changed all of a sudden?  Do we need to update anything in the SQL Server?  I believe we are running SSMS 2016.  Thanks in advance!

 

4 Replies

Are you calling Open? Or are you calling Requery with the changing parameter values? The query speed is significantly faster with the changing parameter values.

@UVUKurtle 

 

Hello,

 

Thanks for the reply.  We re-query Access with 4 different date parameters, each with a Start and End date field, so 8 fields in total.  There are approx 14,000 records and 230 columns.  The re-query always took about 15 minutes (to/from SQL server).  Did a re-query yesterday at end of day, it took 2.5 hours to finish.  I installed the latest ODBC Driver (17.5) - released in March 2020 on the client side, and my re-queries seem to run a bit faster than everyone else in the office (who are still running with previous driver, dated 2019).  I don't know much about SQL, but I'm wondering if SQL needs the same ODBC driver installed on that computer?  Thanks!!

@lyeomans2160 So based off what you told me, I found two areas that could possibly help you out. Yes, absolutely try the new ODBC driver that you downloaded on a different client computer, which yielded great results. 

 

Two: I'm assuming you're operating on Windows 10? I've read all sorts of performance issues expanding across many different pieces of software with the latest March 2020 update. If the ODBC driver does not increase the performance, I'd try uninstalling the latest updates of Windows. Not sure if that's the case but it's worth a mention.

@UVUKurtle 

Hello again,

 

Thank you for the suggestions.  I went over and had a look at the SQL server.  I discovered that Windows update attempt for SQL Server 2016 Service Pack 2 (kb4532097) failed to update.  

 

I also notice in the ODBC window that the driver version is SQL Server 17.  I know that 17.5 was released in March 2020.  So I'm thinking if I get the service update Pack 2 to successfully install, update the ODBC Driver to 17.5 and update all the Access client ODBC drivers to 17.5 version, maybe things will work like they are supposed to.

 

Do you think it's worth a shot?

 

Thanks again!