dbWatch

Last chance to sign up! 🙌

Tomorrow at 3:00 PM (CET) we’re hosting Reporting Basics: a practical walkthrough of time-based visualizations in dbWatch, including time graphs, trends, growth-rate analysis, and merging data across multiple database instances.

Can’t attend live? Register and you’ll receive the webinar recording after the session.

Sign up here➡️

Welcome! You are invited to join a webinar: Reporting Basics . After registering, you will receive a confirmation email about joining the webinar. Compared to the 2025 dbWatch Reporting Basics webinar, which primarily focused on tabular reports and pie charts, this year’s session will introduce a stronger emphasis on time-based visualizations. In the upcoming webinar, we will demonstrate how to build and use time graphs, including trend and ...

We once disconnected a database that hadn’t been used in eight months ... in our defense, it looked safe.

Four months later someone asked:
“Where is my research?”
They updated it once a year.

That’s the risk with manual checks. If you’re retiring SQL Server databases, you need evidence from constant, consistent checks.

Learn how to automate the process in our recent blog👉 https://www.dbwatch.com/blog/database-decommissioning-checklist/

Database Decommissioning Checklist for SQL Server Database Decommissioning Checklist Learn the essential steps in the Database Decommissioning Checklist to ensure a smooth transition and data safety.

Database health is often treated like an incident-response exercise: something we scrutinize only when latency spikes, storage runs out, or users start complaining.

This AWS Database Blog post is a good reminder that the signals are usually there earlier—if you have a consistent way to review them. The authors walk through real troubleshooting scenarios using Amazon CloudWatch Database Insights, including spotting a high-load database in a fleet view, tracing load back to a top query, and confirming the fix (for example, a missing index), plus a storage-capacity case during migration where alarms and events provide the trail.

Article💡[https://aws.amazon.com/blogs/database/amazon-cloudwatch-database-insights-applied-in-real-scenarios/](https://aws.amazon.com/blogs/database/amazon-cloudwatch-database-insights-applied-in-real-scenarios/)

What I think many teams still miss is the repeatability. Turning those same signals into a standard database health report that stakeholders can rely on week after week—across platforms, environments, and owners.

That’s exactly what we cover in our reporting webinar: how to build practical, cross-platform database health reports for everything dbWatch is connected to, with a structure that works for both technical follow-up and executive visibility.

Register here 👉https://us06web.zoom.us/webinar/register/WN_pH_rXlENSgWmrWXYVs8few #/registration

What’s hardest in your environment right now: lack of visibility, too much noise, or inconsistent reporting?

Software as a service (SaaS) budgets keep climbing, and the “invisible tax” many teams are now paying is tool sprawl: too many overlapping platforms, too many logins, too many ways to do the same work—plus the governance and security headaches that come with it.

This article explains why more CIOs are shifting from “adding tools” to rationalizing them—cutting duplication, consolidating vendors, and standardizing where it actually improves speed and quality (not just cost).

Worth a read: [https://www.informationweek.com/software-platforms/as-saas-spend-grows-cios-focus-on-tool-sprawl](https://www.informationweek.com/software-platforms/as-saas-spend-grows-cios-focus-on-tool-sprawl)

What’s the bigger pain for you right now: cost, complexity, or lack of visibility?

As SaaS spend grows, CIOs focus on tool sprawl Software prices are surging, and tech shops are feeling the pinch. As CIOs reduce their tool counts, they're seeing better data consistency, improved product quality, increased innovation, and cost savings.

While database reporting is necessary, losing three months to manual reporting is not. This MSP automated third weekly and monthly reporting to free up 60 workdays a year.

Learn how they cut three months of manual reporting from the workload:

Managed Service Provider Reduces DBA Workload with dbWatch RPDATA Solutions uses dbWatch to save 12 weeks annually, automate reports, and manage cross-platform databases efficiently.