[Looking for Charlie's main web site?]

Speaking online tonight at MMCFUG, on "What if no one is monitoring your DB server?"

Just wanted to share news for my readers here that tonight (Apr 9 at 7pm US Eastern time) I will be presenting at the online meeting of the Mid-Michigan CFUG, on the topic, "What if no one is monitoring your DB server?".

Anyone can join in live, and the meeting will also be recorded and posted eventually at their Youtube Channel.

Here's the description for my talk, which is also offered on my site's presentations page:

Are you having problems in your web app, where you wonder if it might (or might not) be due to your database? Are you able to monitor what's going on in the DB? Is *anyone* doing that? Often, no one is watching, trusting that "the database should just work" or "that's the DBA's job". Maybe you don't have one. Does anyone there know how to see what queries/activities are running right now in the db? How about what's run most recently? or what ran an hour ago, or yesterday at 2:31 when your app server crashed? There are tools that may (or may not) help with that.

Indeed, there are "database monitoring tools" (some free, some commercial) for most any type of database, but some may only monitor very broad metrics, or conversely may focus on needless levels of depth. Sadly, most can't answer those simple questions I just asked. What can you do if you have no DB monitoring tools, or your tool seems to be lacking? And what if you may feel you "can't install a DB monitoring tool"? There may be better solutions than you think--and even if your DB is in the cloud.

In this session, veteran server troubleshooter Charlie Arehart will discuss this topic of DB monitoring, which he helps clients deal with about weekly. Folks come to him with "server problems" (about 200 clients per year), and they often have no insight into where the problems really are or how to solve them. Sometimes it IS a DB problem, and sometimes they DO know that--but they can't figure out "why"; other times they THINK it's a DB problem when it's NOT, and still other times it's a DB problem and they don't even realize it. A good DB monitor can help you know either way--and can help the DBAs and/or the developers.

In this talk, you will come away with several options to consider, and perhaps a new perspective on how to view DB monitoring.

I hope you'll come along, or watch the recording once posted. I'll share the direct link on the presentations page, once it is. (And if any had seen my version of the talk offered first at IntotheBox 2020, this version is both refined and updated quite a bit since then.)

For more content like this from Charlie Arehart: Need more help with problems?
  • If you may prefer direct help, rather than digging around here/elsewhere or via comments, he can help via his online consulting services
  • See that page for more on how he can help a) over the web, safely and securely, b) usually very quickly, c) teaching you along the way, and d) with satisfaction guaranteed
Copyright ©2024 Charlie Arehart
Carehart Logo
BlogCFC was created by Raymond Camden. This blog is running version 5.005.
(Want to validate the html in this page?)

Managed Hosting Services provided by
Managed Dedicated Hosting