Operations Manager is two components built together. dtcSN is a T-SQL reporting layer over Microsoft System Center Operations Manager's OperationsManagerDW data warehouse, normalizing what SCOM already collects into a dedicated database. SQLNow is the web dashboard built on top of it. Together they give a single, customer-aware view of every SQL Server, computer, and database SCOM monitors — enriched with tenant assignment and support-lifecycle data SCOM doesn't track on its own.
SCOM's data warehouse already has the raw inventory and alert history — but turning that into a management-facing view of "what do we run, for whom, and how close to end of support" means writing your own queries against it, every time.
| Without it | With Operations Manager |
|---|---|
| SCOM tracks servers, but not which customer or tenant they belong to | Every SQL Server, computer, and database tagged with its customer and domain |
| No way to see which instances are approaching end of support | Automatic mainstream/extended support-end lookup, per SQL Server version |
| Alerts and maintenance history live only inside the SCOM console | Imported into a dedicated reporting database and browsable in a dashboard |
| A management-report view over SCOM means writing your own queries | A ready set of inventory, distribution, and lifecycle views |
| No single screen for the whole estate | One dashboard: SQL Server, computer, database, and customer views together |
| Microsoft SCOM | With the OperationsManagerDW data warehouse deployed and already collecting SQL Server management pack data |
| SQL Server | To host the dtcSN reporting database, built from the provided T-SQL scripts |
| IIS + ASP.NET | Only if you want the SQLNow dashboard, not just the data layer — it's a WebForms application |
| Dependencies | None beyond SCOM and SQL Server themselves — dtcSN is plain T-SQL, SQLNow is plain ASP.NET with a dhtmlx front end, no PowerShell or dbatools involved in either |
dtcSN lives in its own database, built from a schema-and-ETL script and a separate set of reporting views, kept current by a SQL Agent job. Its extract procedures read directly from SCOM's ManagedEntity/ManagedEntityProperty tables in OperationsManagerDW and normalize them into dedicated SQLServer, Computer, and SQLDatabase tables.
| Added on top of raw SCOM data | How |
|---|---|
| Customer & domain assignment | Customer/CustomerDomain tables, matched by domain DNS name |
| Support lifecycle | Support/SQLVersion tables, driving the end-of-mainstream/end-of-extended lookups below |
| Alert & maintenance history | Imported alongside the inventory into AlertHistory/MaintenanceHistory |
| Reporting exclusions | An ExcludeDB list for databases that shouldn't appear in reports |
A raw @@VERSION string from SQL Server isn't something you can act on directly. dtcSN maps it to a known release via GetSQLVersion, then looks up that release's mainstream and extended support end dates from its own Support table via GetEndOfMainstream and GetEndofExtended — so an instance sitting close to, or past, end of support shows up in a report without anyone cross-referencing Microsoft's lifecycle pages by hand.
SQLNow is an ASP.NET web application with a dhtmlx front end, connecting directly to the dtcSN database. It's organized into a handful of views:
| View | Shows |
|---|---|
| SQL Server | The SQL Server inventory itself, one row per instance |
| Server | The underlying computer/machine inventory |
| Databases | Every database across the estate, with its type and exclusion status |
| Customers | Customer and domain assignment for every tracked server |
| Master data | Reference data: SQL versions, database types, support types, and the exclude list |
| Distribution | Charts breaking the estate down by SQL version, edition, and customer |
| Alerts & maintenance | The imported SCOM alert and maintenance history, browsable per server |
dtcSN is released under the MIT License. SQLNow, the dashboard application, doesn't currently ship a separate license file in its own repository — check with the vendor before redistributing it.
The T-SQL reporting layer — free, MIT-licensed. Run the setup scripts against a database of your own.
The ASP.NET dashboard that reads from dtcSN — deploy it to IIS once the data layer is populated.
Both components assume an existing SCOM deployment with the SQL Server management pack already collecting data — get in touch with questions.