Part 2: Key insights from a fireside chat with Chris Yates. Read part 1 here. 

Choosing a database monitoring vendor isn't just about features. Once you’re confident that it’s time to reassess your database monitoring strategy, the natural instinct is to start comparing products. However, it’s vital to know how to assess vendor relationships, support quality, and product innovation before you sign anything.

I recently sat down with Chris Yates, Senior Vice President and Managing Director of Data & Architecture at Republic Bank, to discuss How to Evaluate Vendors for your Database Monitoring. One of the strongest undercurrents in my conversation with Chris was this: The technology matters, but the people behind it matter just as much.

This post covers some of the topics Chris and I discussed in our webinar, and looks at what separates vendors who simply sell software from those who behave like long‑term partners.

Looking beyond technology: expectations on vendor relationships

The best vendors don’t behave like sellers. They don’t disappear after onboarding, and they don’t treat the relationship as transactional.

Chris described the strongest vendors as those who act like an extension of your organisation- people who understand your constraints, your pressures, and your priorities. They show up curious, and they want to help solve your problems, not just sell their product.

That might look like:

• Connecting you with other customers facing similar challenges
• Sharing lessons learned across industries
• Adapting how they work with you as your organisation evolves

You can often sanity‑check this before signing anything:

• Review case studies
• Read independent forums
• Talk to peers in your industry about their experiences (a great opportunity to do this is at community events)

A good vendor should also be comfortable having difficult conversations. Whether it’s licensing, security concerns, performance limitations, or a blunt “this doesn’t quite work for us”, the right vendor won’t deflect or oversell.

They’ll:

• Be honest about trade‑offs
• Explain constraints clearly
• Say no when something won’t solve the problem

Database monitoring doesn’t exist in isolation. It sits at the centre of teams, workflows, and critical decisions. The vendor relationship needs to reflect that.

If your vendor feels invested, honest, and willing to get uncomfortable when needed, you’re probably in a good place.

Innovation and investment

When the conversation turned to innovation, Chris made a clear distinction between vendors who talk about innovation and those who actually invest in it.

Real innovation doesn’t show up as a flashy rebrand or a renamed feature. It shows up quietly over time, in how the product keeps pace with the way organisations evolve.

Strong vendors:

• Invest ahead of demand
• Anticipate regulatory changes
• Support emerging platforms before they’re mainstream
• Improve performance and usability in ways customers didn’t explicitly request

They’re not just reacting to today’s problems, they’re thinking a few steps ahead.

Innovation is also where partnerships deepen. The best vendors:

• Actively seek customer feedback
• Close the loop on ideas and requests
• Explain what’s possible, what’s coming, and what genuinely isn’t

This ongoing dialogue builds trust, and trust matters when monitoring sits so close to your most critical systems.

Innovation should also be easy to evidence. Ask for:

• Product roadmaps
• Release documentation
• Historical changes, not just recent ones

The last point is important. Vendors shouldn't be limited to demonstrating what’s happened in the last six months, but how the product has evolved over years. If a vendor can’t show that, it’s a red flag.

Questions for vendors

A fair amount of what we've covered can be surfaced through your own independant research, but the most important insights come from when you start talking to vendors directly. It's important you give vendors the opportunity to understand your exact set up and circumstances. Tell them what good looks like for you, and what your expectations are for the partnership. Here are a list of questions you can ask a database monitoring vendor that can help you better understand if they are the right one for you.

• “How has your product evolved in the last five years, and what customer or industry challenges drove those changes?”
• “What are you currently working on, and what does the next 12 months look like in terms of expected releases?”
• “What is your organizations strategy on [AI, Cloud, Security, Cross-platform, etc]?” (This is a great question if your company has a big AI initiative or cloud migration for example- you want your vendor to align with direction your company is going in.)
• “What does onboarding look like for my teams? What support can I expect?”
• “If I raise issues or ideas, how does feedback flow?”
• “When things go wrong, how do you respond?”
• “Are there any customers I can speak with who have faced similar challenges to my own?”

Closing thoughts

By this stage, you should be narrowing your focus to vendors who look strong not just on paper, but in conversation. Vendors who understand your context, invest in their product, and treat the relationship as a partnership. 

The final step is putting that partnership to the test. 

In Part 3, we’ll look at how to run a proof of concept that actually answers the right questions, and helps you make the decision with confidence. 

If you're interested in talking to Redgate and seeing how we measure up for your database monitoring needs, you can get in touch with us here.