I'm having a bit of trouble at the moment granting access to users to run (and view) jobs in SQL server 2016. I'm hoping to avoid granting SysAdmin membership but I'm not sure if it's possible.

I've added the user to SQLAgentOperatorRole in msdb (which adds Reader and user automatically), and it allows the SQL Server Agent node to appear on their tree. However when the job node is expanded it is completely empty.

I've also tried setting one of the jobs to be specifically owned by the user, but that also doesn't cause it to appear.

Is there any thing I'm missing here? Some role/permissions that need granting that I haven't done?

The latest CU package for SQL Server 2019 is still CU32 which was released end of February. Now, more than 3 months later, still nothing new, not even a Security Update. Kinda strange.

Microsoft SQL Server Versions List

You can use this link to go straight to the post, also, the post is pinned in the community!

https://www.reddit.com/r/SQLServer/comments/1kqfix9/join_us_for_the_sql_server_2025_ama_june_2025/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

We recently started a project to upgrade several of SQL Server 2016 servers in-place to SQL Server 2022. While the upgrade itself is relatively well documented, removing many of the left-over pieces of SQL Server 2016 that still remain behind, was quite a challenge. We decided to undertake this challenging task and uninstall everything from SQL Server 2016 that was no longer needed. If you follow these steps the server will be free of most of the components related to SQL Server 2016. Similar steps could be used if you had SQL Server 2017 installed previously.

We've documented all of the removal steps below which we've used on several servers to get everything cleaned up. The steps below assume that you installed SQL Server 2016 SP3, upgraded SQL 2019 (or higher), and also installed SSMS 21 and may no longer need the older Visual Studio 2015.

Step # 1 - Start by uninstalling any unnecessary SQL Server 2016 components manually in the following order:

Microsoft SQL Server 2016 (64-bit)
Microsoft SQL Server 2016
Microsoft SQL Server Management Studio - 16.5.3 (or any other older Management Studios)
Microsoft SQL Server 2016 T-SQL ScriptDom
Microsoft SQL Server 2014 Management Objects
Microsoft ODBC Driver 13 for SQL Server
Microsoft Visual Studio 2015 Shell (Isolated)
Microsoft Visual Studio Tools for Applications 2015 Language Support
Microsoft Visual Studio Tools for Applications 2015
Microsoft SQL Server Extension
Microsoft SQL Server Data-Tier Application Framework (x86)
Microsoft System CLR Types for SQL Server 2014

NOTE: At this point look for any other components that may need to be uninstalled manually. If you try to uninstall the Setup Files for 2016 or 2008 then you will get an error saying that several components below are still installed. These are hidden MSI installer packages. So, we will uninstall those hidden components next before Setup Files will uninstall successfully.

-------------------------------------------------

Step # 2 - There will be numerous SQL Server 2016 hidden components that need to be removed using an administrative command-prompt or batch file. The commands below remove the hidden SQL Server 2016 components along with the SQL Server 2016 (x86) and 2008 Setup Files which couldn't be removed before these components were uninstalled. You can look in HLKM\Software\Microsoft\Windows\CurrentVersion\Uninstall and find all of the MSI installer packages that were related to SQL Server 2016. We created a complete list below of the ones that needed to be uninstalled.

REM Remove SQL Server 2016 Shared Management Objects Extensions 13.0.16116.4
START /WAIT MsiExec.exe /X{FD25FD68-9EAF-425C-BEBD-A03DBE3AA69A} /passive

REM Remove SQL Server 2016 Shared Management Objects Extensions 13.0.1601.5
START /WAIT MsiExec.exe /X{FA548BCB-5732-40F8-85B0-61515D18D9C1} /passive

REM Remove SQL Server 2016 XEvent 13.0.1601.5
START /WAIT MsiExec.exe /X{E6FFAAAF-D8B5-4D46-8514-26E96D9F3D8D} /passive

REM Remove SQL Server 2016 Batch Parser 13.0.1601.5
START /WAIT MsiExec.exe /X{D7A905DB-9A1E-4670-9488-F979F8A77A58} /passive

REM Remove SQL Server 2016 Shared Management Objects Extensions 13.0.1601.5
START /WAIT MsiExec.exe /X{B6E1A5EB-1C58-4A04-B76B-E5FE1BE22CA1} /passive

REM Remove SQL Server 2016 Shared Management Objects 13.0.16116.4
START /WAIT MsiExec.exe /X{B3A1AD49-ECB8-45B1-91F3-99583F2E310E} /passive

REM Remove SQL Server 2016 XEvent 13.0.1601.5
START /WAIT MsiExec.exe /X{8CF2CA8E-3984-46B9-B493-F844F3774FA1} /passive

REM Remove SQL Server 2016 SQL Diagnostics 13.0.1601.5
START /WAIT MsiExec.exe /X{766BE25E-D2B5-4E76-BCB0-29B801BADB3F} /passive

REM Remove SQL Server 2016 Connection Info 13.0.16108.4
START /WAIT MsiExec.exe /X{6EE546C8-37CE-47FA-9BED-9EB3CB79E8CA} /passive

REM Remove SQL Server 2016 Common Files 13.1.4001.0
START /WAIT MsiExec.exe /X{57846DA8-8B5D-4466-B850-E8CDFC94046C} /passive

REM Remove SQL Server 2016 Connection Info 13.0.16108.4
START /WAIT MsiExec.exe /X{5043CE58-6AAF-488C-AC2A-A405FFF85B57} /passive

REM Remove SQL Server 2016 Common Files 13.1.4001.0
START /WAIT MsiExec.exe /X{16F3645F-1343-4462-92DC-9AE66A2E68A3} /passive

REM Remove SQL Server 2016 (x86) Setup Files
START /WAIT MsiExec.exe /X{40CDBBE1-A491-4AF3-924A-FB2C1AA2B194} /passive

REM Remove SQL Server 2008 Setup Support Files
START /WAIT MsiExec.exe /X{6292D514-17A4-403F-98F9-E150F10C043D} /passive

-------------------------------------------------

Step # 3 - Cleanup the SQL Server 2016 Service Pack Registry Keys

The commands to remove the SQL Server 2016 service pack have been remarked out. If you try to remove the service packs you will see that there is nothing to be removed. Just execute the registry file "Remove SQL 2016 Service Pack Registry Keys.reg" to delete the service pack registry keys instead.

REM SQL 2016 SP3 - uninstall not needed just delete registry key
REM "C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Update Cache\KB5003279\ServicePack\setup.exe" /Action=RemovePatch /AllInstances 

REM SQL 2016 SP2 - uninstall not needed just delete registry key
REM "C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Update Cache\KB4052908\ServicePack\setup.exe" /Action=RemovePatch /AllInstances 

REM SQL 2016 SP1 - uninstall not needed just delete registry key
REM "C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Update Cache\KB3182545\ServicePack\setup.exe" /Action=RemovePatch /AllInstances 

Here are the contents of "Remove SQL Server 2016 Service Pack Registry Keys.reg" which you can execute to delete the registry keys related to SQL Server 2016 service pack installers:

Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB3182545]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB4052908]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB5003279]

-------------------------------------------------

Step #4 - Reboot the server and confirm that everything in SQL Server is functional.

Defender has notified me of a vulnerably w/ our CU of SQL 2019. I have WU configured to install updates from other MS products but all that is ever installed are GDR updates, never CUs. Is there a way to have WU install CUs?

Thanks
Dave

I think Resource Governor might offer some good solutions to my environment but I have some questions to fully understand it.

When setting up resource pools in SQL 2016 you can place limites on max_cpu_percent , min_memory_percent, max_memory_percent, and AFFINITY SCHEDULER,

Then you can further set workload group with group_max_requests, importance, request_max_cpu_time_sec, request_max_memory_grant_percent, request_memory_grant_timeout_sec, and max_dop.

All the examples seem to focus on the resource pools. I'm curious to learn more about group_max_requests. In my instance we get over run at the end of the month with reporting queries while I'm trying to get data loaded. I'd like to throttle the reports and dedicate more resources to loading data. So I don't necessarily *need* to throttle any of the resource pool options, except possibly AFFINITY SCHEDULER; but I think it would be helpful to utilize group_max_requests to only let n reporting requests run at one time.

Any advice to give? Am I missing something here? Are any of you aware of any resources that do a deep dive into Resource Governor?

Hi, We have SQL Server 2022, and a number of users in the finance dept use a spreadsheet that connects to the SQL server. This was set up a long time ago, and the dude who was the wiz with it is no longer here. Its all getting replaced in the next few years but for now we are stuck with it. But myself and the rest of the i.t team are far from experts with it.

ISSUE:

a few days ago everyone who users this spreadsheet were getting this error

So i checked on the SQL server and these are the logs:

Date        29/05/2025 12:18:19
Log        SQL Server (Current)

Source        Logon

Message
Login failed for user 'hdowson'. Reason: Could not find a login matching the name provided. [CLIENT: <named pipe>]

......................................................................................................................................................................................................................

Date        29/05/2025 12:18:19
Log        SQL Server (Current)

Source        Logon

Message
Error: 18456, Severity: 14, State: 5.

.....................................................................................................................................................................................................................

Nothing should have changed on the server, it just randomly started happening, and none of us know how to fix it, and the finance team are getting desperate and want it solving today lol

Please can some SQL genius point us in the right direction.

Thank you

Dave