MS SQL Server
  Home arrow MS SQL Server arrow Page 2 - Using the SQLCMD in SQL 2005 Server
ASP Free Forums 
.NET  
ASP  
ASP Code  
ASP.NET  
ASP.NET Code  
BrainDump  
C#  
Code Examples  
Database  
Database Code  
IIS  
Microsoft Access  
MS SQL Server  
Visual Basic.NET  
Windows Scripting  
Windows Security  
XML  
ASP Web Hosting  
ASP.NET Web Hosting 
Moblin 
JMSL Numerical Library 
Windows Web Hosting
 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
MS SQL SERVER

Using the SQLCMD in SQL 2005 Server
By: Jayaram Krishnaswamy
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 3 stars3 stars3 stars3 stars3 stars / 9
    2006-05-15

    Table of Contents:
  • Using the SQLCMD in SQL 2005 Server
  • On using SQLCMD from the command line
  • SQL Server Network Connections
  • SQL Client Connections
  • A simple example of running an interactive session

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Using the SQLCMD in SQL 2005 Server - On using SQLCMD from the command line


    (Page 2 of 5 )

    One of the requirements for running the SQLCMD from the command line (in a DOS screen) is that the client and the server should be listening on/to the same TCP Port. If they are not, then the command line usage of SQLCMD results in an error as shown. While you do get an error message it is not very helpful. The only clue you get is the two words "TCP provider," if you can correctly guess. I wonder why they did not add another paragraph to this message.

    C:Program FilesMicrosoft SQL Server90Shared>sqlcmd
    HResult 0x274D, Level 16, State 1
    TCP Provider: No connection could be made because the target machine
    actively refused it.
    Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
    establishing a connection to the server. When connecting to SQL Server
    2005, this failure 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 we correct the above condition? 

    Open the SQL Configuration Manager by going through All Programs -> MS SQL Server 2005 -> Configuration Tools -> SQL Server Configuration Manager and click as shown.



    More MS SQL Server Articles
    More By Jayaram Krishnaswamy


       · Commandline access to the program is perhaps one of the nicest features any program...
     

    MS SQL SERVER ARTICLES

    - Completing the Introduction to Transact-SQL
    - A Brief Introduction to Transact-SQL
    - Lookups and Blocking Bad Data
    - Field Validation Rules for Blocking Bad Data
    - Using Masks to Block Bad Data
    - Blocking Bad Data
    - Using @@ROWCOUNT and TABLE Variables for Dat...
    - How to Use Variables, IF and CASE in Databas...
    - Creating Important Aspects of Notification S...
    - Working wth Variables in Database Interactio...
    - Delving Deeper into Notification Services
    - Notification Services
    - Building a Multi-table Report with SQL 2005 ...
    - A Secure Way of Building Connection Strings
    - Transferring a Database Using the SSIS Desig...





    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 1 hosted by Hostway
    Stay green...Green IT