Cisco TMS SQL DATABASE User manual

Cisco TMS SQL Database
Product Configuration Guide
December 2010
D14216.01

Table of contents
Cisco TMS Database Knowledge Tips Page 2 of 35
Table of contents
Tip format....................................................................................................................................................5
TIP T100 –Different types of SQL Server...................................................................................................6
Extra reference links............................................................................................................................6
TIP T101 –SQL Server management tools .........................................................................................7
Extra reference links............................................................................................................................7
TIP T103 –SQL Versions bundled with Cisco TMS....................................................................................8
TIP T104 –Cisco TMS SQL version compatibility.......................................................................................9
TIP T105 –Cisco TMS database and files................................................................................................10
TIP T106 –The SQL Server instance........................................................................................................11
TIP T107 – Identifying the SQL Server instance name ............................................................................12
TIP T108 –SQL authentication modes......................................................................................................13
Extra reference links..........................................................................................................................13
Tip T109 –When do I need a full version of SQL?....................................................................................14
Extra reference links..........................................................................................................................14
TIP T109 –Using osql for Cisco TMS tasks..............................................................................................15
Simple examples for Cisco TMS use ................................................................................................16
Extra reference links..........................................................................................................................16
TIP T200 –Enabling remote access to SQL .............................................................................................17
Extra reference links..........................................................................................................................17
TIP T201 –SQL Server 2005 and firewalls...............................................................................................18
Possible scenarios.............................................................................................................................18
Using Windows Firewall for a single instance ...................................................................................18
Using Windows Firewall for multiple instances .................................................................................18
Extra reference links..........................................................................................................................19
TIP T202 –SQL Server 2000 and Firewalls..............................................................................................20
Possible Scenarios............................................................................................................................20
Using Windows Firewall for single instance ......................................................................................20
Using Windows Firewall for multiple instances .................................................................................20
To find the port a SQL Server instance is currently using:................................................................20
Extra reference links..........................................................................................................................21
TIP T300 –Backing up the Cisco TMS Database using osql....................................................................22
Extra reference links..........................................................................................................................22
TIP T301 –Restoring the Cisco TMS Database using osql ......................................................................23
Restoring a database to the same SQL server .................................................................................23
Restoring a database to a different SQL server................................................................................23
Extra reference links..........................................................................................................................24
TIP T302 –Automating backups with SQL 2005 Express.........................................................................25
Extra reference links..........................................................................................................................26
TIP T303 –Detaching and reattaching databases ....................................................................................27
To detach the Cisco TMS database using osql.................................................................................27
To attach the Cisco TMS database using osql..................................................................................27
Extra reference links..........................................................................................................................27
TIP T304 –Upgrading MSDE 2000 to SQL 2005 Express........................................................................28
Cisco TMS customers running MSDE 2000 and Cisco TMS versions 9.0 through 10.0...................28
Cisco TMS Customers running MSDE 2000 and Cisco TMS Versions 11.0 through 11.9.1............29
Alternative 1 – Install SQL Server manually......................................................................................29

Table of contents
Cisco TMS Database Knowledge Tips Page 3 of 35
Pros ...................................................................................................................................................29
Cons ..................................................................................................................................................30
Alternative 2 – Use Cisco TMS Installer to install SQL Server..........................................................31
Pros ...................................................................................................................................................31
Cons ..................................................................................................................................................31
SQL code to update indexes and statistics .......................................................................................32
Extra reference links..........................................................................................................................33
TIP T305 –Resetting/changing/forgotten sa password.............................................................................34
Extra reference links..........................................................................................................................34

Document revision history
Revision 1.0 Initial Release of Document
Revision 1.1 Applied Cisco techdocs template, product names changed, TANDBERG
references changed to Cisco
Revision 1.2 Applied new Cisco product names
Revision 1.3 2
nd
stage rebranding

Introduction
Cisco TMS Database Knowledge Tips Page 5 of 35
Introduction
This document is a collection of various tips for Cisco TelePresence Management Suite (Cisco TMS)
administrators working with SQL backend databases. Because Cisco TMS uses a standard SQL server
for its database, there are many tools and methods available to complete tasks. Many of these tasks can
be completed in several different ways or with different commands. These tips are not written to be
taken as the only way to achieve a goal – simply as a verified way so that Cisco TMS owners who are
not as familiar with SQL or its management tools have easy references.
Tip format
Each Tip will be numbered for each reference. You can click on any tip number to jump to that tip.
Each tip will specify the version of Cisco TMS and SQL Server version it applies to. Due to changes in
Cisco TMS and requirements, not all tips will apply to all installations.
Tip information is limited to Cisco TMS versions 9.0 or newer for clarity purposes

