/build/static/layout/Breadcrumb_cap_w.png

Will Merge Module in different versions of SQL Native Client cause conflict?

I have to install MS SQL Native Client 9 and 10 onto Citrix Terminal Server, which is on Windows Server 2008 R2. MS Dynamics GP 10 requires SQL Native Client 9 and an other tyre management application called Wheels 3 requires version 10. I opened the SQL Native Client 9 and 10 using Wise, and it looked like they install files and registry keys to different folders. However, regarding CRT merge module, version 10 installs 8.0.50727.42 while version 9 installs 8.0.50727.4027. My questions are about how the merge module behaves when I install the two different versions SQL Native Clients.

1. Will the new version of CRT overwrites the old version if I install the old version first?

2. Will the old version of CRT overwrites the new version if I install the new version first?

3. Can SQL Native Client 9 and 10 co-exist?

Thanks.


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: pjgeutjens 12 years ago
Red Belt
2

A merge module will overwrite files it contains that have a higher version than the ones that are currently on the system, it will not downgrade files. They basically contain components that get added to your MSI when they get imported, and then behave the same way other components do.

So if the merge modules contain the same files the answer to your first 2 questions will be

1) yes

2) no

As for question 3, the native clients 9 and 10 can co-exist on one machine, see also this link: http://blogs.msdn.com/b/sqlnativeclient/archive/2008/02/27/microsoft-sql-server-native-client-and-microsoft-sql-server-2008-native-client.aspx

 


Comments:
  • Thanks for your help! - nbafifa02 12 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