dbTalk Databases Forums  

Using SQLCMD to test Connection

Go Back dbTalk Databases Forums Databases microsoft.public.sqlserver.clients Using SQLCMD to test Connection

microsoft.public.sqlserver.clients microsoft.public.sqlserver.clients


Discuss Using SQLCMD to test Connection in the microsoft.public.sqlserver.clients forum.



Reply
Page 1 of 10 1 2 3 4 5 6 7 8 9 10 >
 
Thread Tools Display Modes
  #1  
Old   
Rubens
 
Posts: n/a

Default Using SQLCMD to test Connection - 03-02-2008 , 07:20 PM





I am using the following comand to test a SQL 2005 connection, but I seem to
have the syntax incorrect.

SQLCMD -Stcp:ServerName,1433 -E

What am I doing wrong?

Thanks,
Rubens

Reply With Quote
  #2  
Old   
Tibor Karaszi
 
Posts: n/a

Default Re: Using SQLCMD to test Connection - 03-03-2008 , 02:32 AM





You don't specify tcp:. Try:

SQLCMD -SServerName,1433 -E

Also, assuming the server is a default instance, then no need to specify a port (if you don't
specify an instance name, like ServerName\InstanceName, then 1433 is assumed and is a well-known
port for SQL Server).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rubens" <Rubens (AT) discussions (DOT) microsoft.com> wrote

Quote:
I am using the following comand to test a SQL 2005 connection, but I seem to
have the syntax incorrect.

SQLCMD -Stcp:ServerName,1433 -E

What am I doing wrong?

Thanks,
Rubens


Reply With Quote
  #3  
Old   
Tibor Karaszi
 
Posts: n/a

Default Re: Using SQLCMD to test Connection - 03-03-2008 , 02:32 AM


You don't specify tcp:. Try:

SQLCMD -SServerName,1433 -E

Also, assuming the server is a default instance, then no need to specify a port (if you don't
specify an instance name, like ServerName\InstanceName, then 1433 is assumed and is a well-known
port for SQL Server).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rubens" <Rubens (AT) discussions (DOT) microsoft.com> wrote

Quote:
I am using the following comand to test a SQL 2005 connection, but I seem to
have the syntax incorrect.

SQLCMD -Stcp:ServerName,1433 -E

What am I doing wrong?

Thanks,
Rubens


Reply With Quote
  #4  
Old   
Tibor Karaszi
 
Posts: n/a

Default Re: Using SQLCMD to test Connection - 03-03-2008 , 02:32 AM


You don't specify tcp:. Try:

SQLCMD -SServerName,1433 -E

Also, assuming the server is a default instance, then no need to specify a port (if you don't
specify an instance name, like ServerName\InstanceName, then 1433 is assumed and is a well-known
port for SQL Server).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rubens" <Rubens (AT) discussions (DOT) microsoft.com> wrote

Quote:
I am using the following comand to test a SQL 2005 connection, but I seem to
have the syntax incorrect.

SQLCMD -Stcp:ServerName,1433 -E

What am I doing wrong?

Thanks,
Rubens


Reply With Quote
  #5  
Old   
Tibor Karaszi
 
Posts: n/a

Default Re: Using SQLCMD to test Connection - 03-03-2008 , 02:32 AM


You don't specify tcp:. Try:

SQLCMD -SServerName,1433 -E

Also, assuming the server is a default instance, then no need to specify a port (if you don't
specify an instance name, like ServerName\InstanceName, then 1433 is assumed and is a well-known
port for SQL Server).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rubens" <Rubens (AT) discussions (DOT) microsoft.com> wrote

Quote:
I am using the following comand to test a SQL 2005 connection, but I seem to
have the syntax incorrect.

SQLCMD -Stcp:ServerName,1433 -E

What am I doing wrong?

Thanks,
Rubens


Reply With Quote
  #6  
Old   
Tibor Karaszi
 
