SQL
Server Command Line Tools to Manage Your Server
Problem
There are several useful commands and functions that are available in SQL Server, but not knowing what they are or where to find more information about them is sometimes a problem. Having these commands at your fingertips is very helpful when trying to solve a problem or for just doing general analysis on your database instances.
There are several useful commands and functions that are available in SQL Server, but not knowing what they are or where to find more information about them is sometimes a problem. Having these commands at your fingertips is very helpful when trying to solve a problem or for just doing general analysis on your database instances.
Solution
Following is a list of useful commands that can be run using Query Analyzer. A lot of this information can be retrieved using Enterprise Manager, but it is often faster to use these commands directly in Query Analyzer as well as more detailed information is provided. Each of these commands has different functionality and knowing that the command exists and what types of information they produce is extremely helpful in managing your SQL Server environment
Following is a list of useful commands that can be run using Query Analyzer. A lot of this information can be retrieved using Enterprise Manager, but it is often faster to use these commands directly in Query Analyzer as well as more detailed information is provided. Each of these commands has different functionality and knowing that the command exists and what types of information they produce is extremely helpful in managing your SQL Server environment
|
Command
|
Purpose
|
Sample Usage
|
|
This gives you information about
all databases in the instance or specific information about one database.
|
|
|
|
This command will show you the
number of read and writes to a data file. Use sp_helpdb with the
database name to see the logical file numbers for the data files and the
database id.
|
|
|
|
fn_get_sql()
|
Returns the text of the SQL
statement for the specified SQL handle. This is similar to using DBCC
INPUTBUFFER, but this command will show you additional information.
This can also be embedded in a process easier then using the DBCC command
|
|
|
This command shows you all of the
locks that the system is currently tracking This is similar to
information you can see in Enterprise Manager.
|
|
|
|
This command gives you information
about the objects within a database. The command without an objectname
will give you a list of all objects within the database.
|
|
|
|
Gives you process information
similar to what you see when using Enterprise Manager.
|
|
|
|
Gives you information about the
indexes on a table as well as the columns used for the index.
|
|
|
|
This command shows you how much
space has been allocated for the database (or if specified an object) and how
much space is being used.
|
|
|
|
DBCC CACHESTATS
|
Displays information about the
objects currently in the buffer cache.
|
|
|
This will check the allocation of
all pages in the database as well as check for any integrity issues.
|
|
|
|
This will check the allocation of
all pages for a specific table or index as well as check for any integrity
issues.
|
|
|
|
This command will reindex your
table. If the indexname is left out then all indexes are rebuilt.
If the fillfactor is set to 0 then this will use the original fillfactor when
the table was created.
|
|
|
|
This command will show you
information about the procedure cache and how much is being used.
Spotlight will also show you this same information.
|
|
|
|
DBCC MEMORYSTATUS
|
Displays how the SQL Server buffer
cache is divided up, including buffer activity.
|
|
|
This command gives you information
about how much space is used for a table and indexes. Information
provided includes number of pages used as well as how fragmented the data is
in the database.
|
|
|
|
This will show how statistics are
laid out for an index. You can see how distributed the data is and
whether the index is really a good candidate or not.
|
|
|
|
This will allow you to shrink one
of the database files. This is equivalent to doing a database shrink, but you
can specify what file and the size to shrink it to. Use the sp_helpdb
command along with the database name to see the actual file names used.
|
|
|
|
This command will show you much of
the transaction logs are being used.
|
|
|
|
This command will turn on a trace
flag to capture events in the error log. Trace Flag 1204 captures Deadlock
information.
|
|
|
|
This command turns off a trace
flag.
|
|