SQL server stuck using xojo web 1.0


I’m using some webservices (handlespecialurl…) to query a Sql server db

after some time, the sql service crashes or freezes. the customer says it depends from xojo.

Every ws does some queries on the db (no insert or updates, only select), and after each query I close the dataset and the db


any idea of what it can be?


Which version of SQL Server and which driver are you using?

I know Microsoft now recommends using their ODBC driver over their SQL Native Client.

They go as far as to say this:


The SQL Server Native Client (often abbreviated SNAC) has been removed from SQL Server 2022 (16.x) and SQL Server Management Studio 19 (SSMS). The SQL Server Native Client (SQLNCLI or SQLNCLI11) and the legacy Microsoft OLE DB Provider for SQL Server (SQLOLEDB) are not recommended for new application development.

Have you tried using ODBCDatabase instead of MSSQLServerDatabase, to see if that can help prevent the SQL Server service from freezing?

I noticed that (in SQLite and Desktop) mydb = Nil gave better resuls.

I hope this may help.

ok, I’ll try on SQL SERVER


I tried mydb=nil but still freezes the server

I’ve the webapp compiled as standalone (.exe) and registered as a windows service.
I don’t know if this could help.

Not sure if this will help, it solved some Web1 with MySQL issues for me. My Web1 app was built with Xojo 2019R3.2 (the latest version supporting Web1.) The problem is that the MySQL plugin that comes with the old version of Xojo isn’t fully compatible with current versions of MySQL. I was able to take the MySQL plugin from a newer version of Xojo, place it in the plugins folder of the old Xojo, and rebuild the app. So far this has worked well.

If you really are using SQL Server 2017 this shouldn’t be an issue, unless you’re on an older version of Xojo. SQL Server versions are confusing as multiple versions can be installed on a single server, and there are multiple versions of Management Studio that might also be present. Its easy to be confused about versions if you’re not a SQL Server expert (I’m not.)

As mentioned above, and confirmed by my own experiments, the ODBC plugin works best for Xojo with SQL Server. And if you replace an old plugin, make sure to keep a copy.