Remove limitations on number of projects/databases/etc
Why are there limitations on number of projects? We have dozens!!!

The latest release 1.6.2 of DLM Dashboard now supports up to 50 database,
Note: Previous status update was an error.
-
Scott Paist commented
Why does this limitation exist? And why no comments since 2016? Is this product dead?
-
Prakash commented
I have prefered to take Idera product of Auditing that has no limitation.
-
Dave McClung commented
Is there any update on this. Support for greater than 250 databases or limitations completely removed?
-
Daniel Wilson commented
We have over 300 databases spread across dozens of servers. We really need a tool like this, but the 50 database limit is a killer for us. We would pay for a version that removes this restriction.
-
Dave McClung commented
When will this restriction be lifted completely or at the very least raised to the 250 - 300 mark? Currently this along with the top feature request of moving the stored procs to your own database instead of master are the primary things holding our company back from installing this to monitor production environments and purchasing some toolbelts.
-
Kevin commented
-
[Deleted User] commented
the limit of 10 databases per instance (in an optimal configuration using alert notifications) makes it hard to fully utilize this tool.
-
Christian Cobas commented
We need to monitor at least 50 databases in DEV enviroment.
-
Toby commented
I can't use the beta either, I'd like to monitor drift for 50 catalogs from a common model catalog.
-
Damien commented
This restriction has made the BETA almost untestable. I understand you will probably want companies to pay for this application when out of BETA, but surely you could just time bomb the app to solve that problem?
-
Rad! commented
I think you should remove this restriction altogether, or at least raise it to something like 25
-
Samuel Jones commented
I'm running into the 5 project limit. Each person on the DBA team manages dozens of projects!
-
Anonymous commented
Limitation to only 4 databases per environment will not work for us. I understand limiting while in beta...please remove it for released version. If release version only provides a given database count and we need more, we'd need a work-around such as multiple projects each with their own dbs (PROD1, PROD2, etc.) subset.
-
Anonymous commented
Being able to monitor 10-15 databases per instance would fit my needs for now.
-
Brian Keener commented
We have 30 to 35 databases per environment and would like to add them all as it is I have had to limit to my top 15
-
Phil Grayson commented
Once of my customers has about 40 servers which this would be really useful for.
-
John C. Rogerson commented
Is this limitation applied during the Beta only?