You may install SSMS 17.9.1 side-by-side with SSMS 18.x. I usually don't jump on the latest version since the latest <> the greatest.

based on Microsoft doc, SQL 2016 Enterprise Edition cannot be installed on Windows 10 Enterprise(on Windows Server 2012 or newer only, no client version like Windows 10/8.1/8), but your screenshot...

what's "lac"?

I have the same issue. Due to merge replication, all foreign key relations were removed so that publications can be setup and scheduled in any order without issues. Most tables...

I recommend sticking with your C#. This is probably the easiest and most flexible. If you want to explore options,

1. Telerik reporting, this can be easily put into front-end web...

Used Symantec / Backup Exec, then switched to Avamar Backup. But I only use native backup on sql server side; once the backup is done, backup team can back up...

Your instance was already patched to SP2(13.2.5026). Based on screenshot, the shared features were patched to CU12(13.2.5698); but your default instance was still at SP2(13.2.5026), NOT CU12.

disable one user per day, and see if there is anyone yelling/calling helpdesk. transaction logs only tracks changes to a database, not for select. And reindex could change tlog, too,...

FYI, your instance is not clustered. That's why I like cluster, if it fails when patching the first node, it does not impact the current workload; if it fails when...

To me, it happens to replication between publisher and subscriber. Due to authentication failure, connection to subscriber fails. Since replication handles network and other issues gracefully, including deadlocks, front end...

I have the same issue when DC is patched and rebooted. Since it's monthly on a Sunday and only very short, I just ignore those. There are three DCs and...

I strongly recommend ola hallengren's "SQL Server Maintenance Solution"(https://ola.hallengren.com/). You don't need to worry about the options, there is a history of full/differential/log backup instead of overwriting existing...

Your statement("Replication will allow you to go only two version UP or DOWN") is for transactional replication only. I mentioned it's Merge Replication, no such restriction on merge replication.

you can cast all xml columns to nvarchar(max) then use distinct on nvarchar(max).

I assume you are using Enterprise Edition, not Standard Edition; otherwise, you can only put one database in one basic AG.

If merge replication is used(as my employer does), move publisher...