3rd party monitoring tool is the best way to go. sys.dm_os_ring_buffers DMV provides very limited history for four hours and you can find scripts to parse the xml and get...

this question was asked several times, if you have other holidays besides weekends(new year's day, christmas, labor day, etc), a calendar table is probably the best approach. You can create...

Just a reminder to other readers, Microsoft issued a warning on this CU:

Important

There is an uninstall issue with SQL16 SP2 CU9. The payload in CU9 is fine, but if you...

side by side upgrade, either on the same box or a new box(recommended) will be fine. Could you share why you don't want to patch your SQL server boxes to...

You said, "DS_EDC_T is a Microsoft OLE DB Provider for Oracle Connection", I assume it's MSDAORA.1 from your screenshot, this is a very old driver for SQL 2008. Microsoft did...

I will stay with Microsoft, not only it's much cheaper than Oracle, it's interlinked so heavily and I need all, SQL, SSIS(to Oracle on the other end), SSRS, PowerBI. SSAS...

Yes, the cost increased a lot from SQL 2008/R2 to SQL 2012+, not only per-core licensing model instead of per socket, software assurance(SA) is required on the standby node for...

I plan to do something similar by the end of this year. Publisher: SQL 2016; Subscribers: SQL 2016 and SQL 2008, merge replication, I use push, not pull, all standard...

cluster log will probably provide the best clue to pinpoint the cause, especially those with errors.

I would also check the power plan for each node. All should be on high...

I don't think this is possible, a cluster with SQL2012, then adding a new node with SQL2016 fresh install(instead of upgrading one node from SQL2012). In-place upgrade is the only...

thank you for your update. Logically speaking, after adding @increment to @loopDate, the new @loopDate could still be a holiday(for example, two consecutive holidays on Wed and Thu),  so, the...

Thank you for sharing. I am looking for something like this. When I tried your script, it complained @increment was not declared. Please update the script.

I had not very good experience on production, the row count varies too much. In the end, i changed to temp table.

I encountered Scenario #2 last April after GPO rollout by another team and did the same by adding "Replace a Process Level Token" to SQL Server Service Account.

Alter recovery model to simple then back to full breaks the log backup chain, it invalidates all existing tlog backups for that database. Potential data loss may violate RPO.