Tips category – General
Cisco TMS Database Knowledge Tips Page 6 of 35
Tips category – General
TIP T100 –Different types of SQL Server
Cisco TMS Versions SQL Server Versions
All
SQL v7 – All Versions
MSDE – All Versions
SQL 2000 – All Versions
MSDE 2000 – All Versions
SQL 2005 – All Versions
SQL 2005 Express – All Versions
Microsoft has produced many versions of their SQL Server. The ones most significant in regards to
Cisco TMS have been:
 SQL Server v7 – Introduced 1998 – Full featured version. Replaced by SQL Server 2000
 MSDE – Microsoft Database Engine – Same Engine as SQL v7 – Freely distributable version
intended for software integrators. Replaced by MSDE 2000
 SQL Server 2000 – Introduced 2000 – Full featured version. Replaced by SQL Server 2005
 MSDE 2000 –MSDE product based on the SQL 2000 Engine - Freely distributable version intended
for software integrators. Replaced by SQL Server 2005 Express
 SQL Server 2005 – Introduced 2005 – Full featured version.
 SQL Server 2005 Express – Freely distributable version based on the SQL 2005 Engine
 SQL Server 2008 – Microsoft’s next SQL Server release – slated for 2008 release.
Each fully featured version of SQL was sold in several variants which varied support for amount of
memory, processors, add-on features, etc. Cisco TMS requirements did not require more than the
‘Standard’ edition for fully featured SQL Servers.
The MSDE and Express variants use the same database engine as their fully featured versions but have
specific performance throttles and features removed. The performance limits may be significant to Cisco
TMS depending on the size and type of Cisco TMS installation. See ‘Tip T109 –When do I need a full
version of SQL?’for additional information.
Extra reference links
Comparison of SQL Server 2005 Editions
SQL Server 2005 Express Download

Tips category – General
Cisco TMS Database Knowledge Tips Page 7 of 35
TIP T101 –SQL Server management tools
Cisco TMS Versions SQL Server Versions
All
SQL v7 – All Versions
MSDE – All Versions
SQL 2000 – All Versions
MSDE 2000 – All Versions
SQL 2005 – All Versions
SQL 2005 Express – All Versions
Microsoft provides both graphical and command line interfaces to manage the SQL Server. In general, a
tools installed by a newer server version can control an older version, but not vice versa. Management
tools are automatically installed on the server where SQL Server is installed. Client-only tools can be
installed on other computers to control SQL Servers Remotely.
 osql – command line tool which can be used to interact with nearly all aspects of SQL server.
Installed on any machine where SQL Server or SQL Management Tools have been installed
 sqlcmd – Command line tool introduced with SQL 2005 intended to replace osql. Installed on any
machine where SQL 2005, SQL 2005 Express, or SQL 2005 Management Tools are installed. osql
is still available with SQL 2005 but is marked as depreciated
 SQL Enterprise Manager – GUI Configuration tool installed with full versions of SQL 7 and SQL
2000. Can be installed on additional client computers but is not available for download
 SQL Server Management Studio – GUI Configuration tool installed with full versions of SQL 2005.
Can be installed on additional client computers but is not available for download
 SQL Server Management Studio Express – GUI Configuration tool freely available for download
from Microsoft
Extra reference links
SQL Server Management Studio Express Download

Tips category – General
Cisco TMS Database Knowledge Tips Page 8 of 35
TIP T103 –SQL Versions bundled with Cisco TMS
Cisco TMS Versions SQL Server Versions
All N/A
To simplify installation for Cisco TMS customers, the Cisco TMS installer as an option would install a
free version of the SQL Server engine. The version has changed as Cisco TMS requirements and
version availability has matured.
 Cisco TMS v9.0 through Cisco TMS v11.1 – MSDE 2000 SP3a
 Cisco TMS v11.5 to current – SQL Server 2005 Express

