Is there plan to move from the legacy 2012 native sql client package to the current sql server odbc driver?

Hello,
Microsoft does no longer supports the native client that is required if xojo is building stuff that relies on MSSQL connectivity (source Support Policies - SQL Server Native Client | Microsoft Learn)
Microsoft offers a more modern package (Microsoft ODBC Driver for SQL Server - ODBC Driver for SQL Server | Microsoft Learn) that improves it on by:

  1. Supporting both local and azure based instances
  2. Supporting windows, linux and macos

Are there any plans to move xojo to the current supported runtime?

I’m not sure what kind of sign it is, but the 2022r4 release today omits the MS SQL database plugin.

obviously Xojo should support that… The fact it is no longer shipping an MS SQL server plugin is concerning
-Karen

Update: I’ve found the release note – they’ve just made it more work to get at I guess.

Oracle DB plugin is no longer copied to IDE Plugins folder by default. The MS SQL Server DB plugin is only copied to the IDE Plugins folder on Windows. All DB plugins are now available in Extras/Database Plugin Resources folder.

#70943 - Remove Oracle plugin from default plugins folder

Given that it looks like they now COULD create a plugin that works on the other platforms, they should…

I think the ERP we are getting is based on MS SQL Server and I’m on a Mac, so of course I think that! :wink:

-Karen

This is bad news for me, as I use that heavily in our business apps. Does this mean there is no upgrade path for Xojo users for their apps that utilize the MSSQL Server Plugin?

The MS SQL plugin has always been buggy, so long term might be good, but then Xojo has to provide the newer alternative.

The plugin is still available in the Extras folder. We used to use the ODBC plugin on Mac along with the Actual database drives to access MSSQL server from Mac. That seemed to work well.

It looks like MS is releasing an ODBC driver for other platforms. Either way you would have to switch to the ODBC plugin. Shouldn’t be too difficult.

1 Like

If it’s mission critical, check out the MBS plugins. They probably work better anyway.

4 Likes

The plugin still exists, somewhat hidden on new installs but, if you make mission critical apps and rely on microsoft premier, I’m expecting fat laughs when using the old SQLNCLI 11 with operating systems more modern than win8(native client is technically not supported on win8.1 let alone win10/11). I’ve made the thread since we have more and more unattended install failures for the native client on current systems, requiring manual intervention, something that the new odbc driver seems not to have.

1 Like

Yes, but the new driver is ODBC and Xojo already has an ODBC plugin. You should be able to use it right away.

To be clear the ODBC plugin for Xojo provides the database end of their transaction for any database that has an ODBC driver. Since Microsoft are now providing the drives for all platforms you should be able to just download, configure and use it.

The connection strings should change, but the rest should be fairly similar. Unless the cursor properties are different.

At least on the few machines i tested my database-bound apps on, i will get a clear error indicating that sqlncli is not present if i attempt to connect to a mssql database on a machine that has only the new driver installed. Maybe there is some hardcoded reference to sqlncli.dll ?

Edit: just tested it now for you. On my laptop, which has the new odbc driver v18 and not native client, i get an explicit “SQL Native Client not installed” error when i execute a db connection. It’s hardcoded.

You would have to use the ODBC plugin not the SQLServer one.

I’ve been using the Xojo ODBC plugin to connect to MS SQL Server. In the last several years it seems to work better than the SQL Server plugin. These apps run on Windows only, haven’t tried it on Mac or Linux.

As I said we used it on Mac, but back in the day we had to buy the “Actual SQLServer driver” as MS didn’t at that time provide one. We had no problems with that. ps. Actual is the name of a company.

We used to use ODBC Driver for SQL Server on Linux. We have not had any problems lately.