01 Oktober 2009 19:05Having downloaded the sql script and batch files from MS necessary to maintain my "internal database" I then downloaded and attempted to install SQLServer2005_SQLCMD.msi so that I have the sqlcmd executable. Howerver, when I attempt to install this msi it indicates that I first need to install the sql 2005 native client. Wow! I do have the native client from my SQL 2005 CDs from other servers but no where in MS's documentation for WSUS db maintenance does it indicate this requirement. Am I doing something wrong?
01 Oktober 2009 20:25Moderator
What you need to download and install is the full SQL Server Management Studio Express which will get you the SQL Native Client along with it.
Alternatively, you can also install the SQL Server Management Studio from your SQL 2005 media kit.
Either of those should also install SQLCMD.exe.
As for the "native client" question... ALL SQL Tools require the SQL Native Client to be installed, so anything that references using the client tools pretty much implies (and presumes) that the SQL Native Client will need to be installed, and most people get SQLCMD by installing SSMS Express, or the full Client Tool kit from the SQL Server media.
Truthfully, I'm not exactly sure why SQLCMD is even provided as a standalone MSI package.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com
- Ditandai sebagai Jawaban oleh Eric Zhang CHNModerator 08 Oktober 2009 7:26
06 Juli 2012 13:24So I installed the full SQL Server Management Studio Express and still no SQLCMD.exe tool. I can connect to WID with the QUI from the SQL Server Management Studio Express using
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query but no SQLCMD.EXE. Try installing the SQLCMD MSI package but still getting the Native Client error.
- Disarankan sebagai Jawaban oleh TH-Hill 06 Juli 2012 14:14
06 Juli 2012 14:21
I found the problem had to install the Sql Server Management Studio Express as Lawrence stated above but also the Microsoft SQL Server Native Client and then the Microsoft SQL Server 2005 Command Line Query Utility http://www.microsoft.com/en-us/download/details.aspx?id=15748 which it clealy tells you if I would just read!Microsoft SQL Server 2005 Command Line Query Utility
The SQLCMD utility allows users to connect, send Transact-SQL batches, and output rowset information from SQL Server 7.0, SQL Server 2000, and SQL Server 2005 instances. SQLCMD is a replacement for ISQL and OSQL, but can coexist with installations that have
ISQL or OSQL installed.
Note: Microsoft SQL Server 2005 Command Line Query Utility requires Microsoft SQL Server Native Client, also available on this page.