Episode 228: Predicting Application Problems with Database Metrics

Episode 228: Predicting Application Problems with Database Metrics

Episode 228: Predicting Application Problems with Database Metrics 560 420 Carlos L Chacon

As data practitioners, we want to get ahead of any problems that might come up and share those insights with others on our team. In this episode, Edward Pollack gives us a few scenarios we might consider as we attempt to prevent application issues. These techniques also go into the security space and could help prevent data loss. As we collect this information and make it available to others, we can also demonstrate the ROI we provide to the organization.

Our Guest

Edward Pollack

Ed has over 20 years of experience in database and systems administration, developing a passion for performance optimization, database design, and wacky analytics. He has spoken at many user groups, data conferences, and summits. This led him to organize SQL Saturday Albany, which has become an annual event for New York’s Capital Region. Sharing these experiences with the community is a top priority, and encouraging everyone to take the leap into public speaking and engaging others, a passion. In his free time, Ed enjoys video games, sci-fi & fantasy, traveling, and cooking exceptionally spicy foods.

Never Miss An Episode

Subscribe to get podcast notifications by email.

If you can find a bug before [users] do, you’re a hero and you’ve solved a huge problem and made it look easy and that’s great!

Edward Pollack

3 Takeaways

  1. IO trends can be a way to spot hacking/suspicious activity
  2. Capturing the before and after metrics help show ROI—which can increase your value
  3. More success will come when you can present what is needed versus just sharing a bunch of data. Putting a little presentation on the data can go a long way.

Imagine what’s possible with a dedicated SQL specialist on your team.

Leave a Reply

Back to top