Tips category – General
Cisco TMS Database Knowledge Tips Page 9 of 35
TIP T104 –Cisco TMS SQL version compatibility
Cisco TMS Versions SQL Server Versions
All
SQL 2000 – All Versions
MSDE 2000 – All Versions
SQL 2005 – All Versions
SQL 2005 Express – All Versions
The SQL Server versions supported for each version of Cisco TMS are listed in the Cisco TMS Release
notes. The major changes in support can be summarized as:
 Cisco TMS 9.0 to Cisco TMS 9.21 – MSDE, MSDE 2000, SQL 2000
 Cisco TMS 9.6 to Cisco TMS 10.0 – MSDE 2000, SQL 2000
 Cisco TMS 11.0 to Cisco TMS 11.9.1 – MSDE 2000, SQL 2000, SQL 2005, SQL 2005 Express
 Cisco TMS 12.0 to current – SQL Server 2005, SQL Server 2005 Express
Please see the Installation and Getting Started Manual for your Cisco TMS version for specific version
requirements and service pack levels

Tips category – General
Cisco TMS Database Knowledge Tips Page 10 of 35
TIP T105 –Cisco TMS database and files
Cisco TMS Versions SQL Server Versions
All
SQL 2000 – All Versions
MSDE 2000 – All Versions
SQL 2005 – All Versions
SQL 2005 Express – All Versions
The Cisco TMS database is installed and maintained by the Cisco TMS installer. Since Cisco TMS v9.0
– the Cisco TMS database is named tmsng . The database consists of two files, a data file and log file –
tmsng.mdf and tmsng_log.ldf respectively. These files will be created in the default data directory of the
SQL Server. For default installations this will be:
 For MSDE/SQL 2000 Servers - C:\Program Files\Microsoft SQL Server\MSSQL\Data
 SQL Server 2005 Express is installed as the named instance \SQLTMS . The data directory is -
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\MSSQL.1\MSSQL\DATA
The Cisco TMS data and log files may not be directly manipulated as long as the database is attached to
the SQL Server. All interaction must be through the SQL Server interface. To work with the files directly,
the database should be detached from the SQL Server (removing the database from the server without
deleting it).

Tips category – General
Cisco TMS Database Knowledge Tips Page 11 of 35
TIP T106 –The SQL Server instance
Cisco TMS Versions SQL Server Versions
All
SQL 2000 – All Versions
MSDE 2000 – All Versions
SQL 2005 – All Versions
SQL 2005 Express – All Versions
SQL Servers are installed as the default instance, or a named instance. The default instance is normally
reached via IP or hostname of the server. A named instance is reached by appending \<instancename>
to the IP or hostname. Example: productionsql\sqltms . Named instances allow multiple SQL servers
to be operating on the same physical server. Configuring a server to run as a named instance can only
be configured at time of installation. SQL 2000 by default installs as the default instance. SQL 2005
Express by default will install as the named instance \sqlexpress
 Prior to Cisco TMS 11.5, MSDE 2000 installed by Cisco TMS would be installed as the default
instance.
 Starting with Cisco TMS 11.5, SQL 2005 Express installed by Cisco TMS would be installed as the
named instance \SQLTMS
When using osql, the –S parameter is used to specify which server to connect to.
Example: osql –E –S localhost\sqltms would connect to the named instance SQLTMS on the
local server

Tips category – General
Cisco TMS Database Knowledge Tips Page 12 of 35
TIP T107 – Identifying the SQL Server instance name
Cisco TMS Versions SQL Server Versions
All
SQL 2000 – All Versions
MSDE 2000 – All Versions
SQL 2005 – All Versions
SQL 2005 Express – All Versions
If you do not know the SQL Server’s instance name, you cannot connect to it. The easiest way to find the
name of an installed named instance is to look in the Services Control Panel of the Windows Server
running the SQL Server. Start Menu->Control Panel->Administrative Tools->Services
 MSDE and SQL 2000 services will be named MSSQL$INSTANCENAME – The default instance is
named MSSQLSERVER
 SQL 2005 and 2005 Express services will be named SQL Server(INSTANCENAME) – If there is no
name in parentheses, it is installed as the default instance
You may also use the osql utility to find local SQL instances and any remote instances that are
broadcasting their presence on the local network.
 Open a command prompt on a computer with SQL Server installed or one with the SQL
Management Tools installed
 Enter the command osql –L
 The command will list any servers it was able to discover

Tips category – General
Cisco TMS Database Knowledge Tips Page 13 of 35
TIP T108 –SQL authentication modes
Cisco TMS Versions SQL Server Versions
All
SQL v7 – All Versions
MSDE – All Versions
SQL 2000 – All Versions
MSDE 2000 – All Versions
SQL 2005 – All Versions
SQL 2005 Express – All Versions
When a client connects to a SQL server, it must authenticate to the server with a SQL Login. The server
can be configured in one of two modes for how clients authenticate. Windows Authentication or Mixed
Mode Authentication. Windows Authentication is using accounts from the Windows Server system.
Accounts can be either local or domain users. Mixed Mode Authentication allows Windows
Authentication but additionally SQL Server Authentication where logins can be defined in the SQL server
itself.
When using Windows Authentication, the credentials of the user running the SQL client are
automatically used to authenticate against the SQL server. When using SQL Server Authentication, the
SQL client provides a specified username and password which may differ from those of the user
themselves.
The authentication mode is configured for an entire SQL instance. When installed, an administrator
account named ‘sa’ is created as the Administrator when using SQL Server Authentication. If installing
with Windows Authentication, local administrators of the Windows Server are automatically granted
administration rights within SQL Server.
Cisco TMS requires the SQL Server be in Mixed Mode Authentication as it uses SQL Server
Authentication to connect to the SQL server.
Extra reference links
Authentication Modes in SQL Server 2000

Tips category – General
Cisco TMS Database Knowledge Tips Page 14 of 35
Tip T109 –When do I need a full version of SQL?
Cisco TMS Versions SQL Server Versions
Cisco TMS 11 and newer
SQL 2000 – All Versions
MSDE 2000 – All Versions
SQL 2005 – All Versions
SQL 2005 Express – All Versions
Cisco TMS ships with a free version of SQL Server to accommodate smaller installations. This edition of
SQL Server is not suitable for all installations, depending on usage and size due to the restrictions on the
free versions of SQL Server.
If running MSDE 2000 upgrading to SQL Server 2005 Express or a full edition of SQL is recommended if
any of the below criteria are met:
 Installations larger than 50 systems
 Scheduling/Monitoring a Cisco TelePresence MPS MCU
 Scheduling conferences larger than 8 participants
 Using a external integration product with Cisco TMS (Exchange, 3
rd
Party Booking, etc)
 Need to use Cisco TMS versions newer then version 11.9.1
SQL Server 2005 is less restrictive then MSDE 2000 and can accommodate most installations but a full
version of SQL Server 2005 is required if any of the below criteria are met
 Database is greater than 4gigs in Size
 Wish to utilize more than 1 CPU and/or 1gig of RAM for SQL Server
 Any clustering/failover solutions are to be used for the SQL Server
Extra reference links
SQL Server 2005 Features Comparison

Tips category – General
Cisco TMS Database Knowledge Tips Page 15 of 35
TIP T109 –Using osql for Cisco TMS tasks
Cisco TMS Versions SQL Server Versions
All
SQL v7 – All Versions
MSDE – All Versions
SQL 2000 – All Versions
MSDE 2000 – All Versions
SQL 2005 – All Versions
SQL 2005 Express – All Versions
osql is the command line utility installed with SQL server. For SQL Server 2005, osql has been
superseded by the new sqlcmd utility, but is still available for use. osql may be intimidating to users for
server configuration tasks, but is well suited for quick changes or simple queries. Many instructions or
changes from Tech Support may be listed using osql for its precision and general availability. osql is best
used by opening a dedicated command prompt on the Windows Server. It will be added to the path for
Windows, so it can be executed without having to navigate to a specific directory.
For Cisco TMS related tasks, the osql syntax needed is simple. Syntax help can be seen by using osql
-?
Note that command line switches are case sensitive!
The most common switches used with Cisco TMS operations are listed below
Switch Description
-S
server\instance Specifies the SQL Server Address to connect to. Can be a hostname, IP or
WINS name. Connect to a named instance by appending \instancename
Examples:
-S
prodsql.company.com\sqlexpress
Connect to named instance
sqlexpress at
prodsql.company.com
-S localhost\sqltms Connect to named instance
sqltms on local server
-E Use Windows Authentication to authenticate to the SQL Server. Will try
connecting to the server using the username and password you logged
into the computer with
-U username Use SQL Server Authentication with the specified username. If –P
parameter is not specified, login is attempted with a NULL password.
Examples:
-U sa
Connect using username sa
-U john.smith Connect using username
john.smith
-P password Use SQL Server Authentication with the specified password. Used in
conjunction with the –U option. If –P is specified but no password supplied,
the system will prompt for the password when the command is executed
Examples:
-U sa –P coolPass
Login using account sa with
password coolPass
-U sa -P Login using account sa but prompt
for password

