Availability Group failover! After a maintenance window we have a Powershell script to monitor if a DB has failed over or not and needs failing back.
red tape and politics is my biggest challenge
Getting buy-in and access from the DBA's.
My biggest challenge is trying to convince the business to invest more resources so we can monitor all our DB environment and get ahead of customer facing issues.
I already see others have the same challenges. It's like with cyber security. It's not on their radar till it's an issue....by then it's too late.
Complex support models mean performance is reported by Application Owners and not by automated alerting.
Like so many others said, the politics of the business.
We rock database monitoring - our DBA team loves DPA and we are rolling out SQL Sentry right now. The lead DBAs love all the tools it allows them to see issues in DEV before applications get moved into production. SQL Sentry is really amazing with how it gives you a single pane of glass to see what is going on with everything on a SQL node.
LARGEST CHALLENGE TO DATE: Insight into complex data connections and data modeling for aging and disparaging vendor (COTS) stranglehold on our data housed in their failing data solutions. Integration across multivendor products is a security risk and performance risk unto itself.And inheriting such a mess is not a fun way to begin your day!
I've had issues with deadlocks from database but show up in Commvault backup software jobs. Sometimes problems like these can be tough to find root cause for. Query tuning is also an art not always a science.
Bill
Like ednelgmont, it is the getting the business to invest in the resources for anything really,
Like Jfrazier said!
Getting the funding from the business to properly monitor the entire environment, rather than just specific pieces.
Management not seeing the need for DB monitoring.
Getting necessary funding to effectively monitor the DB environment
Trying to get the DBA team to email me back about what they would like to monitor in AppInsights.
finding time to make a project of DB monitoring
Getting the database engineers to trust in the tools. They want to use multiple tools and no tools in some cases
The hardest part we have is that the DBAs don't care about most of the performance metrics.We get all sorts of alerts about SQL problems, but unless the DB server is on fire they ignore them all. ¯\_(ツ)_/¯
The DBA's.
I DON'T MONITOR DATABASE
DBAs have a SQL "monitoring" product and are not interested in migrating to a different platform.
Alright!
