October 27, 2017 at 11:00 am
I am going to download and install the SQL Server 2017 Developer Edition this weekend. My concern is I have tried unsuccessfully to install SQL Server 2016 Developer Edition several times and instead of digging in and figuring out why the install completes successfully (no errors) SQL Server 2016 would fail to start, and all I remember about the error message was something about a handle.
Would it make since to go through my registry and clean out any SQL Server entries? SQL Server 2016 is the only version of SQL Server I have tried to install at home.
October 27, 2017 at 11:05 am
Shouldn't matter overall for the instance. The db engine should be separate. What's shared is typically the connection libraries, the tools, the other stuff.
One thing you might aim for, Lynn, is grab Virtual Box as well, drop a quick Windows instance on there (or Ubuntu, that is really easy) and then install there. In fact, I bet you could get Ubuntu and SSoL going and for the most part, it would look like any other SQL instance from SSMS.
October 27, 2017 at 11:11 am
I am lucky to be able to spell Linux. I am VM ignorant even though I work with (on) them daily.
October 27, 2017 at 11:47 am
Lynn Pettis - Friday, October 27, 2017 11:11 AMI am lucky to be able to spell Linux. I am VM ignorant even though I work with (on) them daily.
I'm very VM ignorant too, but I've found VirtualBox very easy to use, and have used it on my laptop a number of times when I need a temporary sandbox to play with something. Just ignore who the current owner of VirtualBox is and you'll be OK! 😉
October 27, 2017 at 11:53 am
It's really easy. Don't let ignorance create fear. Virtual Box is a Windows app, next, next, next. Create a VM, pick a folder/file to hold it. My Ubuntu VM was just 40GB. Download the Ubuntu desktop, 16.04.3 LTS (Long Term Stable release). It's just a file, but when you create a new VM, just point the install to this file. Create a VM with 4GB RAM, let it install. You'll log in and set a new password for admin.
You'll use this as your sudo password, and the BOL instructions give you the commands. It's not hard.
Virtual Box - https://www.virtualbox.org/wiki/Downloads
Ubuntu Desktop - https://www.ubuntu.com/download/desktop
New VM - http://www.virtualbox.org/manual/ch01.html#gui-createvm
If you want to do this with Windows, same thing, just download a Windows .iso. It's worth understanding this a bit. If you have W10, you could just get Docker running and pull a 2017 container image.
I think you should be able to install 2017 easily on your host. If it doesn't work, likely you might have something in your Windows host that's borked. Dig into the install log.
One last thing, what version of Win? I think 2016/2017 is 8+
October 27, 2017 at 12:04 pm
Steve Jones - SSC Editor - Friday, October 27, 2017 11:53 AMIt's really easy. Don't let ignorance create fear. Virtual Box is a Windows app, next, next, next. Create a VM, pick a folder/file to hold it. My Ubuntu VM was just 40GB. Download the Ubuntu desktop, 16.04.3 LTS (Long Term Stable release). It's just a file, but when you create a new VM, just point the install to this file. Create a VM with 4GB RAM, let it install. You'll log in and set a new password for admin.
You'll use this as your sudo password, and the BOL instructions give you the commands. It's not hard.Virtual Box - https://www.virtualbox.org/wiki/Downloads
Ubuntu Desktop - https://www.ubuntu.com/download/desktopNew VM - http://www.virtualbox.org/manual/ch01.html#gui-createvm
If you want to do this with Windows, same thing, just download a Windows .iso. It's worth understanding this a bit. If you have W10, you could just get Docker running and pull a 2017 container image.
I think you should be able to install 2017 easily on your host. If it doesn't work, likely you might have something in your Windows host that's borked. Dig into the install log.
One last thing, what version of Win? I think 2016/2017 is 8+
I have windows 10 on my laptop at home. Not sure of the exact edition but it isn't the home edition. If I knew anything about hyper-v I'd use that.
Oh, and it isn't fear, it's just a lack of understanding how to set them up. I rely on the Sysadmins here to provide me with the VMs I need.
October 27, 2017 at 2:29 pm
It's simple. If you have W10, I'd just install a .\SQL2017 instance and get it working.
You might also try the container route. You can keep SQL 2016 and 2017 in containers, not install the services on the host, and easily switch between the versions as default, which is cool.
October 27, 2017 at 2:36 pm
Steve Jones - SSC Editor - Friday, October 27, 2017 2:29 PMIt's simple. If you have W10, I'd just install a .\SQL2017 instance and get it working.You might also try the container route. You can keep SQL 2016 and 2017 in containers, not install the services on the host, and easily switch between the versions as default, which is cool.
My problem is that I was never able to get a fully successful install of SQL Server 2016. The install ran with no errors but SQL Server 2016 would not start.
October 27, 2017 at 2:39 pm
C'mon, Lynn. You're a senior guy. dig into the logs. Should be something in /log/errorlog that helps you.
October 27, 2017 at 2:53 pm
Steve Jones - SSC Editor - Friday, October 27, 2017 2:39 PMC'mon, Lynn. You're a senior guy. dig into the logs. Should be something in /log/errorlog that helps you.
I would have, I just wasn't motivated enough to do it at home (and yes, that is my problem). Perhaps because we just late last year finally moved to SQL Server 2012 from SQL Server 2008 R2 (which we finally deployed in early 2015) in the field. Now my plan is to install SQL Server 2017 (and help my daughter figure out why her install of SQL Server 2017 didn't fully work, looking like the same thing as my 2016 install). I have more motivation now based on things going on at work. I am getting moved more into internal projects instead of the products we build and support for government customers which are moving toward MongoDB and PostreSQL.
This is why I was asking if it would make sense to clean the registry before I try installing SQL Server 2017.
Kylie had to play a bit with virtual machines in one of her classes. Maybe I will have her try downloading VirtualBox and Ubuntu and create a VM that way. She can then help me with that as well.
October 27, 2017 at 3:43 pm
I'm sure you'll be fine. Give it a go, post if things seem confusing. I think Hyper-V networking can be confusing, whereas VMWare just gets things working. I have VB on one machine here, and it was fairly easy to get connected.
It wouldn't hurt to clean the registry, but if your issue was something else, might not help. I'd flip through the errorlog for now, see if there's a service, maybe check the install log. See if there's something that stands out. If not, try installing SQL 2017. Can always go back and uninstall or clean registry and delete folders.
October 28, 2017 at 7:04 am
I have sql2016 and sql2017 running side by side on Windows 8.1 64 bit version and they are quite happy, no real issues but Steve's suggestion of virtual box sounds great, may have to try that.
Personally I would want to solve the SQL 2016 install issue first, simply to get an understanding of what went wrong,
Steve's virtual box installed in minutes and looks good may have a bash with that too.
If all installed with no prob check the service account's I seem to recall an issue with permissions for which I set up a separate account.
HTH
...
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply