Default SQL instance 2008 r2. Named instance SQL 2016/2017 ... any gotchas?

Hey peeps,

Mix of SQL instances. 2008 r2 as default and 2016 or 2017 as named instance.
Any gotchas.

Currently have the 2008 r2 now as default and want to move all production systems other than one into a named instance using the latest SQL.

This is the preferred option as opposed to having an additional VM's and licensing etc...

Many thanks

R
LVL 7
RomoloIT Pro, Projects, Mentor, TrainerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

RomoloIT Pro, Projects, Mentor, TrainerAuthor Commented:
Windows 2008 r2 standard as OS.

Ta

R
0
ste5anSenior DeveloperCommented:
SQL Server 2016+ is not supported on Windows Server 2008 R2. See Hardware and Software Requirements for Installing SQL Server.
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor Commented:
Good point Ste5an.

Was focussed on the mix of instances... my bad.

So if installing on Server 2012 r2, best configuration?

Default SQL 2016/17, Named SQL 2008 r2
Default SQL 2008r2, Named SQL 2016/17

Best way round? Needs to be on the same VM.

Many thanks

R
0
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

ste5anSenior DeveloperCommented:
Depends on the kind of use-case and your applications.

When there is a SQL Server instance to serve the "primary use-case", then using a default instance for make sense.
Otherwise using only named instances makes working with them easier and less error-prone.

Cause it's

YOUSERVER
YOURSERVER\SecondaryInstance

vs

YOUSERVER\PrimaryInstance
YOURSERVER\SecondaryInstance

so it's easier to see on what instance you are/should be without the possibility that you forgot to specify the correct instance name.
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor Commented:
Good point Ste5an.

I am happy with that.

It is more is there any gotchas for mixing these versions on the same box and should be a certain way round, or install first etc...

I am looking for the best way.

One app requires Sql Server 2008 r2.
Others can use later SQL.

I want to avoid unnecessary hiccups if I can help it.

Thanks
0
ste5anSenior DeveloperCommented:
SQL Server 2008 R2: How important is this application? How much resources are needed for the database? How long should it run SQL 2008 R2, which is out of support?

Maybe when this is only short or medium term, then maybe a separate VM is an option.

Otherwise start installing the requirements first for 2008 and 2016+ (.NET frameworks). Then install the instances, 2008 first.

I'm not aware of issues with mixed instances.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RomoloIT Pro, Projects, Mentor, TrainerAuthor Commented:
Hi Ste5an,

Yes I know!!!! I am in big discussions with the supplier of the software solution. You are commenting the same as myself. However, this is where we are stuck.. usual IT challenge :).

Cannot do separate VM at this time.

OK.. cool.. I figured SQL 2008 r2 first and then sql 2016/2017.

I believed it would be good... however, just wanted to check with others as I have not mixed the newest versions with a version as SQL 2008 r2.

Thanks ste5an.

Anyone else have any comments or tips on this configuration?

Thanks

R
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
You can always try to migrate the MSSQL 2008R2 database to one of the new instances and do not change that database compatibility so it will act as a MSSQL 2008R2 database even it's stored in an higher SQL Server instance version. Perform some tests to check how the application behaves with this database configuration. If it works perfectly fine then you can remove the old SQL Server version and free resources to other instances.
0
RomoloIT Pro, Projects, Mentor, TrainerAuthor Commented:
Many thanks .... I was looking for my specific requirement and if no-one else has any comments about mixing versions then I can close this.

Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SQL

From novice to tech pro — start learning today.