Posts: n/a

Default Re: Using SQLCMD to test Connection - 03-03-2008 , 02:32 AM


You don't specify tcp:. Try:

SQLCMD -SServerName,1433 -E

Also, assuming the server is a default instance, then no need to specify a port (if you don't
specify an instance name, like ServerName\InstanceName, then 1433 is assumed and is a well-known
port for SQL Server).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rubens" <Rubens (AT) discussions (DOT) microsoft.com> wrote

Quote:
I am using the following comand to test a SQL 2005 connection, but I seem to
have the syntax incorrect.

SQLCMD -Stcp:ServerName,1433 -E

What am I doing wrong?

Thanks,
Rubens


Reply With Quote
  #7  
Old   
Tibor Karaszi
 
Posts: n/a

Default Re: Using SQLCMD to test Connection - 03-03-2008 , 02:32 AM


You don't specify tcp:. Try:

SQLCMD -SServerName,1433 -E

Also, assuming the server is a default instance, then no need to specify a port (if you don't
specify an instance name, like ServerName\InstanceName, then 1433 is assumed and is a well-known
port for SQL Server).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rubens" <Rubens (AT) discussions (DOT) microsoft.com> wrote

Quote:
I am using the following comand to test a SQL 2005 connection, but I seem to
have the syntax incorrect.

SQLCMD -Stcp:ServerName,1433 -E

What am I doing wrong?

Thanks,
Rubens


Reply With Quote
  #8  
Old   
Tibor Karaszi
 
Posts: n/a

Default Re: Using SQLCMD to test Connection - 03-03-2008 , 02:32 AM


You don't specify tcp:. Try:

SQLCMD -SServerName,1433 -E

Also, assuming the server is a default instance, then no need to specify a port (if you don't
specify an instance name, like ServerName\InstanceName, then 1433 is assumed and is a well-known
port for SQL Server).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rubens" <Rubens (AT) discussions (DOT) microsoft.com> wrote

Quote:
I am using the following comand to test a SQL 2005 connection, but I seem to
have the syntax incorrect.

SQLCMD -Stcp:ServerName,1433 -E

What am I doing wrong?

Thanks,
Rubens


Reply With Quote
  #9  
Old   
Tibor Karaszi
 
Posts: n/a

Default Re: Using SQLCMD to test Connection - 03-03-2008 , 02:32 AM


You don't specify tcp:. Try:

SQLCMD -SServerName,1433 -E

Also, assuming the server is a default instance, then no need to specify a port (if you don't
specify an instance name, like ServerName\InstanceName, then 1433 is assumed and is a well-known
port for SQL Server).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rubens" <Rubens (AT) discussions (DOT) microsoft.com> wrote

Quote:
I am using the following comand to test a SQL 2005 connection, but I seem to
have the syntax incorrect.

SQLCMD -Stcp:ServerName,1433 -E

What am I doing wrong?

Thanks,
Rubens


Reply With Quote
  #10  
Old   
Tibor Karaszi
 
Posts: n/a

Default Re: Using SQLCMD to test Connection - 03-03-2008 , 02:32 AM


You don't specify tcp:. Try:

SQLCMD -SServerName,1433 -E

Also, assuming the server is a default instance, then no need to specify a port (if you don't
specify an instance name, like ServerName\InstanceName, then 1433 is assumed and is a well-known
port for SQL Server).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rubens" <Rubens (AT) discussions (DOT) microsoft.com> wrote

Quote:
I am using the following comand to test a SQL 2005 connection, but I seem to
have the syntax incorrect.

SQLCMD -Stcp:ServerName,1433 -E

What am I doing wrong?

Thanks,
Rubens


Reply With Quote
Reply
Page 1 of 10 1 2 3 4 5 6 7 8 9 10 >

« Previous Thread | Next Thread »



Thread Tools
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.


Contact Us - dbTalk Databases Forums - Archive - Top