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.
The weakest link seems to be the SQLite DB. Once the DB gets to 1GB size, the SC application becomes unstable.
Official support for MSSQL database instead of SQLite would make large on-prem deployments much more manageable.
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.
Please allow for Microsoft SQL Server as a supported database platform for CW Control
This is LONG overdue for a production product that many, many companies rely on for great remote connectivity to clients. Even if the first step is just ability to use MS SQL, this would be a huge improvement. Plus, it's not that it wouldn't work with it as the queries are almost identical (evidenced by the fact that other customers have switched to it). However, as it's not officially supported, we do not want to risk any potential "out of support" issues to switch until we know that the scenario will be supported, with updates as well. MS SQL Express supports 10GB databases at this point, so even if SQL licensing is too much a burden, this is a no cost option. Please at least give us the option of choosing the built-in SQLite or a MS SQL server at minimum. Thanks!
Also get this problem, have on prem unlimited licences but the database fills up quickly over time and cant cope. Periodically we need to manually purge data out of the session.db
Hi Rob,
What database maintenance plan do you currently have set up?
Thanks!
Hi Rob,
What database maintenance plan do you currently have set up?
Thanks!
Description | |
---|---|
Support: Delete ended sessions older than 1 day | |
Support: Delete Host and Guest connections older than 1 day | |
Support: Delete All Events events older than 1 day | |
Meeting: Delete ended sessions older than 1 day | |
Meeting: Delete Host and Guest connections older than 1 day | |
Meeting: Delete All Events events older than 1 day | |
Access: Delete ended sessions older than 1 day | |
Support: Delete Host and Guest connections older than 2 days | |
Access: Delete All Events events older than 1 day | |
Delete session captures older than 1 day | |
Compact database files | |
Delete session captures older than 30 days | |
Access: Delete All Events events older than 14 days | |
Support: Delete All Events events older than 2 days | |
Support: Delete ended sessions older than 1 day |
This needs to be added to the product asap. The current structure is unmanageable with more than 30,000 access sessions. Retention is already set to only a few days. When the db file gets to 2ish GB the web app completely crashes out.
I am very surprised as well that this has yet to be implemented. SQLite is just that lite. "SQLite emphasizes economy, efficiency, reliability, independence, and simplicity" to quote directly from the product page. It is not meant to scale to large data. Large data is meant for a RDBMS (relational database management system) that can reindex, defrag, etc.
Can SQLite do everything I have mentioned - sure and depending on memory (RAM) constraints, it can either do it well or as many have seen, crash hard. I would suggest that they makes this change. Otherwise there are always other RATs in the world (non-viral).
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.