Problem with MSSQL driver, the driver opens a dozen connections to the database. It is enough to just log in with the connection string and immediately in the SSMS Activity monitor you will see a dozen sessions started.
So far with C11 everything was ok. It is impossible to work like this, MSSQL Server slows down if there are more users and more databases on the server. For now I have stayed on C11.
I’m trying to report it on Problem Tracker, but there’s no option for C12 yet.
Prior versions of Clarion often had trouble maintaining connections, and one of the workarounds was to create a bunch of connections (100, IIRC) at program startup. These were just connections, not actually doing anything, and therefore didn’t strain the server in any way.
Perhaps C12 uses a similar approach to work around quirks in SQL Sever (and there are MANY quirks there). 
I understand what you want to say, but how can I explain to my clients that the application works at least twice as slowly. I tested the application made with C11 and C12 where nothing was changed in the code, the application made with C11 is incomparably fast and works perfectly.
Which version of the Microsoft ODBC client for SQL Server do you have installed?
These drivers are installed:
MESSAGE(Paramet{PROP:ConnectString})
Since I don’t know what clarion uses for connection. I put this line in the code after open files and got the answer DRIVER=ODBC Driver 17for SQL Server;SERVER=.......
I think then I’m using ODBC Driver and not Native. This is the connection string I’m using con=clip(clip(Glo:Server)&','&clip(MSBase)&','&clip(Glo:Name)&','&clip(Glo:Password))
While in the dictionary in the table properties:
Driver: MSSQL
Driver Options: /IGNORETRUNCATION=TRUE /LOGONSCREEN=FALSE
Owner Name: !con
Create,Threaded and Bindable are checked
Problem with MSSQL driver, cannot commit delete and app hangs up. There is lot of open transactions with SERIALIZABLE isolation level that locks transaction. I tried with SQL 10.50.4000 and SQL 15.0.2080. Tried also to change ISOLATION LEVEL with no result.