August 29, 2017 at 4:42 am
A company we are developing for have purchased a new Server
There will be about 4 users
Trying to install SqlServer 2016 (and 2014) but both failed after installing for about 30 minutes
The log file is very big and its difficult to see why it failed
I also see now that its not recommended to install SqlServer on a Domian Contoller (which is what the new Server seems to have been set up as)
Any suggestions on what might be stopping the install or where I go from here
August 29, 2017 at 5:09 am
You're going to have to search the install log for errors. Without more info, this is impossible to diagnose at a distance.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
August 29, 2017 at 5:34 am
What Phil said. Additionally, I wouldn't want to install SQL Server on a domain controller. Using a server for multiple purposes means the hardware resources will be split between both types of functionality. I like my SQL Server to run on hardware that's dedicated to it and it alone.
August 29, 2017 at 5:42 am
Thanks for your replies
So my only option would be:
4 pcs
Separate Machine (as Domain Controller)
Separate Machine (As Sql Server Machine)
Seems like an overkill for just 4 users
Do I have any other options
Can I operate without a Domain Controller ?
August 29, 2017 at 6:07 am
xxx-593414 - Tuesday, August 29, 2017 5:42 AMThanks for your replies
So my only option would be:
4 pcs
Separate Machine (as Domain Controller)
Separate Machine (As Sql Server Machine)Seems like an overkill for just 4 users
Do I have any other options
Can I operate without a Domain Controller ?
It's not if you can operate without a domain controller, but can your client?
If they have set their server up as a DC there must be a reason for it.
Solutions may be to install Hyper-V on the DC and create a VM for a SQL server get a small PC attached to the network to run SQL, but as Phil and Ed said you need to look at the error log, its not impossible to install SQL on a DC just has to be done right, using the right configuration options etc. Its just not best practice to do so.
August 29, 2017 at 6:16 am
Thanks again for your reply
Any idea of where on the logs to start looking
There seems to be a few 'Log Files' and they just have hundreds of commands of what has been done
August 29, 2017 at 6:23 am
xxx-593414 - Tuesday, August 29, 2017 6:16 AMThanks again for your reply
Any idea of where on the logs to start looking
There seems to be a few 'Log Files' and they just have hundreds of commands of what has been done
Look through the setup bootstrap log, that will detail what failed on the installation.
August 29, 2017 at 6:32 am
Hi
Going back to one of earlier replies
Is it possible to configure, on the one Physical machine, through HyperV or another
a Domian Controller
A SqlServer Machine
.i.e. on the one physical machine, have a Domain Controller and Sql Server as separate 'Virtual ' machines
If possible, this would overcome the 'Not recommended to install SqlServer on a VM '
August 29, 2017 at 6:37 am
It's fine to install it on a VM.
August 29, 2017 at 6:46 am
xxx-593414 - Tuesday, August 29, 2017 6:32 AMHi
Going back to one of earlier replies
Is it possible to configure, on the one Physical machine, through HyperV or another
a Domian Controller
A SqlServer Machine.i.e. on the one physical machine, have a Domain Controller and Sql Server as separate 'Virtual ' machines
If possible, this would overcome the 'Not recommended to install SqlServer on a VM '
Short answer: Yes.
Long answer: Yes, and depending on the version of Windows Server you have, you may be able to do this from one license key (check your license carefully, I'm not a MS Licensing Specialist and I didn't stay at a Holiday Inn Express last night.) Further, you'll need to be a bit more aware of the resources available on the physical server and how those resources are allocated. You need to look at keeping sufficient resources for the Hyper-V host, plus the DC, plus the SQL Server.
As for the allocation of those resources, you'll likely need to do some testing to see where things start to go south, performance-wise, and that includes the DC.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply