January 10, 2018 at 2:23 pm
We upgrade our server from SQL server 2014 to 2017.
I upgraded SSIS 2014 to 2017 by mainly change the connection string from Provider=SQLNCLI11; to Provider=SQLNCLI11.1.
I found somewhere says 2017 SSIS use 11.1 version. But I cannot find where I found this information.
Is there a way or website document that tells which version of SQL server like use which version of native client.
I cannot find it.
Does it matter I use SQLNCLI11.1. or SQLNCLI11 for the connection string on SQL server 2017 and SSIS 2017?
Thanks
January 10, 2018 at 3:51 pm
sqlfriends - Wednesday, January 10, 2018 2:23 PMWe upgrade our server from SQL server 2014 to 2017.I upgraded SSIS 2014 to 2017 by mainly change the connection string from Provider=SQLNCLI11; to Provider=SQLNCLI11.1.
I found somewhere says 2017 SSIS use 11.1 version. But I cannot find where I found this information.
Is there a way or website document that tells which version of SQL server like use which version of native client.
I cannot find it.
Does it matter I use SQLNCLI11.1. or SQLNCLI11 for the connection string on SQL server 2017 and SSIS 2017?Thanks
I'd like to know where that documentation would be as well. I did try finding info a couple of week ago - on some other forums there were a few posts about 11.1 and I remember one poster saying that their errors with the 11.0 driver and SSIS went away when they switched to 11.1
I had checked the SQLCLi team blog - you'd think they'd have it there but nothing has been updated yet as I just checked after seeing your post. I would guess it's still related to their last post though - if you want to check it here is the link:
Announcing the new release of OLE DB Driver for SQL Server
Seems they managed to make a lot of this a mess...depreciate, undepreciate, new version and no documentation.....
Sue
January 10, 2018 at 4:46 pm
Thanks,
For now, I would like to know if it matters if use one vs the other.
In the connection manager -all tab, there is a provider that shows 11.1.
There is a sceenshot in this article shows that even this article is not related much to this post.
https://www.virtual-dba.com/ssis-package-connection-timeout-unlimited/
January 10, 2018 at 5:39 pm
sqlfriends - Wednesday, January 10, 2018 4:46 PMThanks,
For now, I would like to know if it matters if use one vs the other.
In the connection manager -all tab, there is a provider that shows 11.1.There is a sceenshot in this article shows that even this article is not related much to this post.
https://www.virtual-dba.com/ssis-package-connection-timeout-unlimited/
If 11.1 was installed with 2017 and all of the components it really shouldn't be an issue.
Sue
January 11, 2018 at 9:57 am
The problem is I don't know what is installed. 11 or 11.1
From ODBC driver I can see it is 11. From SSMS - server management - linked server- provider I can see it is also 11.
Only on the screen of the last post it is 11.1. it is the screen on the All tab in the connection manager of OLDEB.
So not sure what version is installed and how to check it.
Thanks
January 11, 2018 at 10:09 am
sqlfriends - Thursday, January 11, 2018 9:57 AMThe problem is I don't know what is installed. 11 or 11.1From ODBC driver I can see it is 11. From SSMS - server management - linked server- provider I can see it is also 11.
Only on the screen of the last post it is 11.1. it is the screen on the All tab in the connection manager of OLDEB.
So not sure what version is installed and how to check it.
Thanks
You can find the dlls for the drivers in the Windows\System32 folder. Then in that folder, search for: sqlncli*.dll
That should pull up the sql native client drivers. You can right click on the dlls and select properties, then details and the Product Version should have the full build number to see what you have.
Sue
January 11, 2018 at 10:56 am
In the folder I found it is 11.
But on the connecition manager there is also a 11.1.
See attached screenshot.
January 11, 2018 at 11:02 am
sqlfriends - Thursday, January 11, 2018 10:56 AMIn the folder I found it is 11.
But on the connecition manager there is also a 11.1.See attached screenshot.
Those are both 11.0.
Sue
January 11, 2018 at 11:05 am
Sorry, you might see the one I posted before I updated.
Can you refresh to see the second attachment? it says 11.1
January 11, 2018 at 1:15 pm
sqlfriends - Thursday, January 11, 2018 11:05 AMSorry, you might see the one I posted before I updated.
Can you refresh to see the second attachment? it says 11.1
Thanks...yup I see that. Weird since you don't have an 11.1 version so it could just be a display things since those seem to be screwed up in a lot of places these days.
I'd play around and test packages with whatever it used as the default - 11.1 right? Just do a couple basic packages. Then what I would try (and I am assuming your on a Dev) is moving the 11.0 driver to some odd folder, rerun one of the packages and see if it craps out on you. If it does, that's likely the dll it was pointing to.
Sue
January 11, 2018 at 2:02 pm
I read somewhere on the web they both point to the same DDL.
January 11, 2018 at 2:24 pm
sqlfriends - Thursday, January 11, 2018 2:02 PMI read somewhere on the web they both point to the same DDL.
I ran across some reference to that as well somewhere. I think we ran across the same articles. That's a good test though in terms of the moving the dll.
I'm pretty sure it is just pointing to that 11.0 dll but cant say for sure. I'm wondering if things look like 11.1 just due to rounding the full product number.
Take a look - it would round up to 11.1. 🙂
Sue
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply