EF is the likely the reason, but it's not easy to fix. Your server resource(48 cores, 768GB memory) is more than enough for your workload(50,000 hits a day). Inside EF,...

you may enable "lock page in memory", which I never do and it works fine on my server boxes, but a lot of well-known people in the SQL community recommend...

my sysadmin likes doing that, and I told him don't do that again. Restart SQL server is NOT the option. Everything in memory will be wiped out when restarting. Try...

Google some script on the web to check free space of the 257GB data file, I guess there will be some free space available. Until it's all used, autogrowth will...

Agree. this is the sensitive case I was involved. A consultant was hired by my employer to work on a payroll-related project. I provided access to live data and testing...

both MSDTC and quorum belong to the cluster, not to a node, of course, it will be owned by a node. With one node(CANMTLDEVSQL1 ) only, quorum needs to be...

this is doable. Since CANMTLSQL2 was already shutdown, quorum, MSDTC, sql server, etc are all running on CANMTLDEVSQL1 and simply evict CANMTLSQL2  from failover cluster manager | node

this is similar to what I did and still is in use. Every hour, I copy the transaction log backup to another workstation via powershell. An agent job restores the...

yes, this could take a while if you didn't disable telemetry extended events. At least that's the case on my local SQL 2016 instance, although there is no load, only...

I didn't do this before, but you can set up merge replication between SQL 2016 and SQL 2008. Select all tables and once snapshot is applied to subscriber/SQL 2008, you...

Your database is write heavy(update/insert/delete). It should be fine. Or, change t-log backup to every 5 minutes from 15 minutes.

I just did the same, so, I answer the questions I am aware of.

1. I have a 24 core physical server and am planning to purchase SQL core license. Since...

someone troubleshot similar issue and NIC teaming was the cause. It may not be the same, but it included a good reference to dig in.

https://www.sqlservercentral.com/articles/workplace-encounters-grappling-with-async_network_io-waits

https://www.sqlshack.com/reducing-sql-server-async_network_io-wait-type/

I would suggest setting up a virtual machine and trying it out. Even if someone says it's OK, you still need to verify it and test the scenario before performing...

I use https://www.sentryone.com/plan-explorer, even the professional edition is free now.