Re: SQLCMD installation

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Hey, this is just what I wanted to know. I am taking a course in Database
Management. We are learning SQL as a part of this course (or at least we
would like to learn SQL). The computers we have in the labs are running
Microsoft XP. I noticed on these computers that they have Microsoft SQL on
them. And I noticed using the Task Manager that SQL server is running
(sqlservr.exe, sqlbrowser.exe, and sqlwriter.exe are all listed under
processes) But I can't get this to run. I looked at the newsgroups and
discovered that there is this program called sqlcmd.exe. Why can't I use
these SQL servers to try to practice using SQL. I have downloaded MySQL on
my computer at home, and you can interact with it from the command prompt.
You can type things like "show tables" and you get a list of tables. I'd like
to be able to do that kind of thing here on these machines. When I try
running sqlcmd.exe, I get error messages:
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

How do I get access to the SQL server so that I can try out SQL? I know
this is quite probably another episode in hopelessness, trying to get this to
work (I mean, why would a university allow their students who are taking a
course in Database Management, which specifically talks about SQL, actually
use the SQL on the computers they set up in the computer labs for us to use?).

"Lawrence Garvin" wrote:

"Maria Bravo" <MariaBravo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BEB945DB-0268-4073-9AA9-1DD773B38EC6@xxxxxxxxxxxxxxxx
I have MS sqlserver 2005, and want to install a client in a PC. I expect
the
SQLCMD to be installed, but the installation finishes and the SQL comand
line
program does not exist in the client. What is the procedure to have it
install, and test that is working fine?

SQLCMD.EXE is installed as part of the core SQL Server installation, but
it's not pathed by default.

You'll find it at C:\Program Files\Microsoft SQL Server\90\Tools\Binn.

You'll need to either change to that directory, or add the folder to your
path declaration.


--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas



.



Relevant Pages

  • Re: SQL Server 2005 Cluster Setup Quiz
    ... SQL Server 2005 failover cluster has been installed? ... drive of a SQL Server 2005 failover cluster installation? ...
    (microsoft.public.sqlserver.clustering)
  • Missing DLL during re-installation
    ... The installation appeared to complete successfully and I ... SQL Server Setup failed to execute a command for server configuration. ... Refer to the server error logs and Setup ...
    (microsoft.public.sqlserver.setup)
  • Re: Solution to do Accent Insensitive Full Text Search with SQL Server 2000
    ... Also note that SQL 2005 does support accent insensitive searching. ... Looking for a SQL Server replication book? ... Installing an accent insensitive version of Microsoft Search ... This is the installation program we will use to ...
    (microsoft.public.sqlserver.fulltext)
  • =?iso-8859-1?Q?Re:_Installation_von_SQL-Server_Expres_schl=F6gt_fehl?=
    ... dass bei der Installation von Visual Studio eine SQL Server Express Instance installiert wird?! ... Falls du vor der Installation von Inventor schon VS installiert hattest, musste die SQL Express Installation fehlschalgen! ...
    (microsoft.public.de.sqlserver)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)