To avoid running queries against every database, Movere performs a schema check on each database looking for the schemas specific to the technologies listed above. If a match is found, a set of queries specific to that technology (and version) is run against that database.

To avoid ingesting stale data, Movere also captures the last date the data was written to the database. If it is more than 90 days old, the data collected is held as potentially stale.

To identify the databases on each SQL Server, Movere queries the ‘master’ database. If Movere has not been given access to this database, it will go to the CIM to retrieve a list of the active databases as mentioned above. A schema check will then be performed against this list. This failback was created as it isn’t uncommon for customers to only grant Movere access to the database(s) they want Movere to capture (e.g. SCCM) and, if access to the ‘master’ database is blocked, then Movere would not be aware of the existence of any other databases on that SQL Server. This is the same approach used to capture statistics from each SQL Server, even when no SQL Server access has been granted.

IMPORTANT: For ARC data from the SQL Server database level (e.g. CPU and memory usage, connections, IOPS etc.), Movere will require ‘db_datareader’ access to each database, in addition to the ‘master’ database. For more information, see What SQL access does Movere need?