Also have a look at https://www.microsoft.com/en-us/download/details.aspx?id=49999 It is essentially the same information, but refers to SP3 – always good to be on the latest service pack. Just be sure to download the 32-bit version of the driver – “X86 Package”.
Regarding the Windows 10 path limit, it may not be rescinded for all applications: “ "Enabling NTFS long paths will allow manifested win32 applications and Windows Store applications to access paths beyond the normal 260 char limit per node. Enabling this setting will cause the long paths to be accessible within the process."” So you may run into scenarios that still suffer from the old limitation. As well, you may need to set a group policy or do a Registry hack to enable this feature. It seems to be a work in progress and perhaps MS will make it more widely available in future Windows updates.
Best,
Ethan
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Moore, Steven
Sent: Thursday, June 2, 2016 10:25 AM
To: [log in to unmask]
Subject: Re: SQL Server Native Client
Thanks Ethan. That is very helpful. We are going with SQL Server 2014 and the v11 driver which is available below. And to make it even more confusing MS calls it Microsoft® SQL Server® 2012 Native Client.
https://www.microsoft.com/en-us/download/details.aspx?id=29065
On a different note, I read a few days ago that MS is getting rid of the 256 character path limit with Windows Server 2016 and Windows 10 Pro. Should help with the installs.
Steve
Steven Moore
Database Administrator
The Museum of Modern Art (MoMA)
11 West 53 Street ~ New York, NY ~ 10019
[log in to unmask]<mailto:[log in to unmask]>
Phone: 011.33.62.782.1223
[http://thinkbeforeprinting.org/struct/signature-1.gif]
On Thu, Jun 2, 2016 at 10:11 AM, Ethan Kalfus <[log in to unmask]<mailto:[log in to unmask]>> wrote:
Hi Steve,
You will need to upgrade the client machines to the SQL Server Native Client 11 driver. We didn’t do testing with the older driver against later versions of SQL Server and there may well be compatibility issues (syntax, etc.). As well, the newer driver affords performance benefits over the older one, as well as bugs fixes. One caution: there is a similarly named driver that is *not* compatible with TMS -- “ODBC Driver 11 for SQL Server” – you must continue to use the “Native Client” family of drivers.
Another consideration is version of SQL Server itself. We deprecated SQL Server 2008 R2 starting with TMS 2012, so for TMS 2016 we support SQL Server 2012 and 2014.
Hope this helps. Let me know if you have any further questions.
Best,
Ethan
---
Ethan Kalfus | Director, Development
[log in to unmask]<mailto:[log in to unmask]> | 646.733.2239 x232
GallerySystems | www.gallerysystems.com<http://www.gallerysystems.com/>
From: The Museum System (TMS) Users [mailto:[log in to unmask]<mailto:[log in to unmask]>] On Behalf Of Moore, Steven
Sent: Thursday, June 2, 2016 8:54 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: SQL Server Native Client
Does anyone know if it is OK to use SQL Server Native Client 10 (ie, the one we use with TMS 2012) for TMS 2016? Just wondering if I can keep that in place or need to change it to v11 as part of installs. Thanks!
Steve
Steven Moore
Database Administrator
The Museum of Modern Art (MoMA)
11 West 53 Street ~ New York, NY ~ 10019
[log in to unmask]<mailto:[log in to unmask]>
Phone: 011.33.62.782.1223
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
|
