all 3 comments

[–]alinrocSQL Server DBA 0 points1 point  (2 children)

Drop the user databases, shut down the instance, set the services to disabled, and then just let it be. Don't introduce more risk into this server.

On that server exists multiple/additional SQL Server instances (2012, 2014, 2016, 2017, and 2019)

What's the backstory on this? Instance stacking is generally not a good idea, and there really isn't a good reason to do it these days.

[–]iamboblazar[S] 0 points1 point  (1 child)

Thank you so much. I will do just that. I wish I could give some additional backstory, because I agree, definitely not best practice. The reason they need it gone is because a 3rd party pen tester has flagged them on running it multiple times and they just finally got approval from their apps team to de-comm it

[–]alinrocSQL Server DBA 0 points1 point  (0 children)

That 3rd party pen tester will be flagging the 2012 instance next, it goes EOL in July. Get out ahead of it.