Where I work, the DBA patches the DBA software (SQL for example) and the IT team patches the OS.

So Windows updates are handled by IT and SQL patches are handled...

I am glad I could help.  I also want to make a note, which is in my signature, but I want to make it very clear:

As with all advice you...

I have not tested this, but I am 99.99999% confident you could create a temp table (CREATE TABLE #tmpTable(col1 datatype1, col2 datatype2, ...)) with the columns you expect then do...

I don't think SQL will be able to rank those the way you wanted them.  The reason why - if you are ordering it by "Rating", ID 8 has a...

One thing to keep in mind is if you are using SSIS, you will want the SSMS version that matches the SSIS database version.  For example, if you have SSIS...

If that error pops up when opening SSMS, I would try doing an uninstall and reinstall.  I would also check for free disk space and if you are on a...

We still have Windows XP computers that are "critical" to the company due to similar things.  In-house built software that is used for a product we are working to EOL...

My HOPE is that your application is throwing an error.  Since the application is known, you either have the source to it OR can contact the vendor to get them...

To add to your patching notes, it also falls under how much planned downtime can you get.  I have some systems that require maximum uptime and downtime on them is...

To add to what Phil said, my understanding is that ADS (Azure Data Studio) is more of a "development" tool and SSMS is more of a "management and administration" tool.

Deploying...

My opinion - VERY.  In general, what you are going to be doing the most of in SQL is NOT going to be CPU heavy operations but memory and disk...

I MAY be mistaken on this, but I think that an i9 is a desktop processor not a server processor. Generally, you would want to have SQL Server running on...

You just need to make your font smaller if it doesn't fit 😛

BUT even if you...

That is VERY hard to read and consume...  But stripping out everything prior to the line of *'s, fixing a bad piece of formatting,  and running it through a SQL...

To add to what Phil is saying - I would try it out and see what happens.  Basically, run your code and then either SELECT or PRINT @Where to see...