Add support for MariaDB/MySQL or another DB engine for scalability
The weakest link seems to be the SQLite DB. Once the DB gets to 1GB size, the SC application becomes unstable.
Welcome to our community!
Duplicates 3
Actually Support MS SQL
MSSQL
Official support for MSSQL database instead of SQLite would make large on-prem deployments much more manageable.
Officially Support SQL Server
Right now MS SQL Server is not officially supported, but generally works with support in the forums. It would be nice to see full support for MS SQL including SQL Clustering and Always On HA.
Replies 46
This request has been open for 7 years. Is there any chance your going to enhance the product to support a real database engine, instead of SQL Lite?
I've found no information in the past to support this.
I found reference to MSSQL in some documentation somewhere and when I asked about it I was told "Oh that's not supposed to be in there, we'll get that cleaned up"
I've found no information in the past to support this.
I found reference to MSSQL in some documentation somewhere and when I asked about it I was told "Oh that's not supposed to be in there, we'll get that cleaned up"
Here you go!!
<system.data>
<dbproviderfactories>
<add name="SqlClient Data Provider" invariant="System.Data.SqlClient" description=".Net Framework Data Provider for SqlServer" type="System.Data.SqlClient.SqlClientFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
</add></dbproviderfactories>
</system.data>
<connectionstrings>
<add name="SessionDatabase" providername="System.Data.SqlClient" connectionstring="Persist Security Info=False; uid=<MSSQL USERNAME>; pwd=<MSSQL PASSWORD>; Data Source=<FQDN OR IP OF SERVER>; Initial Catalog=secureconnect; ">
</add></connectionstrings>
FYI, we've been using SQL Server for years with ScreenConnect. Mostly works splendidly. They don't provide much assistance if you call in, but it works.
It's a bit of wandering around the dark with a candle until you figure it out, but it ends up being 5 tables in a database (4 originally then recent updates added security.db and a new table that also has to be added). Once these are converted and the web.config is properly updated it works well.
We actively support 20 agents and aprox 2000 connections. Would LOVE this if it was a first-class citizen though.
When we piloted ScreenConnect several years ago, we worked with the SC team and installed using MS SQL Standard because of complications/limitations for our reporting and concurrent access needs with the built-in SQLite DB.
On two separate occasions, support has been utterly and completely useless in supporting the application because of the DB flavor. While I would not expect the support team to support the DB layer, I would still expect full support of the application.
Please either officially support MS SQL or provide reference architecture or whatever else is necessary so that it is a "supported configuration."
Given that we've been running it for going on 3 years, I wouldn't think much is necessary from a technical perspective.