wayne1022d ✭✭✭✭✭

Voted

Any thoughts on configuring SW as the data collector for SNOW, with SNOW serving as the alerting/ticketing engine instead?

As I mentioned, I'm not trying to be overly critical of any individual or specific case. The issue was eventually resolved after two months of 'communication' (mostly waiting). Moreover, the SME initially tried to close my ticket by providing a general solution and a document that had no direct relevance to my issue. I had…

The best practices are in the book, but the result come from experience.

sounds like a plan!

It would be more helpful if they simply acknowledged this as a bug that currently doesn't have a fix. 

Quick update: Support finally responded after four days, stating he’s 'out of the office' and shared a link to the release notes, claiming it includes a fix for my issue. However, after carefully reading through the article, I found nothing related to my problem. I replied within 10 minutes, but it looks like I’ll have to…

Thanks for the advice! I'll give it a try

I'm glad to hear this is a well-known issue with their support, though I’m sorry you're also having to deal with it like the rest of us. We’re approaching our 10-year mark but may need to reconsider pursuing this milestone.

I've tried everything I could, including contacting their support line for escalation. The case is still opened. It feels like everything I’ve sent/requested has just been forwarded into a black hole. 

@"Kita" Thank you for your prompt response. The case number is 01787984. I've been reaching out daily to obtain an update, as we need to proceed with our internal compliance process. Unfortunately, we haven’t received any response, and the delay is impacting our customer experience. Thank you for your assistance in this…

Thank you for the information, will definitely give it a try in Dev

Any progress has been made from your end since this post? My team plans to do the same implementation with same concern.

Same concern here, anyone please ?

Do you have more details on the output and your expectation? 

I would suggest at least to upgrade to SQL Server 2016 SP1 or SP2, but why not to at least SQL Server 2019 ? Otherwise, check your daily database maintenance logs to find abnormal events or try running CW to fix the database. Hope this help.