If you are concerned with the number of VLFs a database has as too many, we handle that by setting up a job which counts the number of VLFs per...

You may be able to follow some of these steps.   Based on your comments, each step may or may not apply depending on if the disk was ever properly presented to...

Just to add, as far as changing database owners, one thing we noticed when we changed the owner of the databases to 'sa', the previous owner which was removed as...

This is another "depends" question.  Is each instance treated as equally important?  Are the database sizes and expected I/O comparable for each instance?  How critical is the application whose back-end database...

Pretty sure you will need to remove the databases from the AG, and then re-add them back which will require database restores with no recovery as you know which is where the new transaction...

There are a good bit of articles out there which state that for Synchronous Always-On, the server is likely to take a performance hit due to the confirmation it requires for commits,...

Hi, no, each named instance will need to have its own static reserved IP address.  The Sql Server Network Name, which you will complete during the Sql Server failover Cluster installation will...

The reason we both mentioned AG failover is because your configuration sounded like you had both FCIs (Failover Clustered Instances) and AGs (Availability Groups) in which case you would want to...

I would probably approach this task similarly.  The key is always ensuring that NO instances or Ags are running on the node you are upgrading until after it is upgraded.  

Some experts say that the log file for tempdb should be twice the size of a single data file and to set the log file auto-growth to a hard value...

See if this script helps you -

DECLARE @DB_USers