bcp
- A utility used for the interactive
process of bulk coping of data between the SQL Server 2000 instance and data
file (format information file should be specified or a default bcp.fmt
should be used instead). The bcp utility is the typical example of a "two-way"
tool, i.e. copying data "into SQL Server instance" or "out of
SQL Server instance" is allowed. Alternatively, bcp can be used for
copying data:
-
Between SQL Server instances with different
language collations;
-
To or from a view;
-
Returned from a T-SQL query (to data
file);
-
Between the Microsoft SQL Server and
database servers of other vendors;
-
Between the SQL Servers working on
different processor architectures;
-
To or from a database table (including
temporary tables);
-
Between databases within one SQL Server
instance.
The bcp utility is installed by default to the \Program
Files\Microsoft SQL Server\80\Tools\Binn directory.
cdw - The executable for Copy Database Wizard. To copy the database, cdw performs detach and attach
processes on the source database to copy the files to the destination.
Typically, cdw is used for moving databases and their related information into
the clustered, named instance of SQL Server 2000. The cdw
utility is installed to the \Program
Files\Microsoft SQL Server\80\Tools\Binn directory by default .
cmdwrap - This utility is undocumented. The search for any additional information (SQL Server
Books OnLine, Microsoft Technet, MSDN) returned no useful information. It seems
that this utility does not require any command line parameters and is used
internally by the SQL Server setup program. Judging by its name, cmdwrap is
probably used for parsing (Input? Output? Or both?) text strings. The cmdwrap utility is installed to
the \Program Files\Microsoft SQL Server\MSSQL\Binn directory by default .
cnfgsrv
- Another undocumented utility (try to run
it with /? switch - to receive a set of command line parameters which it
accepts). Cnfgsrv is used internally by the SQL Server setup
program, during the configuration of your SQL Server computer. The
cnfgsrv utility is installed to the \Program Files\Microsoft SQL
Server\80\Tools\Binn directory by default.
console
- A utility used to diagnose backup /
restore processes on tape dump devices. The console utility displays information
messages during SQL Server databases back up / restore from tape dump devices. The
console utility
is installed to the \Program Files\Microsoft SQL Server\MSSQL\Binn directory
by default.
dcomscm
- The COM-component, is used to manage /
administer an SQL Server instance and its services state checking. dcomscm - The dcomscm utility is installed to the \Program
Files\Microsoft SQL Server\80\Tools\Binn directory by default.
distrib
- Replication distribution Agent - command
prompt utility, which configures and begins a distribution Agent, which moves
transactions and snapshot jobs held in the distribution database tables to
Subscribers. Huge (!!!) set of command line switches.
distrib utility installed by
default to the \Program Files\Microsoft SQL Server\80\Com directory.
[http://doc.ddart.net/mssql/sql70/4_dist.htm]
dtsrun
- A command line utility used for
retrieving, executing, deleting and overwriting packages, previously created
with the use of Microsoft Data Transformation Services. The DTS packages,
executed by dtsrun can be stored in the Msdb database, a COM-structured
storage file or Microsoft Repository. The dtsrun
utility is installed to the \Program
Files\Microsoft SQL Server\80\Tools\Binn directory by default .
dtsrunui
-The executable
for the DTS Run utility. DTS Run provides a graphical interface for the dtsrun
utility. The dtsrunui utility is installed to the \Program Files\Microsoft
SQLServer\80\Tools\Binn directory by default.
dtswiz
- The utility for running the Data
Transformation Services Import / Export Wizard from a command prompt. Dtswiz
can be used for creating DTS packages that import, export or transform data
among different ODBC-data sources. The dtswiz utility is installed to the \Program Files\Microsoft
SQLServer\80\Tools\Binn directory by default .
dw15
- Dw15 provides the ability to send
application crash information to Microsoft. This utility was introduced first
in SQL Server 2000 Service Pack 3. Dw15 supports applications such as SQL
Server 2000 SP3, that ship with Error Reporting technology. Dw15 announces in a
user dialog box that an error has occurred; if the user chooses to send the
report to Microsoft, it establishes a connection with watson.microsoft.com on
port 80 (using HTTP), and then sends the report securely via port 443 (using
HTTPS). The dw15 utility is installed to the \Program Files\Microsoft
SQLServer\80\Com directory by default.
isql
- A utility for interactive Transact-SQL
scripts and stored procedures execution. It uses the DB-library for
communicating with the database server. isql can be started directly from the
operating system command prompt and uses a standard output device (monitor, by
default) to display results. isql works as a SQL Server 6.5 level client when
connected to SQL Server 2000. The isql
utility is installed to the \Program
Files\Microsoft SQLServer\80\Tools\Binn directory by default.
isqlw
- The executable for SQL Server Query
Analyzer. isqlw can be used with (when valid login information, input and
output files are specified) or without a user interface (if input and output
files are not specified). The isqlw utility is installed to the \Program Files\Microsoft
SQLServer\80\Tools\Binn directory by default.
itwiz
- itwiz allows the Index Tuning Wizard to
be executed from a command prompt. Index tuning using an itwiz is similar to
tuning via Index Tuning Wizard with a user interface. The itwiz
utility is installed to the \Program
Files\Microsoft SQLServer\80\Tools\Binn directory by default.
logread
- logread is used for configuring and starting a Log Reader Agent. All
transactions (marked for replication) move from the transaction log on the
Publisher to the distribution database. The logread utility is installed
to the \Program Files\Microsoft SQLServer\80\Com directory by default.
makepipe - A diagnostic utility used for the network Named Pipe
services "checks-if-it-is-working" integrity testing. The makepipe
utility should be launched at the database server console and it expects a connection
from readpipe, started at problem SQL-client console. After makepipe is
started, the database server waits for a client to connect. In other words, makepipe
is used in conjunction
with the readpipe utility. This utility is no longer installed by SQL Server 2000
Setup. If you need to run it - please do this manually from the \x86\Binn
directory on the SQL Server 2000 compact disc, or manually copy it to any
location.
odbccmpt - A migration assistance
utility that enables or disables the 2.65 SQL Server ODBC driver support. Odbccmpt should be used
ONLY (!!!) for applications having problems in porting to Microsoft SQL Server
2000 (and 3.7 SQL Server ODBC driver). The odbccmpt utility is installed
to the \Program Files\Microsoft SQLServer\80\Tools\Binn directory by default.
odbcping - A diagnostic utility that every DBA (in case ODBC
related connection problems should appear) should use for testing ODBC data
source integrity and the ability of successful connection between SQL-client
and database server. This
utility is no longer installed by SQL Server 2000 Setup. If you need to run it
- please do this manually from the \x86\Binn directory on the SQL Server 2000
compact disc, or manually copy it to any location.
osql - A utility for interactive Transact-SQL scripts and
stored procedures execution. It uses ODBC libraries for communicating with the database
server. Osql can be started directly from the operating system command prompt
and uses a standard output device (monitor, by default) for displaying results. The osql
utility is installed to the \Program
Files\Microsoft SQLServer\80\Tools\Binn directory by default.
Part one of this two part series has introduced tools hidden in every SQL Server 2000 installation, with the primary focus being an introduction to the SQL Server command line utilities. The next installment will continue our examination of these utilities.
»
See All Articles by Columnist Alexzander Nepomnjashiy
» 