Table Partitioning in SQL Server – Partition Switching

https://pragmaticworks.com/blog/table-partitioning-in-sql-server-partition-switching Partition switching moves entire partitions between tables almost instantly. It is extremely fast because it is a metadata-only operation that updates the location of the data, no data is physically moved. New data can be loaded to separate tables and then switched in, old data can be switched out to separate tables and then archived or purged.... » read more

Advantages of Database Partition

https://blog.coeo.com/five-cool-things-you-can-do-using-partitioning Move files to another location without affecting the availability of the database. Rebuild part of our data using different compression/fill factor settings. Setting part of our data to be READ_ONLY. Quickly remove old data without incurring in high log usage. … Partial backups and restores.

Create Index Progress

Create Index Progress Sources: https://dba.stackexchange.com/questions/139191/sql-server-how-to-track-progress-of-create-index-command/139225

Apply Latest CU Update for SQL Server 2019

Note: Run the SQLServer2019-KB5039747-x64.exe file to start the patch. An GUI similar to the SQL Server Install will popup to guide you through the patch process. Make sure SQL Server services has been stopped. Make sure to restart the server after the patch has completed. After the restart, the SQL Server version should reflect what... » read more

Windows Failover Cluster – Configure a File Share Witness

Create a Witness This sections shows how to  create a witness. In the Failover Cluster Manager, locate the new cluster resource, right click, More Actions, Configure Cluster Quorum Settings. You Begin page of the Configure Quorum Wizard Choose “Select the quorum witness” Quorum Configuration Option page. This is where you will inform the Wizard which... » read more

SQL AlwaysOn failover cluster automatically failing over

Issues: SQL failover cluster automatically failing over. Windows Failover Cluster Log: Cluster node xxxxx was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration... » read more

SQL Job stuck in “Performing completion action”

Issue: All the sql job stuck in the state “Performing completion action” An AlwaysOn failure would sometimes cause this issue. A network glitch between SQL Server and Exchange Server can also cause this issue. Fix: Restart the SQL Agent service.