Multiple SQL instances on 2012R2 Domain server

[mikemcsharry]

Help!

I've been doing a 'self audit' of one of the servers in the school I work with.

They have a 21012R2 box that is set up as the AD with a SIMS Hyper V and now has a Veeam Hyper V

 

Over the years (and I'm partially guilty for this) various systems have been trialled on the host machine then discounted / removed

 

I've noticed that I have a lot of debris of SQL of various versions. I've stopped most of the SQL services without upsetting my server,

first question (I'm sure the answer is no, but just checking..

For an AD is there any need for an SQL installation?

 

Main question

Is there any way to find out what applications these SQL versions think they are running before I kill them off?

 

there have been a few hacks on local schools recently and I'm just having a general look around and ditching anything not needed.

Thanks for any help

[Guest Guest]

AD does not require SQL, its considered bad practice to install SQL on a Domain Controller

[mikemcsharry]

Hi kieran, thanks for confirming that SQL not needed, and also confirmng that SQL on AD is bad practice.

I'm now looking to uninstall all the SQL from the server. I'm 99.9% certain that the SQLs were loaded as part of installs of other software, but weren't removed with it.

Is there a way to find out what the SQL installs 'think' they are running before I uninstall them?

[Cache]

You could, if you have it installed, connect SQL Managament Studio up to each of the instances and see what databases are running, or alternatively browse to the instance directory and take a look in the Data folder and see if there's any database files in there - would give you an indication atleast.

[Steve21]

Some of the common ones that use SQL that people "like" to install on DCs even though they shouldn't be are things like AADC which uses SQL express, MBAM etc

 

But as Cache said above, you should be able to tell from the tables if you check with management studio

 

Steve

[googlemad]

With regards to SQL Management Studio, connect to the instance(s) then simply run a new query :-

 

exec sp_who

 

This will list all databases and who is connected to them, there will be some active connections no matter what e.g. 'administrator' as you running that query is a connection to the database in itself

 

But perhaps the easiest way is to keep things simple, shut down the SQL services (Either via SSMS or even just the standard Windows services console, it will list the instances if more than one as seperate services e.g. MSSQLSERVER1 MSSQLSERVER2) and give it a few weeks to see if it breaks anything

 

Both SIMS and Veeam do use SQL but I presume those instances are installed on the individual VMs, can't speak for SIMS but unless someone has gone to the effort Veeam will be running a SQL Express instance

[HPlum78]

I would setup a new DC transfer all the FSMO roles and such likes (DNS (if not AD integrated) DHCP and those types of services) then dcpromo that server out and sort out the SQL stuff.... Thing is if you need support chances are you are going to get told to do that anyway. Edited January 31, 2021 by HPlum78

[Primus]

I would setup a new DC transfer all the FSMO roles and such likes (DNS (if not AD integrated) DCHP and those types of services) then dcpromo that server out and sort out the SQL stuff.... Thing is if you need support chances are you are going to get told to do that anyway.

 

This is good advice - you don't know what messing about has been done with that DC, a clean start would be a really good idea.

[Norphy]

Demoting the DC while SQL server is running on it will break SQL. You’re better off buiding another SQL server first, migrating the databases then demoting the DC, IMO. You can then rebuild it and promote it again, if you want.

[HPlum78]

@Norphy is not wrong its not a great place to find yourself in, and I should have been clear that I say sort out the SQL means you will be taking an outage on the SQL service but I thought that had been covered further up this thread.

 

Either way I think you are rebuilding a DC and SQL server.

Edited February 1, 2021 by HPlum78

[Jcx500]

I Agree With what everyone else is saying.

 

Migrate SQL and it databases onto its own VM

 

Then Spin up a new DC and demote the old one

 

If you have the resource I've always thought to have one role per VM

[Davit2005]

I'm not sure what current best practice is but I'd recommend not installing AD on a server running the Hyper-V role or vice versa. I'm not sure if it possible even.

[Jcx500]

I'm not sure what current best practice is but I'd recommend not installing AD on a server running the Hyper-V role or vice versa. I'm not sure if it possible even.

 

I Agree

 

If your DC Gets comprised so does your host then so do your other vm's. You can run a domain controller on a tiny vm using server core these days. The only services i ever run on a dc is dns and dhcp

[mikemcsharry]

Thanks everyone, I had stopped all the SQL services on the server a while ago and nothing had broken. I have VEEAM and SIMS on separate HyperVs on this box and SCCM on a separate HyperV on another box.

I uninstalled all the SQL packages and rebooted a few times during the process.

I’ve been in today and everything looks good

I’m chasing funding for replacement kit as one of these boxes won’t go past 2012R2, plus a lot going on with 365 etc