ODBC from Access to SQL Server database - query timeout expired
I am having issues connecting to a database located on a SQL Server 2022. When creating the connection all test gives OK. But when trying to connect, it fails with: ODBC--call failed "Query timeout expired" If I don't define the database, then Access connects to master db and lists the tables that I can access. So it seems the connection to the server itself is ok. Tried ODBC SQL server driver, SQL Server 17 and 18 odbc driver, all same results. Same database on SQL Server 2014 also does not work for my user, but another user has previously been able to connect to old database, but seems something is missing either client-side or server option in the new setup?
SQL Server 2012 Native Client
Microsoft SQL Server 2012 Native Client is being flagged an obsolete software and will stop receiving security updates starting July 12th, but I have done a lot of searching on the internet and getting a mixed results on whether this is true or not. So I figured I would ask here to see if anyone else is dealing with this situation and what conclusion can be made here. For example, Microsoft has a blog post regarding the software that says the software is obsolete on July 12th, which can be seen here: https://techcommunity.microsoft.com/t5/sql-server-blog/snac-lifecycle-explained/ba-p/385381 However, I have been told that there is an exception to the rule that says it is supported "in SQL Server 2012 through 2019 until their respective end-of-support lifecycles", described at the bottom here: https://docs.microsoft.com/en-us/sql/relational-databases/native-client/applications/support-policies-for-sql-server-native-client?view=sql-server-ver16 So I guess my ultimate question is: Will "SQL Server 2012 Native Client" still receive security updates post July 12th of this year?Lesson Learned #371: Playing with the ODBC tracing file: connecting to the database
A few days ago, I encountered a case where our customer asked about the process of reading and reviewing all the ODBC traces generated by their application. In this example, I would like to share the lessons I learned while connecting to the database.
“Operating system is not presently configured” error with Access ODBC
I get the following error when I try to connect to Microsoft Access Database via Python. The code has been working all this time and only started popping the error today. Can someone please guide me what may be the problem occurring now? I tried doing this https://stackoverflow.com/questions/63899661/operating-system-is-not-presently-configured-error-with-access-odbc even after removing the “Office 16 Click-to-Run Extensibility Component 64-bit Registration” my problem isn't getting solved. import pyodbc as pyo import os #print(pyo.drivers()) filename='//MCISERVER1/TestData/access/Proof.mdb' full_file=os.path.abspath(os.path.join('data',filename)) print("opening access") Driver='{Microsoft Access Driver (*.mdb, *.accdb)}' access_driver=['MS Access Database'] try: cnn=pyo.connect(driver=Driver,dbq=full_file,autocommit=True) except pyodbc.Error as ex: print("Error connecting") cursor=cnn.cursor() sql="select * from [ERT ITRON] as e where e.SO='7888'" cursor.execute(sql) for row in cursor.fetchall(): print(row) print("success") cursor.close() cnn.close() print("connection closed")
ODBC cannot set by command line
Oracle x86 is installed in a x64 window 10 system, but cannot set as below. Error screen shots as attached . Used 32-bit and 64-bit odbcconf.exe are also failed. C:\Windows\SysWOW64\odbcconf.exe ODBCCONF CONFIGSYSDSN "Oracle in OraClient11g_home1" "DSN=xxx|SERVER=xxx" odbcconf.exe /A {CONFIGSYSDSN "Oracle in OraClient11g_home1" "DSN=xxx;SERVER=xxx"}
