SQL 2016 install

[Koldov]

I'm in the process of setting up a Hyper-V VM with a view to getting our SIMS server transferred to it next year.

 

Unfortunately I've stumbled within the first few steps wand I don't want this server one to end up as messy as the last!

 

So, I have some really basic questions...

 

I have downloaded: SQL Server 2016 Standard Edition with SP3 - Per Server/CAL and not the 'per core' version (not sure what difference it makes).

 

I presume this is the correct one as we license SQL server as "Servers SQL Server - Standard 2022 (1)" under our OVS.

 

When I go to install it one of the first steps is to enter a license key... it asks you to choose either an evaluation version or use a key (the one that comes pre-entered ), I checked if I could enter my own and looked on MVLSC to find it... but it says 'this product does not require a license key'.

 

Apart from wondering why a product that doesn't require a key asks you to enter one... anyone have any other advice to get a simple SQL server installed or any other surprises/gotchas/best practise/choices...?

Edited December 23, 2022 by Koldov

[Koldov]

..."download the ISO from your Microsoft Open License Portal and run it... The product key is pre-filled from your specific license"...

 

So, that answers that part... the rest still stands, I imagine most here have plenty of experience of SQL server, so any advice would be gratefully received.

Edited December 23, 2022 by Koldov

[3s-gtech]

Looking at the roadmap, I just can’t believe that they’ve no plan in the next year to even support SQL 2019. I mean - that’s an old product now. 2016 is ancient - SQL 2012 is out of support (non ESU) and yet that’s the compatibility level.

 

I’d not want to be putting too much time investment into a new SQL 2016 install - personally I’d be using a newer version and setting the compatibility down. Supported or not. Did so with Eclipse and it just works.

[Koldov]

Yeah I get that, but the way I see it is this, it's only a VM, it's only for SIMS, it's only in production for that purpose and 2016 may be old (although that being said it's supported until 2026).

 

I only chose SQL 2016 from reading the latest roadmap from ESS... so, (although there's no reason SQL 2019 wouldn't work) if that's what they want they might as well get it for us to remain supported... then there is the option of SQL 2016 > SQL 2019 when required, unless there is a compelling reason NOT to use it?

 

The other reason I need to stay supported is that I may well need to use ESS for the transfer... or even if I attempt it myself it's them I will have to call if it all goes wrong...

[HereIGoAgain2601]

In my experience you are better off to use SQL 2016 as ESS will throw their toys out of the pram and blame everything on the SQL version (if) when you have a problem. I’m just rebuilding our SIMS servers and very disappointed to have to use Server 2019 still! No sign of Server 2022 support on the roadmap either!

[FragglePete]

! No sign of Server 2022 support on the roadmap either!

 

Unlikely they will... they want everybody to be on SIMS Connected so will make it difficult in the future to support on premise installs.

 

Spend the energy on looking at an alternative!

 

Pete

[DrCheese]

Yes - Stick to supported versions, however stupid they may be. You don't want SIMS to laugh at you when you need support & have to explain to management that you need to rebuild the SIMS server to fix an issue. End of the day you don't really get any benefit from newer versions at this point because of their stupid SQL 2012 compatibility requirement.

[HereIGoAgain2601]

Unlikely they will... they want everybody to be on SIMS Connected so will make it difficult in the future to support on premise installs.

 

Spend the energy on looking at an alternative!

 

Pete

 

The irony is we are moving back in house as SIMS connected has been a disaster 😂 Here’s hoping the powers that be will agree to ditch by the time the contract comes around for renewal! Personally I think ESS are stuck whatever they do - I would hazard a bet that most who stuck with SIMS did so because they’re scared of change so won’t like SIMS next Gen anymore than they’d like Arbor or Bromcom!

[dapaulio]

The problem I am finding moving schools away are they have years and years of “this is how we have always done it” and they are scared of change.

 

Tbh I get it, why would they want to change their is no incentive for them to change. Cos let’s face it it does not affect them in the slightest if they don’t move. They just expect it to work in practice like it always has for several years.

 

The users need to feel the heavy impact before they can cast their vote to change vendor.

 

If sims is such an issue for you now I would seriously consider seeking an alternative rather than bringing it back on prem. we don’t move back we have to move forward and unfortunately for those who wish to stay with sims we have to follow the roadmap of ess and although that the ceasing support of on prem sims is not on the foreseeable roadmap it’s only going to be a matter of time where ess will cease support and you will have to make the choice to go back again or choose to change.

 

If you do proceed bringing it back on prem just check 2016 sp3 is supported now on the current road map. Long story short I upgraded myself out of support on my last call earlier this year preempting ess saying we weren’t upto date. Thankfully they were logical about it and continued to support me but they warned me that future tickets may be not supported.

 

Good luck

Edited December 27, 2022 by dapaulio

[Koldov]

So, does anyone have a link to the SQL Server installation guide for SIMS please...?

 

 

I've searched a few posts here but they are contradictory about accounts to use and which options are needed...

Edited December 28, 2022 by Koldov

[willtech]

Should just need Database Engine Services ticked.

[Koldov]

Thanks, but this is like pulling teeth!

 

There's at least another 5 or 6 sections to complete and I doubt I'll know what to do so I think I'll wait until everybody is back from their holiday or I can get into work and contact ESS.