Tips category – General
Cisco TMS Database Knowledge Tips Page 16 of 35
-d database Specify the database to connect to. Equivalent to saying ‘use
databasename’. For Cisco TMS operations, you will almost always specify
the tmsng database
Examples:
-d tmsng
Connect to database named
tmsng
-Q “query” Executes a query and immediately exits. Use double quotation marks
around the query and single quotation marks around anything embedded
in the query. Used to run a single command against the server.
Examples:
-Q “select * from
acluser”
Runs the t-sql query select * from
acluser
-i filename Executes a SQL script from the specified filename. Useful when running a
batch of commands. Filenames that include spaces should be enclosed in
double quotation marks. To ease specifying filenames, files can be
dragged and dropped to the command window and the full path will
automatically be typed out
Examples:
-I “c:\update
scripts\test.sql”
Will execute the SQL code in the
file test.sql
-o filename Outputs result of command to a file rather than to the screen. Useful when
running large scripts or queries with lots of output.
Simple examples for Cisco TMS use
 Execute a script c:\update.sql against a local Cisco TMS SQL server install while logged in as a
Windows administrator
osql –E –S localhost\sqltms –d tmsng –i “c:\update.sql”
 Run a query ‘select username from acluser’ against a local Cisco TMS SQL server install while
logged in as a Windows administrator and output results to c:\output.txt
osql –E –S localhost\sqltms –d tmsng –o c:\output.txt –Q “select username
from acluser”
Extra reference links
How to manage the SQL Server Desktop Engine (MSDE 2000) or SQL Server 2005 Express Edition by
using the osql utility

Tips category – Networking
Cisco TMS Database Knowledge Tips Page 17 of 35
Tips category – Networking
TIP T200 –Enabling remote access to SQL
Cisco TMS Versions SQL Server Versions
11.0 or newer SQL 2005 – All Versions
SQL 2005 Express – All Versions
SQL Server 2005 installs in a secure fashion that only allows local connections to the database by
default. This includes SQL Server 2005 Express installed by the Cisco TMS installer. To connect to the
database from a remote computer, you must enable remote access.
To enable remote access
1. Open the SQL Server Surface Area Configuration tool from the Microsoft SQL Server Program
Group in the Start Menu
2. Expand under the SQL Server to Database Engine and click on Remote Connections
3. By Default, Local Connections Only is selected. Select Using TCP/IP Only and Click Apply
4. The Database Engine must be restarted to make the change take effect. Click on Service under the
database engine in the left panel. In the details pane, click Stop, and once the service stops, click
Start to restart it.
If using named instances, you should enable the SQL Server Browser as well to allow all instances to be
found from a single connection point. Some restricted security scenarios require connecting to the
explicit port of each instance rather than using the SQL Server Browser.
5. To enable the browser, click on SQL Server Browser in the left panel.
6. In the details pane, change startup type to Automatic, and click Start to start the service immediately
If there are firewalls enabled or between you and the server, you must open ports for the SQL
Connection – See TIP T201 –SQL Server 2005 and firewalls for more details
Extra reference links
How to configure SQL Server 2005 to allow remote connections

Tips category – Networking
Cisco TMS Database Knowledge Tips Page 18 of 35
TIP T201 –SQL Server 2005 and firewalls
Cisco TMS Versions SQL Server Versions
11.0 or newer SQL 2005 – All Versions
SQL 2005 Express – All Versions
SQL Server 2005 requires one TCP port per named instance. Named instances by default will run on an
unassigned dynamic port. Default instances will run on TCP Port 1433. The SQL Server Browser service
is used to tell clients what port a named instance is currently using. The SQL Server Browser service
uses UDP Port 1434 . Restrictive networks can force an instance to run on a fixed port allowing specific
firewall rules to be made and remove the need for SQL Server Browser. The Windows Firewall on the
SQL Server can be setup to allow the dynamic ports for a single instance of SQL Server.
Possible scenarios
 Only using the default instance? Open TCP Port 1433 in your firewall
 Only using one instance and only Windows Firewall - no external firewalls between SQL and client?
Use Windows Firewall steps below
 Using multiple instances on same server with local firewall? Must configure fixed ports for each
instance and configure firewall rules for those ports. SQL Server Browser is optional
 Using external firewalls between client and server? Must configure fixed ports for each instance
