Components from prior versions of SQL

Epicor ERP 10
1

Does your server where SQl is installed show components of prior SQL versions?

Our :production SQL server is running SQL Server 2014, but has a some SQL 2012 and SQL 2008 components installed.

image
image.png811×232 39.9 KB

This box only ever had SQL 2014 installed.

A test SQL server we arre using has SQL 2016 Installed, and has components from 2014, 2012, and 2008.

image
image.png775×239 37.9 KB

Is this normal?

And should my SQL 2016 install have both “SQL Server 2016” and “SQL Server 2016 (64-bit)” ?

Our company’s IT uses a special group for all our DB administration (I think its an outside party, but that’s not important). And they want to know who installed those components, when it was their group that dis the SQL 2016 install on the test server.

If SQL 2016 installs those older components, I’d not have a warm and fuzzy feeling about the competence of the DBA group I have to work with.

2

I know for a fact that my test server and live server have only had 2012. I see 2008 Management Objects and 2008 Support Files still on there.

Also, I only see 64-bit installed.

1 Like
3

if it helps, my 2017 install has all of this - but some of it came from SSDT and VS installations…

image
image.png604×539 195 KB

1 Like
4

@MikeGross -
Looks like SQL 2017 was installed on 5/1/2019. And that seems to be the date for the “older components” (2012 Native Client, 2014 Mngmnt Obj, 2016 LocalDB) as well.

If you don’t mind, can you confirm there aren’t any SQL entries above the “2012 Native Client” one? I seem to have SQL 2008 files on any of my SQL boxes.

5

True - I built this DEV box for my .400 upgrade testing on that date.
Confirmed - nothing above that point, but there are more Visual Studio entries below.

Here is a listing form SQL 2014 with newer SSMS and SSDT tools installed

image
image.png597×698 266 KB

6

Thanks. I’m guessing the 2008 and 2012 components are actually part of 2014 (for some sort of legacy compatibility).

7

Yes they show up on every install by default, just like on the 2017 install. But it’s most likely because I do a FULL install every time which includes all of the ‘backwards compatibility’ components. I do this so I can connect to any version I have installed (linked servers, SSMS, etc.)

I’d be happy to discuss it with anyone on your side if you need me to. I do ALL MY OWN installs and no one else touches my SQL Servers - been doing it for 20 years…

1 Like