Applications using Hyper Server become slow when there are more than 200 sessions

[Wilton Ergon]

I was having random problems with losing connection with the SQL server 2019, and I used MSOLEDB 18 to connect, I updated to the latest version of MSOLEDB 19.3.2, and these problems stopped.

I have more than 2000 k of simultaneous connections without performance problems.
see that if you use FIREDAC it may not use MSOLEDB to connect but ODBC

I use SDAC.

https://learn.microsoft.com/pt-br/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver16

[Muhammad Idris]

3 hours ago, Wilton Ergon said:

I was having random problems with losing connection with the SQL server 2019, and I used MSOLEDB 18 to connect, I updated to the latest version of MSOLEDB 19.3.2, and these problems stopped.

I have more than 2000 k of simultaneous connections without performance problems.
see that if you use FIREDAC it may not use MSOLEDB to connect but ODBC

I use SDAC.

https://learn.microsoft.com/pt-br/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver16

Is MSOLEDB 19.3.2 installed on the database server or client side on the web server?

and I use ADOConnection to connect to SQL Server

[Abaksoft]

On 12/9/2023 at 8:41 AM, Muhammad Idris said:

Is MSOLEDB 19.3.2 installed on the database server or client side on the web server?

and I use ADOConnection to connect to SQL Server

Muhammed,

Avoid AdoConection (old technology)

Use instead Devart components.

They are much faster, stable and scalable. You have also pooling propertie for absorbing many open / close connections.

- If you develop only with sqlServer then buy Sdac component 

- If you develop with many RDBM, buy Unidac.

Advise :

Unidac has a global connection, but not specific to each rdbm. Sdac is more accurate and designed for SqlServer.

https://www.devart.com/

[Wilton Ergon]

On 09/12/2023 at 04:41, Muhammad Idris said:

O MSOLEDB 19.3.2 está instalado no servidor de banco de dados ou no lado do cliente no servidor web?

e eu uso ADOConnection para conectar ao SQL Server

If you use unigui, just install it on the bank's server, and on your application servers, if you have several servers.
As the friend said ADOConnection, it is outdated, but you can try changing a connection string, to use MSOLEDB, this would avoid changing components for now.

https://www.connectionstrings.com/ole-db-driver-for-sql-server/

 

 

An important detail is that UNIDAC has a conversion tool, so you can migrate from ADOCONNECTION to UNIDAC in a few minutes.

[Wilton Ergon]

On 10/12/2023 at 05:24, Abaksoft said:

Maomé,

Evite AdoConection (tecnologia antiga)

Em vez disso, use componentes Devart .

Eles são muito mais rápidos, estáveis e escaláveis. Você também tem propriedade de pooling para absorver muitas conexões abertas/fechadas.

- Se você desenvolve apenas com sqlServer então compre o componente Sdac 

- Se você desenvolve com muitos RDBM, compre Unidac.

Conselho :

O Unidac possui uma conexão global, mas não específica para cada rdbm. Sdac é mais preciso e projetado para SqlServer.

https://www.devart.com/

I believe that UNIDAC uses the same access engine as SDAC to connect to the sql server, because it does not accept that you have an old version of SDAC, and a new version of UNIDAC installed, as it would generate a conflict in the use of the files

[Abaksoft]

8 hours ago, Wilton Ergon said:

I believe that UNIDAC uses the same access engine as SDAC to connect to the sql server.

Yes.

But for a specific use like backup/restore or other funtionality SDAC is well designed for sqlServer.

https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://forums.devart.com/viewtopic.php%3Ft%3D34699%23:~:text%3DUniDAC%20allows%20working%20with%20a,prices%20were%20made%20the%20same.&ved=2ahUKEwiFnsTwnIiDAxVQUqQEHSjeBY8QFnoECA0QBQ&usg=AOvVaw02z76CrctcIgZ9baYuIGBy

 

The same for IBDAC :

https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://forums.devart.com/viewtopic.php%3Ft%3D54310&ved=2ahUKEwi5qM-FnoiDAxVxX_EDHdlqAtwQFnoECBoQAQ&usg=AOvVaw2ZXw7sVXUw8SBZ_fXUoewD

[Wilton Ergon]

I'm referring to access to the database, unit uses the same units as sdac, so it will have the same performance, the difference is in specific resources

---
To access SQL Server, UniDAC uses the same main modules that are used in SDAC. However, UniDAC has no support for some specific SQL Server features, that are supported in SDAC:

- ServiceBroker;
- ChangeNotification;
- the NonBlocking mode, in which an SQL query is executed in a separate thread;
- data types: geometry, geography, hierarchyid, and xml

Therefore, if you don't plan to use SDAC specific features, there is no difference between using SDAC and UniDAC.