and configure firewall rules for those ports. SQL Server Browser is optional
Using Windows Firewall for a single instance
These steps allow a single instance to run on dynamic ports with Windows Firewall Enabled on the SQL
Server
1. Open the Control Panel, open Network Connections, right-click the active connection, and then click
Properties
2. Click the Advanced tab, and then click Windows Firewall Settings
3. Click the Exceptions tab
4. Click Add Port. Enter SQL Server Browser in the Name text field, type 1434 in the Port Number text
field, select UDP, and then click OK.
5. Click Add Program
6. Click Browse, and navigate to the instance of SQL Server. The Cisco TMS default installed SQL
Server will be at C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Sqlservr.exe
7. Click OK twice to close the Windows firewall program.
Using Windows Firewall for multiple instances
Each SQL instance must be configured to run on a fixed port. See the Microsoft article at the end of this
Tip for instructions on configuring fixed ports. Use the steps below to configure the Windows Firewall
1. Open the Control Panel, open Network Connections, right-click the active connection, and then click
Properties
2. Click the Advanced tab, and then click Windows Firewall Settings
3. Click the Exceptions tab
4. Click Add Port. Enter the name of the instance in the Name text field, type the port number assigned
to the instance in the Port Number text field, select TCP, and then click OK.
5. Repeat Step 4 for each instance the server will use
6. If SQL Server Browser is going to be enabled (optional to allow connecting by name only), Click Add
Port. Enter SQL Server Browser in the Name text field, type 1434 in the Port Number text field,
select UDP, and then click OK.
7. Click OK to close the Windows firewall program.

Tips category – Networking
Cisco TMS Database Knowledge Tips Page 19 of 35
Extra reference links
How to: Configure a Firewall for SQL Server Access
How to: Configure a Server to Listen on a Specific TCP Port

Tips category – Networking
Cisco TMS Database Knowledge Tips Page 20 of 35
TIP T202 –SQL Server 2000 and Firewalls
Cisco TMS Versions SQL Server Versions
Cisco TMS 9.0 through
11.9.1 SQL 2000 – All Versions
MSDE 2000 – All Versions
SQL Server 2000 requires one TCP port per named instance. The first instance will run on TCP Port
1433. Secondary named instances will run on a dynamically assigned port. SQL Server will listen on
UDP 1434 to assist clients trying to connect to a secondary instance. Fixed ports can be assigned to
each instance to simplify firewall connectivity. Dynamic ports in SQL 2000 requires additional client
configuration that is beyond the scope of this Tip.
Possible Scenarios
 Only using one instance? Open TCP Port 1433 in your firewall
 Only using one instance and only Windows Firewall - no external firewalls between SQL and client?
Use Windows Firewall steps below
 Using multiple instances on same server with local firewall? Must configure fixed ports for each
instance and configure firewall rules for those ports.
 Using external firewalls between client and server? Must configure fixed ports for each instance
and configure firewall rules for those ports. SQL Server Browser is optional
Using Windows Firewall for single instance
These steps allow a single instance to run on dynamic ports with Windows Firewall Enabled on the SQL
Server
1. Open the Control Panel, open Network Connections, right-click the active connection, and then click
Properties
2. Click the Advanced tab, and then click Windows Firewall Settings
3. Click the Exceptions tab
4. Click Add Port. Enter SQL Server in the Name text field, type 1433 in the Port Number text field,
select UDP, and then click OK.
5. Click OK twice to close the Windows firewall program.
Using Windows Firewall for multiple instances
Each SQL instance must be configured to run on a fixed port. See the Microsoft article at the end of this
Tip for instructions on configuring fixed ports. Use the steps below to configure the Windows Firewall
1. Open the Control Panel, open Network Connections, right-click the active connection, and then click
Properties
2. Click the Advanced tab, and then click Windows Firewall Settings
3. Click the Exceptions tab
4. Click Add Port. Enter the name of the instance in the Name text field, type the port number assigned
to the instance in the Port Number text field, select TCP, and then click OK.
5. Repeat Step 4 for each instance the server will use
6. If connecting by name is to be used, UDP Port 1434 must also be enabled. Click Add Port. Enter
SQL Server Browser in the Name text field, type 1434 in the Port Number text field, select UDP, and
then click OK.
7. Click OK to close the Windows firewall program.
To find the port a SQL Server instance is currently using:
1. On the server that is running SQL Server 2000, start the Server Network Utility
2. Click the General tab, and then select the instance that you want from the Instances list
3. Click TCP/IP, and then click Properties. The TCP/IP port number for this instance is shown