MS SQL Server
  Home arrow MS SQL Server arrow Page 4 - 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 
Mobile Linux 
App Generation ROI 
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 - SQL Client Connections


    (Page 4 of 5 )

    Close out of the SQL Server Network Connections, click on the SQL Client Configuration and expand the node to reveal the TCP node in the right pane. Right click on the TCP node to reveal the properties as shown in the next picture. You will see that the port it is listening to is different; it is 1433. Change this to 1037. Click on the button Apply and then click Ok. Close out of the configuration tool.

    Did it fix the problem?

    Go back to the DOS screen and run the SQLCMD command again. You will see that you are rocking now. Both OSQL and SQLCMD will work, the former implemented for backward compatibility with legacy scripts. They in no way interfere with one another. When SQLCMD is invoked from the command line it accesses the server via OleDB, whereas when it is invoked in the SQL Server Management Studio, it uses the .NET SQL Client.

    C:Program FilesMicrosoft SQL Server90Shared>sqlcmd
    1> exit
    C:Program FilesMicrosoft SQL Server90Shared>osql
    Error: No user selected. Try with -U or -E switches
    C:Program FilesMicrosoft SQL Server90Shared>osql -E
    1>
    SQLCMD command line arguments
    

    You can easily get a listing of the command-line arguments by typing in:

    C:sqlcmd -?

    as shown below:

    C:Documents and Settings>sqlcmd -?
    Microsoft (R) SQL Server Command Line Tool
    Version 9.00.1399.06 NT INTEL X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    usage: Sqlcmd           [-U login id]       [-P password]
    [-S server]            [-H hostname]       [-E trusted connection]
    [-d use database name] [-l login timeout]  [-t query timeout]
    [-h headers]           [-s colseparator]   [-w screen width]
    [-a packetsize]        [-e echo input]     [-I Enable Quoted Identifiers]
    [-c cmdend]            [-L[c] list servers[clean output]]
    [-q "cmdline query"]   [-Q "cmdline query" and exit]
    [-m errorlevel]        [-V severitylevel]  [-W remove trailing spaces]
    [-u unicode output]    [-r[0|1] msgs to stderr]
    [-i inputfile]         [-o outputfile]     [-z new password]
    [-f
    | i:
    [,o:
    ]] [-Z new password and exit]
    [-k[1|2] remove[replace] control characters]
    [-y variable length type display width]
    [-Y fixed length type display width]
    [-p[1] print statistics[colon format]]
    [-R use client regional setting]
    [-b On error batch abort]
    [-v var = "value"...]  [-A dedicated admin connection]
    [-X[1] disable commands, startup script, environment variables [and exit]]
    [-x disable variable substitution]
    [-? show syntax summary]

    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 6 hosted by Hostway
    Stay green...Green IT