SQL Statement lenght limits for SQL Server Native Client and ODBC Driver for odbc
Hi, I have an application that use SQL Server from 2012 to 2022. It executes SQL Statements with up to 88.000 characters With SQL Server Native Client 2012 it works, however with ODBC Driver 18 for SQL Server it doesn't, ODBC limit the SQL Statement up to 65000 characters, I noticed this in SQL Profiler I will need ODBC Driver for SQL because SQL Native Client doesn't support sql server 2022 I don't know if there is a solution to this issue I'm using DELPHI and FireDAC for the development and I don’t need create a DNS to connect the application to the database, I set the necessary params to FireDAC so it does the connection thanks for your suppor
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?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.
Access with SharePoint List link - ODBC
Hi all, I needed to get some of the SharePoint List data into Python, Matlab etc. As there were no dedicated connectors that would also combine well with SSO, I used ODBC to create a connection with Access DB. In this Access DB I linked the SharePoint list. It allows me to use basic SQL on sharepoint data from the code. That works reasonably well when it comes to running Select and Delete queries. However when it comes to Inserts it has encountered an issue when a duplicate record is added to a unique column. This breaks the linked connection in Access Db. To restore it I need to open Access Db and resolve the conflicts there or refresh the SharePoint link. Is there any way to do through some command without opening the Access Db?Problem to migrate simple Access mde app and Microsoft Sql Database to another PC
Hello there, Im struggling to move an old Access app, which runs on a windows server 2003, to my Windows 10 PC, The app is run from the Server desktop via mde file and is connected to a microsoft SQLEXPRESS database installed locally on the server, I installed locally on my pc windows 10 Microsoft Sql express, and changed the hostname of my PC setting "SERVER". I can access the tables and the database seems to work, but when I launch the "example.mde" file from my computer the application fails and cannot find the database asking me for the path.. if i click continue with trusted authentication it ask me again for every move i make .. I don't know how to specify the data source or connection string for the database on the new machine, I believe this is about the ODBC driver, attached the error I get. https://i.stack.imgur.com/ZWzme.png Thanks in advance for the helpSQL 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?
