The dbWatch Blog

We all experience how the number of database instances keep growing (especially SQL Servers) in the last few years.

Managing large database farms requires a different mind-set and a different set of tools than what you need when you only have a handful of instances to look after.

The secret to monitoring data is about finding the perfect balance. Too much data and you’re drowning, not enough and an ailing instance may slip under your radar. The perfect mix will track your instance’s vital signs, putting your finger on the databases’ pulse. With these vital signs, you can quickly find out if the database is healthy, while being able to track and understand any irregularities.

Monitoring databases in large,  distributed or hybrid environments

Monitoring database or SQL servers can in itself be a complex task - as we discuss in SQL Monitoring - 5 steps to full control. But what if you have a really complex environment, with multiple locations, restricted networks behind firewalls, high number of servers or a hybrid solution with some on-premise and some in a cloud? What are the issues, and how can you resolve them?

dbWatch Enterprise Manager 12

This year Bob’s job as a DBA has some challenging issues. His company is considering moving to the cloud, which has Bob worried about job security. The developers are interested in adopting Devops, to streamline their applications. Additionally, his boss wants more database security and decided that the system needs 24 x 7 maintenance. As if that’s not enough, there seems to be never ending demands for growth in services, solutions, data and the need for speed.

No matter what the service, no matter what the purpose, no matter what the product, the cloud is being touted as an answer to scalability by pretty much every major vendor. It started with data-storage, and rapidly moved to databases. In the past we were limited by the actual hardware that we owned. If we needed to expand on it, we needed to purchase more memory, and in many cases we needed to purchase new hardware as the old wore out, or was incapable of handling what we needed it to do.

It's an old problem. The more results you deliver, the more that are expected. The faster you provide them, the faster they are expected. Next thing you know, old methods don't work as well as they used to.

New demands require new workflows. On top of it new technologies are appearing making it seem like your old tools are no longer needed. Next thing you know the environment in which you work has changed. It is barely recognisable, and you might be afraid that you are no longer relevant.