%3CLINGO-SUB%20id%3D%22lingo-sub-318605%22%20slang%3D%22en-US%22%3EGetting%20the%20latest%20SQL%20Server%20Native%20Client%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-318605%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Jul%2014%2C%202015%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CIFRAME%20frameborder%3D%220%22%20height%3D%22315%22%20src%3D%22https%3A%2F%2Fwww.youtube.com%2Fembed%2F4PWkg6cyjoc%3Flist%3DPLv2BtOtLblH0lZ3pFS6C0_s77kPpV99HW%22%20width%3D%22560%22%3E%20%3C%2FIFRAME%3E%3CP%3EIf%20you%20are%20installing%20a%20Service%20Pack%20(SP)%20or%20Cumulative%20Update%20(CU)%20for%20SQL%20Server%2C%20you%20may%20notice%20that%20the%20SQL%20Server%20Native%20Client%20doesn%E2%80%99t%20get%20updated.%26nbsp%3B%20It%20may%20also%20be%20difficult%20to%20find%20the%20item%20to%20actually%20get%20it%20updated.%3C%2FP%3E%0A%20%20%3CP%3EIf%20you%20go%20look%20at%20the%20Feature%20Packs%20for%20the%20Service%20Packs%2C%20or%20go%20look%20at%20the%20Cumulative%20Update%20downloads%2C%20the%20sqlncli.msi%20package%20may%20not%20be%20listed%20there.%26nbsp%3B%20So%2C%20how%20do%20you%20get%20it%3F%3C%2FP%3E%0A%20%20%3CH2%20id%3D%22toc-hId-1674403153%22%20id%3D%22toc-hId-1733336446%22%3EGet%20it%20from%20the%20SP%20or%20CU%20Package%3C%2FH2%3E%0A%20%20%3CP%3EWhen%20you%20go%20to%20run%20the%20SP%20or%20CU%20Package%2C%20it%20will%20self%20extract%20to%20a%20GUID%20folder.%26nbsp%3B%20When%20it%20is%20done%20self%20extracting%2C%20you%20will%20see%20the%20SQL%20Setup%20landing%20page.%26nbsp%3B%20I%20actually%20want%20to%20ignore%20the%20Setup%20landing%20page%20for%20this.%26nbsp%3B%20But%20while%20that%20is%20there%2C%20we%20can%20go%20into%20Explorer%20and%20browse%20to%20the%20GUID%20folder.%3C%2FP%3E%0A%20%20%3CBLOCKQUOTE%3E%0A%20%20%20%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F68333i5CF6470BC77F7D55%22%20%2F%3E%3C%2FP%3E%0A%20%20%3C%2FBLOCKQUOTE%3E%0A%20%20%3CP%3EFrom%20there%2C%20you%20will%20want%20to%20go%20to%20the%20region%20folder%20that%20matches%20your%20region.%26nbsp%3B%20For%20me%2C%20it%20will%20be%20the%201033%20folder.%3C%2FP%3E%0A%20%20%3CBLOCKQUOTE%3E%0A%20%20%20%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F68334iE99F43F04937A9CE%22%20%2F%3E%3C%2FP%3E%0A%20%20%3C%2FBLOCKQUOTE%3E%0A%20%20%3CP%3EFrom%20there%2C%20we%20can%20go%20to%20%5Cx64%5Csetup%5Cx64%20and%20you%20should%20see%20the%20sqlnsli.msi%20there.%26nbsp%3B%20If%20you%20are%2032bit%2C%20it%20will%20be%20an%20x86%20folder.%3C%2FP%3E%0A%20%20%3CBLOCKQUOTE%3E%0A%20%20%20%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F68335i3D459684F3524F28%22%20%2F%3E%3C%2FP%3E%0A%20%20%3C%2FBLOCKQUOTE%3E%0A%20%20%3CP%3EFrom%20there%2C%20you%20can%20copy%20the%20MSI%20out%20to%20where%20ever%20you%20need%20to%20run%20it%20at.%3C%2FP%3E%0A%20%20%3CP%3EIf%20you%20are%20looking%20for%20the%2032bit%20SQL%20Server%20Native%20Client%2C%20but%20are%20running%20on%20a%20x64%20machine%2C%20use%20the%20x64%20MSI.%26nbsp%3B%20It%20will%20lay%20down%20both%20the%2032bit%20and%2064bit%20Driver%2FProvider.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EAdam%20W.%20Saxton%20%7C%20Microsoft%20Business%20Intelligence%20Support%20-%20Escalation%20Services%20%3CBR%20%2F%3E%20%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2Fguyinacube%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20%40GuyInACube%20%3C%2FA%3E%20%7C%20%3CA%20href%3D%22https%3A%2F%2Fwww.youtube.com%2Fchannel%2FUCFp1vaKzpfvoGai0vE5VJ0w%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20YouTube%20%3C%2FA%3E%20%7C%20%3CA%20href%3D%22https%3A%2F%2Fwww.facebook.com%2FGuyInACube%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Facebook.com%5Cguyinacube%3C%2FA%3E%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-318605%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Jul%2014%2C%202015%20If%20you%20are%20installing%20a%20Service%20Pack%20(SP)%20or%20Cumulative%20Update%20(CU)%20for%20SQL%20Server%2C%20you%20may%20notice%20that%20the%20SQL%20Server%20Native%20Client%20doesn%E2%80%99t%20get%20updated.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-318605%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Econnectivity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Epatching%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft
First published on MSDN on Jul 14, 2015

If you are installing a Service Pack (SP) or Cumulative Update (CU) for SQL Server, you may notice that the SQL Server Native Client doesn’t get updated.  It may also be difficult to find the item to actually get it updated.

If you go look at the Feature Packs for the Service Packs, or go look at the Cumulative Update downloads, the sqlncli.msi package may not be listed there.  So, how do you get it?

Get it from the SP or CU Package

When you go to run the SP or CU Package, it will self extract to a GUID folder.  When it is done self extracting, you will see the SQL Setup landing page.  I actually want to ignore the Setup landing page for this.  But while that is there, we can go into Explorer and browse to the GUID folder.

From there, you will want to go to the region folder that matches your region.  For me, it will be the 1033 folder.

From there, we can go to \x64\setup\x64 and you should see the sqlnsli.msi there.  If you are 32bit, it will be an x86 folder.

From there, you can copy the MSI out to where ever you need to run it at.

If you are looking for the 32bit SQL Server Native Client, but are running on a x64 machine, use the x64 MSI.  It will lay down both the 32bit and 64bit Driver/Provider.

Adam W. Saxton | Microsoft Business Intelligence Support - Escalation Services
@GuyInACube | YouTube | Facebook.com\guyinacube