How to control SQL Server 2005 Express installed as a "prerequisite"

Suppose I check "SQL Server 2005 Express Edition" as one of the prerequisites for a custom app in a Windows Setup project.

From reading whatever docs I could get my hands on, it's still not clear to me how to control the installation of SQL Server Express with respect to things like instance name, service account, etc, etc.

In other words, this is stuff that's normally the domain of template.ini. However, there's no clear indication of where I should put template.ini so that the install of "prerequisite" SQL Server Express will see it and configure accordingly...

Thanks in advance to anyone who can help solve this...

Josh

Josh, template.ini is not used for configuration settings (as the .iss files were in SQL 2000). This file merely is used as documentation for creating silent installs by describing which flags are used in various situations.

As for another application installing SQL 2005 Express, I would assume that the application is controlling the install (instance name, accounts, etc) so that it can connect after install. If they are not exposing these install features during their install, they probably are using some default values for all installs.

Thanks,
Samuel Lester (MSFT)

|||

Samuel:

Yep, it looks like the parameters (at least, all the ones I tried) are recognized when supplied on the command line.

One parameter I haven't been able to find, though, is one that tells SQL Server Express Edition to use port 1433 instead of dynamic ports. I know about DISABLENETWORKPROTOCOLS (and it, too, works as expected), but it only activates TCP -- it doesn't affect the port-assignment scheme.

Thanks,
Josh

HOW TO CONNECTED MS SQL 2005?

I had just install MS SQL 2005 at my server computer ( OS windows 2000
server sp4). I have LAN in office with workgroup, and I have a problem
that I can't connect to MS SQL 2005 from client mechine. Previously, I
used MS SQL 2000 server.
Please anybody can help me to resolve this problem?
Regard's
Rudi H
Try this:
Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"RUDI HARSONO" <binapusat@.nusa.net.id> wrote in message
news:%23k1wt7LJHHA.780@.TK2MSFTNGP03.phx.gbl...
>I had just install MS SQL 2005 at my server computer ( OS windows 2000
>server sp4). I have LAN in office with workgroup, and I have a problem that
>I can't connect to MS SQL 2005 from client mechine. Previously, I used MS
>SQL 2000 server.
> Please anybody can help me to resolve this problem?
> Regard's
> Rudi H
|||Arnie Rowland wrote:
> Try this:
> Configuration -Configure SQL Server 2005 to allow remote connections
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
>
thanks for your help...

HOW TO CONNECTED MS SQL 2005?

I had just install MS SQL 2005 at my server computer ( OS windows 2000
server sp4). I have LAN in office with workgroup, and I have a problem
that I can't connect to MS SQL 2005 from client mechine. Previously, I
used MS SQL 2000 server.
Please anybody can help me to resolve this problem?
Regard's
Rudi HTry this:
Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/defaul...kb;EN-US;914277
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"RUDI HARSONO" <binapusat@.nusa.net.id> wrote in message
news:%23k1wt7LJHHA.780@.TK2MSFTNGP03.phx.gbl...
>I had just install MS SQL 2005 at my server computer ( OS windows 2000
>server sp4). I have LAN in office with workgroup, and I have a problem that
>I can't connect to MS SQL 2005 from client mechine. Previously, I used MS
>SQL 2000 server.
> Please anybody can help me to resolve this problem?
> Regard's
> Rudi H|||Arnie Rowland wrote:
> Try this:
> Configuration -Configure SQL Server 2005 to allow remote connections
> http://support.microsoft.com/defaul...kb;EN-US;914277
>
thanks for your help...

how to connect to sql server as other's window login rather than user's window login thorugh A

Dear members,

In MSDN, it says that it is recommended to use windows authentication to connect to SQL Server rather than use mixed authentication.

I create user delta\sqluser on windows OS, and I specify in my webform ASP.NET script below :

protected System.Web.UI.WebControls.Label Label1;
private string _connString = @."data source=delta\sql2000;initial catalog=northwind;integrated security=false;user id=delta\sqluser";
/*
comment : I login to my windows as delta\koronx, and I want to every user (including me), connected to sql server through IIS, will be identified as delta\sqluser not as user's login (impersonate)
*/
private void Page_Load(object sender, System.EventArgs e)
{
SqlConnection conn = new SqlConnection(_connString);
SqlCommand cmd = new SqlCommand();
cmd.Connection = conn;
cmd.CommandType = CommandType.Text;
cmd.CommandText = "select suser_sname()";

conn.Open();

string userName = cmd.ExecuteScalar() as string;
conn.Close();
conn.Close();
Label1.Text = userName;
}

at web.config, I add :
<identity impersonate="false" userName="delta\sqluser" password="" />

at IIS webApplication1's properties, tab "Directory Security", at "Authentication and access control" section, I checked "enable anonymous access" with user : DELTA\IUSR_DELTA and checked "Integrated Windows Authentication",

at query analyzer, I login as "sa" and execute script below :
exec sp_grantdbaccess 'delta\sqluser','northwind'

when I run the ASP.NET script, error at conn.Open(); with error message :
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

What should I do so that IIS login to SQL Server as user delta\sqluser not as "NT AUTHORITY\NETWORK SERVICE" ?

Regards,

Koronx

Your connection string is incorrect. You specify using SQL Authentication (integrated security = false) but what you want is integrated security. However, the connection string for integrated security does not allow you to impersonate a user. You should look for help on configuring your application to impersonate a specific account on an ASP.NET forum at: http://forums.asp.net/.

Thanks
Laurentiu

how to connect to sql server as other's window login rather than user's window login thoru

Dear members,

In MSDN, it says that it is recommended to use windows authentication to connect to SQL Server rather than use mixed authentication.

I create user delta\sqluser on windows OS, and I specify in my webform ASP.NET script below :

protected System.Web.UI.WebControls.Label Label1;
private string _connString = @."data source=delta\sql2000;initial catalog=northwind;integrated security=false;user id=delta\sqluser";
/*
comment : I login to my windows as delta\koronx, and I want to every user (including me), connected to sql server through IIS, will be identified as delta\sqluser not as user's login (impersonate)
*/
private void Page_Load(object sender, System.EventArgs e)
{
SqlConnection conn = new SqlConnection(_connString);
SqlCommand cmd = new SqlCommand();
cmd.Connection = conn;
cmd.CommandType = CommandType.Text;
cmd.CommandText = "select suser_sname()";

conn.Open();

string userName = cmd.ExecuteScalar() as string;
conn.Close();
conn.Close();
Label1.Text = userName;
}

at web.config, I add :
<identity impersonate="false" userName="delta\sqluser" password="" />

at IIS webApplication1's properties, tab "Directory Security", at "Authentication and access control" section, I checked "enable anonymous access" with user : DELTA\IUSR_DELTA and checked "Integrated Windows Authentication",

at query analyzer, I login as "sa" and execute script below :
exec sp_grantdbaccess 'delta\sqluser','northwind'

when I run the ASP.NET script, error at conn.Open(); with error message :
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

What should I do so that IIS login to SQL Server as user delta\sqluser not as "NT AUTHORITY\NETWORK SERVICE" ?

Regards,

Koronx

Your connection string is incorrect. You specify using SQL Authentication (integrated security = false) but what you want is integrated security. However, the connection string for integrated security does not allow you to impersonate a user. You should look for help on configuring your application to impersonate a specific account on an ASP.NET forum at: http://forums.asp.net/.

Thanks
Laurentiu

How to Connect to SQL Server 2005 enterprise version

I've just installed sql server 2005 enterprise on my Windows XP Professional
SP2 machine.
I can't find a way to connect with it.
I'm totaly new to SQL Server and have installed it to learn about it.
I can' t even find out if it is running or not.
When I do a
c:>netstat -a
I can't find the port number 1433 in the list.
I've checked the services but can't find the name there
Thanks in advance,
WillyThis may help. It's a new tutorial I wrote for the coming web release of
Books Online.
Getting Started with the Database Engine
Welcome to the Getting Started with the Database Engine tutorial. This
tutorial is intended for users who are new to SQL Server 2005 and who have
installed Developer, Express, or Evaluation Edition on a computer running
Windows XP Professional Service Pack 1 (SP1).This brief tutorial helps you
get started using the Database Engine.
What You Will Learn
This tutorial shows you how to connect to the Database Engine using SQL
Server Management Studio or Management Studio Express, on both the local
computer and from another computer.
This tutorial is divided into two lessons:
Lesson 1: Connecting to the Database Engine
In this lesson, you will learn how to connect to the Database Engine and
enable additional people to connect.
Lesson 2: Connecting from Another Computer
In this lesson, you will learn how to connect to the Database Engine from a
second computer, including enabling protocols, configuring ports, and
configuring firewall settings.
Requirements
This lesson has no knowledge prerequisites.
Your system must have the following installed to use this tutorial:
a.. Internet Explorer 6.0 or later.
b.. Either SQL Server Management Studio or Management Studio Express.
Lesson 1: Connecting to the Database Engine
When you install the SQL Server 2005 Database Engine, the tools that are
installed depend upon the edition and your setup choices. This lesson
reviews the principal tools, and shows you how to connect and perform a
basic function (authorizing more users).
This lesson contains the following topics:
a.. Tools for Getting Started
b.. Connecting with Management Studio
c.. Authorizing Additional Connections
Tools for Getting Started
The SQL Server 2005 Database Engine ships with a variety of tools. This
topic describes the first tools you will need, and helps you select the
right tool for the job. All tools can be accessed from the Start menu.
Generally, tools such as SQL Server Management Studio are not installed by
default. You must select the tools as part of the client components during
setup. For complete description of the tools described below, search for
them in Books Online. SQL Server 2005 Express Edition contains only a subset
of the tools.
Basic Tools
a.. SQL Server Management Studio is the principal tool for administering
the Database Engine and writing Transact-SQL code. It is hosted in the
Visual Studio shell. It is not included in SQL Server 2005 Express Edition
or SQL Server 2005 Mobile Edition.
b.. SQL Server Management Studio Express is a free, limited version of SQL
Server Management Studio, intended for use with SQL Server 2005 Express
Edition and for users who want the basic features of Management Studio in a
lightweight tool.
c.. SQL Server Surface Area Configuration installs with SQL Server and
lets you enable the server protocols, configure services to start
automatically, and enable some optional features of the Database Engine.
d.. SQL Server Configuration Manager installs with both SQL Server and the
client tools. It lets you enable server protocols, configure protocol
options such as TCP ports, configure server services to start automatically,
and configure client computers to connect in your preferred manner.
Sample Database
SQL Server 2005 includes a sample database called AdventureWorks. This
database is not installed by default. If you wish to experiment with the
AdventureWorks database, you must select it using the Setup program. Most
examples described in Books Online use the AdventureWorks database. For more
information, see Running Setup to Install AdventureWorks Sample Databases
and Samples.
To start SQL Server Management Studio
1. On the Start menu, point to All Programs, point to Microsoft SQL
Server 2005, and then click SQL Server Management Studio.
To start SQL Server Surface Area Configuration or SQL Server Configuration
Manager
1. On the Start menu, point to All Programs, point to Microsoft SQL
Server 2005, point to Configuration Tools, and then click either SQL Server
Surface Area Configuration or SQL Server Configuration Manager.
Connecting with Management Studio
It is easy to connect to the Database Engine from tools running on the same
computer if you know the name of the instance, and if you are connecting as
a member of the Administrators group on the computer. The following
procedures must be performed on the same computer that hosts SQL Server.
To determine the name of the Database Engine instance
1. Log into Windows as a member of the Administrators group, and open
either Management Studio or Management Studio Express Edition.
The Connect to Server dialog box opens.
2. Click Cancel.
3. If Registered Servers is not displayed, on the View menu, click
Registered Servers.
4. With Database Engine selected on the Registered Servers toolbar,
right-click Database Engine, and then click Update Local Server
Registration. All instances of the Database Engine installed on the computer
are displayed. This includes instances of SQL Server 2000. Management Studio
can connect and manage instances of SQL Server 2000 as well as SQL Server
2005. The default instance is unnamed and is shown as the computer name. A
named instance displays as the computer name followed by a backward slash
(\) and then the name of the instance. For SQL Server 2005 Express Edition,
the instance is named <computer_name>\sqlexpress unless the name was changed
during setup.
To verify that the Database Engine is running
1. In Registered Servers, if the name of your instance of SQL Server
has a green dot with a white arrow next to the name, the Database Engine is
running and no further action is necessary.
2. If the name of your instance of SQL Server has a red dot with a
white square next to the name, the Database Engine is stopped. Right-click
the name of the Database Engine, and then click Start. After a confirmation
dialog box, the Database Engine should start and the circle should turn
green.
To connect to the Database Engine
1. On the File menu, click Connect Object Explorer.
The Connect to Server dialog box opens. The Server type box displays the
type that was last used.
2. Select Database Engine.
3. In the Server name box, type the name of the Database Engine
instance.
4. Click Connect.
Authorizing Additional Connections
Now that you have connected to SQL Server as an administrator, one of your
first tasks is to authorize other users to connect. You do this by creating
a login and authorizing that login to access a database as a user. Logins
can be either Windows Authentication logins, which use your Windows
credentials, or SQL Server Authentication logins, which store the
authentication information in SQL Server and are independent of your network
credentials. Use Windows Authentication whenever possible.
Create a Windows Authentication login
1. In the previous task, you connected to the Database Engine using
Management Studio. In Object Explorer, expand your server instance, expand
Security, right-click Logins, and then click New Login.
The Login - New dialog box appears.
2. On the General page, in the Login name box, type a Windows login in
the format <domain>\<login>.
3. In the Default database box, select AdventureWorks if available.
Otherwise select master.
4. On the Server Roles page, if the new login is to be an
administrator, click sysadmin, otherwise leave this blank.
5. On the User Mapping page, select Map for the AdventureWorks
database if it is available. Otherwise select master. Note that the User box
is populated with the login. When closed, the dialog box will create this
user in the database.
6. In the Default Schema box, type dbo to map the login to the
database administrator schema.
7. Accept the default settings for the Securables and Status boxes and
click OK to create the login.
Note:
This is basic information to get you started. SQL Server provides a
rich security environment, and security is obviously an important aspect of
database operations. For more information about security, read the security
sections of Books Online, starting with Security Considerations for
Databases and Database Applications.
Lesson 2: Connecting from Another Computer
To enhance security, the Database Engine of SQL Server 2005 Developer,
Express, and Evaluation Editions cannot be accessed from another computer
when initially installed. This lesson shows you how to enable the protocols,
configure the ports, and configure the Windows Firewall for connecting from
other computers.
This lesson contains the following topics:
a.. Enabling Protocols
b.. Configuring a Fixed Port
c.. Opening Ports in the Firewall
d.. Connecting to the Database Engine from Another Computer
e.. Connecting Using the SQL Server Browser Service
Enabling Protocols
To enhance security, SQL Server 2005 Express Edition Developer Edition and
Evaluation Edition install with only limited network connectivity.
Connections to the Database Engine can be made from tools running the same
computer, but not from other computers. If you are planning to do your
development work on the same computer as the Database Engine, you're done.
Management Studio or Management Studio Express Edition will connect to the
Database Engine using the shared memory protocol, which is already enabled.
If you plan to connect to the Database Engine from another computer, you
must enable a protocol, such as TCP/IP.
How to enable TCP/IP connections from another computer
1. Start SQL Server Surface Area Configuration, and click Surface Area
Configuration for Services.
2. In the Surface Area Configuration for Services and Connections box,
the View by Instance box lists the instances of the Database Engine
installed on the computer. The default instance (an unnamed instance) is
listed as MSSQLSERVER. If you installed a named instance, the name you
provided is listed. SQL Server 2005 Express Edition installs as SQLEXPRESS
unless you changed the name during setup. In the View by Instance box,
expand the instance you wish to configure, expand Database Engine, and then
click Remote Connections.
3. Click Local and remote connections, click Using TCP/IP only, then
click OK and close the tool.
Configuring a Fixed Port
To enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
the Windows Firewall. When SQL Server 2005 Developer, Express, or Evaluation
Edition is running on Windows XP Professional, and you wish to connect to it
from another computer, you must open a communication port in the firewall.
The default instance of the Database Engine listens on port 1433, so you do
not need to configure a fixed port, but named instances including SQL Server
2005 Express Edition listen on dynamic ports. Before you can open a port in
the firewall, you must first configure the Database Engine to listen on a
specific port; otherwise the Database Engine may listen on a different port
each time it is started.
Configure SQL Server to listen on a specific port
1. In SQL Server Configuration Manager, expand SQL Server 2005 Network
Configuration, and then click on the server instance you wish to configure.
2. In the right pane, double-click TCP/IP.
3. In the TCP/IP Properties dialog box, click the IP Addresses tab.
4. In the TCP Port box of the IPAll section, type an available port
number. For this tutorial, we will use 1500.
5. Click OK to close the dialog box, and click OK to the warning that
the service must be restarted.
6. In the left pane, click SQL Server 2005 Services.
7. In the right pane, right-click the instance of SQL Server, and then
click Restart. When the Database Engine restarts, it will listen on port
1500.
Opening Ports in the Firewall
Firewall systems prevent unauthorized access to computer resources. To
enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
Windows Firewall. To connect to SQL Server from another computer, you must
open a port in the firewall.
Important:
Opening ports in your firewall can leave your server exposed to
malicious attacks. Be sure to understand firewall systems before opening
ports. For more information, see Security Considerations for a SQL Server
Installation.
After configuring the Database Engine to use a fixed port, follow the
following instructions to open that port in your Windows Firewall. (You do
not need to configure a fixed port for the default instance, because it is
already fixed on port 1433.)
To open a port in Windows Firewall
1. On the Start menu, click Control Panel.
2. In Control Panel, click Network and Internet Connections, and then
open Windows Firewall.
3. In Windows Firewall, click the Exceptions tab, and then click Add
Port.
4. In the Add a Port dialog box, in the Name box, type SQL Server
<instanceName>.
5. In the Port number box, type the port number of the Database Engine
instance. Use 1433 for the default instance. Type 1500 if you are
configuring a named instance and configured a fixed port in the previous
task. Verify that TCP is selected, and then click OK.
Connecting to the Database Engine from Another Computer
Now that you have configured the Database Engine to listen on a fixed port,
and have opened that port in the firewall, you can connect to SQL Server
from another computer.
When the SQL Server Browser service is running on the server computer, and
when the firewall has opened UDP port 1434, the connection can be made using
the computer name and instance name. To enhance security, our example does
not use the SQL Server Browser service.
To connect to the Database Engine from another computer
1. On a second computer containing the SQL Server 2005 client tools,
log in with an account authorized to connect to SQL Server, and open
Management Studio.
2. In the Connect to Server dialog box, confirm Database Engine in the
Server type box.
3. In the Server name box, type tcp: to specify the protocol, followed
by the computer name, a comma, and the port number. To connect to the
default instance, the port 1433 is implied and can be omitted, so type
tcp:<computer_name>. In our example for a named instance, type
tcp:<computer_name>,1500.
4. In the Authentication box, confirm Window Authentication, and then
click Connect.
Connecting Using the SQL Server Browser Service
The SQL Server Browser service listens for incoming requests for SQL Server
resources and provides information about SQL Server instances installed on
the computer. When the SQL Server Browser service is running, users can
connect to named instances by providing the computer name and instance name,
instead of the computer name and port number. Because SQL Server Browser
receives unauthenticated UDP requests, it is not always turned on during
setup. For a description of the service and an explanation of when it is
turned on, see SQL Server Browser Service.
To use the SQL Server Browser, you must follow the same steps as the
previous task in this lesson, and open UDP port 1434.
This concludes this brief tutorial on basic connectivity. For more
information about configuring server and client connectivity, see Database
Engine Connectivity How-to Topics.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Willy Verbiest" <willy.verbiest@.telenetnospam.be> wrote in message
news:Oo4ff.51028$Uj3.2801801@.phobos.telenet-ops.be...
> I've just installed sql server 2005 enterprise on my Windows XP
> Professional SP2 machine.
> I can't find a way to connect with it.
> I'm totaly new to SQL Server and have installed it to learn about it.
> I can' t even find out if it is running or not.
> When I do a
> c:>netstat -a
> I can't find the port number 1433 in the list.
> I've checked the services but can't find the name there
> Thanks in advance,
> Willy
>

How to Connect to SQL Server 2005 enterprise version

I've just installed sql server 2005 enterprise on my Windows XP Professional
SP2 machine.
I can't find a way to connect with it.
I'm totaly new to SQL Server and have installed it to learn about it.
I can' t even find out if it is running or not.
When I do a
c:>netstat -a
I can't find the port number 1433 in the list.
I've checked the services but can't find the name there
Thanks in advance,
Willy
This may help. It's a new tutorial I wrote for the coming web release of
Books Online.
Getting Started with the Database Engine
Welcome to the Getting Started with the Database Engine tutorial. This
tutorial is intended for users who are new to SQL Server 2005 and who have
installed Developer, Express, or Evaluation Edition on a computer running
Windows XP Professional Service Pack 1 (SP1).This brief tutorial helps you
get started using the Database Engine.
What You Will Learn
This tutorial shows you how to connect to the Database Engine using SQL
Server Management Studio or Management Studio Express, on both the local
computer and from another computer.
This tutorial is divided into two lessons:
Lesson 1: Connecting to the Database Engine
In this lesson, you will learn how to connect to the Database Engine and
enable additional people to connect.
Lesson 2: Connecting from Another Computer
In this lesson, you will learn how to connect to the Database Engine from a
second computer, including enabling protocols, configuring ports, and
configuring firewall settings.
Requirements
This lesson has no knowledge prerequisites.
Your system must have the following installed to use this tutorial:
a.. Internet Explorer 6.0 or later.
b.. Either SQL Server Management Studio or Management Studio Express.
Lesson 1: Connecting to the Database Engine
When you install the SQL Server 2005 Database Engine, the tools that are
installed depend upon the edition and your setup choices. This lesson
reviews the principal tools, and shows you how to connect and perform a
basic function (authorizing more users).
This lesson contains the following topics:
a.. Tools for Getting Started
b.. Connecting with Management Studio
c.. Authorizing Additional Connections
Tools for Getting Started
The SQL Server 2005 Database Engine ships with a variety of tools. This
topic describes the first tools you will need, and helps you select the
right tool for the job. All tools can be accessed from the Start menu.
Generally, tools such as SQL Server Management Studio are not installed by
default. You must select the tools as part of the client components during
setup. For complete description of the tools described below, search for
them in Books Online. SQL Server 2005 Express Edition contains only a subset
of the tools.
Basic Tools
a.. SQL Server Management Studio is the principal tool for administering
the Database Engine and writing Transact-SQL code. It is hosted in the
Visual Studio shell. It is not included in SQL Server 2005 Express Edition
or SQL Server 2005 Mobile Edition.
b.. SQL Server Management Studio Express is a free, limited version of SQL
Server Management Studio, intended for use with SQL Server 2005 Express
Edition and for users who want the basic features of Management Studio in a
lightweight tool.
c.. SQL Server Surface Area Configuration installs with SQL Server and
lets you enable the server protocols, configure services to start
automatically, and enable some optional features of the Database Engine.
d.. SQL Server Configuration Manager installs with both SQL Server and the
client tools. It lets you enable server protocols, configure protocol
options such as TCP ports, configure server services to start automatically,
and configure client computers to connect in your preferred manner.
Sample Database
SQL Server 2005 includes a sample database called AdventureWorks. This
database is not installed by default. If you wish to experiment with the
AdventureWorks database, you must select it using the Setup program. Most
examples described in Books Online use the AdventureWorks database. For more
information, see Running Setup to Install AdventureWorks Sample Databases
and Samples.
To start SQL Server Management Studio
1. On the Start menu, point to All Programs, point to Microsoft SQL
Server 2005, and then click SQL Server Management Studio.
To start SQL Server Surface Area Configuration or SQL Server Configuration
Manager
1. On the Start menu, point to All Programs, point to Microsoft SQL
Server 2005, point to Configuration Tools, and then click either SQL Server
Surface Area Configuration or SQL Server Configuration Manager.
Connecting with Management Studio
It is easy to connect to the Database Engine from tools running on the same
computer if you know the name of the instance, and if you are connecting as
a member of the Administrators group on the computer. The following
procedures must be performed on the same computer that hosts SQL Server.
To determine the name of the Database Engine instance
1. Log into Windows as a member of the Administrators group, and open
either Management Studio or Management Studio Express Edition.
The Connect to Server dialog box opens.
2. Click Cancel.
3. If Registered Servers is not displayed, on the View menu, click
Registered Servers.
4. With Database Engine selected on the Registered Servers toolbar,
right-click Database Engine, and then click Update Local Server
Registration. All instances of the Database Engine installed on the computer
are displayed. This includes instances of SQL Server 2000. Management Studio
can connect and manage instances of SQL Server 2000 as well as SQL Server
2005. The default instance is unnamed and is shown as the computer name. A
named instance displays as the computer name followed by a backward slash
(\) and then the name of the instance. For SQL Server 2005 Express Edition,
the instance is named <computer_name>\sqlexpress unless the name was changed
during setup.
To verify that the Database Engine is running
1. In Registered Servers, if the name of your instance of SQL Server
has a green dot with a white arrow next to the name, the Database Engine is
running and no further action is necessary.
2. If the name of your instance of SQL Server has a red dot with a
white square next to the name, the Database Engine is stopped. Right-click
the name of the Database Engine, and then click Start. After a confirmation
dialog box, the Database Engine should start and the circle should turn
green.
To connect to the Database Engine
1. On the File menu, click Connect Object Explorer.
The Connect to Server dialog box opens. The Server type box displays the
type that was last used.
2. Select Database Engine.
3. In the Server name box, type the name of the Database Engine
instance.
4. Click Connect.
Authorizing Additional Connections
Now that you have connected to SQL Server as an administrator, one of your
first tasks is to authorize other users to connect. You do this by creating
a login and authorizing that login to access a database as a user. Logins
can be either Windows Authentication logins, which use your Windows
credentials, or SQL Server Authentication logins, which store the
authentication information in SQL Server and are independent of your network
credentials. Use Windows Authentication whenever possible.
Create a Windows Authentication login
1. In the previous task, you connected to the Database Engine using
Management Studio. In Object Explorer, expand your server instance, expand
Security, right-click Logins, and then click New Login.
The Login - New dialog box appears.
2. On the General page, in the Login name box, type a Windows login in
the format <domain>\<login>.
3. In the Default database box, select AdventureWorks if available.
Otherwise select master.
4. On the Server Roles page, if the new login is to be an
administrator, click sysadmin, otherwise leave this blank.
5. On the User Mapping page, select Map for the AdventureWorks
database if it is available. Otherwise select master. Note that the User box
is populated with the login. When closed, the dialog box will create this
user in the database.
6. In the Default Schema box, type dbo to map the login to the
database administrator schema.
7. Accept the default settings for the Securables and Status boxes and
click OK to create the login.
Note:
This is basic information to get you started. SQL Server provides a
rich security environment, and security is obviously an important aspect of
database operations. For more information about security, read the security
sections of Books Online, starting with Security Considerations for
Databases and Database Applications.
Lesson 2: Connecting from Another Computer
To enhance security, the Database Engine of SQL Server 2005 Developer,
Express, and Evaluation Editions cannot be accessed from another computer
when initially installed. This lesson shows you how to enable the protocols,
configure the ports, and configure the Windows Firewall for connecting from
other computers.
This lesson contains the following topics:
a.. Enabling Protocols
b.. Configuring a Fixed Port
c.. Opening Ports in the Firewall
d.. Connecting to the Database Engine from Another Computer
e.. Connecting Using the SQL Server Browser Service
Enabling Protocols
To enhance security, SQL Server 2005 Express Edition Developer Edition and
Evaluation Edition install with only limited network connectivity.
Connections to the Database Engine can be made from tools running the same
computer, but not from other computers. If you are planning to do your
development work on the same computer as the Database Engine, you're done.
Management Studio or Management Studio Express Edition will connect to the
Database Engine using the shared memory protocol, which is already enabled.
If you plan to connect to the Database Engine from another computer, you
must enable a protocol, such as TCP/IP.
How to enable TCP/IP connections from another computer
1. Start SQL Server Surface Area Configuration, and click Surface Area
Configuration for Services.
2. In the Surface Area Configuration for Services and Connections box,
the View by Instance box lists the instances of the Database Engine
installed on the computer. The default instance (an unnamed instance) is
listed as MSSQLSERVER. If you installed a named instance, the name you
provided is listed. SQL Server 2005 Express Edition installs as SQLEXPRESS
unless you changed the name during setup. In the View by Instance box,
expand the instance you wish to configure, expand Database Engine, and then
click Remote Connections.
3. Click Local and remote connections, click Using TCP/IP only, then
click OK and close the tool.
Configuring a Fixed Port
To enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
the Windows Firewall. When SQL Server 2005 Developer, Express, or Evaluation
Edition is running on Windows XP Professional, and you wish to connect to it
from another computer, you must open a communication port in the firewall.
The default instance of the Database Engine listens on port 1433, so you do
not need to configure a fixed port, but named instances including SQL Server
2005 Express Edition listen on dynamic ports. Before you can open a port in
the firewall, you must first configure the Database Engine to listen on a
specific port; otherwise the Database Engine may listen on a different port
each time it is started.
Configure SQL Server to listen on a specific port
1. In SQL Server Configuration Manager, expand SQL Server 2005 Network
Configuration, and then click on the server instance you wish to configure.
2. In the right pane, double-click TCP/IP.
3. In the TCP/IP Properties dialog box, click the IP Addresses tab.
4. In the TCP Port box of the IPAll section, type an available port
number. For this tutorial, we will use 1500.
5. Click OK to close the dialog box, and click OK to the warning that
the service must be restarted.
6. In the left pane, click SQL Server 2005 Services.
7. In the right pane, right-click the instance of SQL Server, and then
click Restart. When the Database Engine restarts, it will listen on port
1500.
Opening Ports in the Firewall
Firewall systems prevent unauthorized access to computer resources. To
enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
Windows Firewall. To connect to SQL Server from another computer, you must
open a port in the firewall.
Important:
Opening ports in your firewall can leave your server exposed to
malicious attacks. Be sure to understand firewall systems before opening
ports. For more information, see Security Considerations for a SQL Server
Installation.
After configuring the Database Engine to use a fixed port, follow the
following instructions to open that port in your Windows Firewall. (You do
not need to configure a fixed port for the default instance, because it is
already fixed on port 1433.)
To open a port in Windows Firewall
1. On the Start menu, click Control Panel.
2. In Control Panel, click Network and Internet Connections, and then
open Windows Firewall.
3. In Windows Firewall, click the Exceptions tab, and then click Add
Port.
4. In the Add a Port dialog box, in the Name box, type SQL Server
<instanceName>.
5. In the Port number box, type the port number of the Database Engine
instance. Use 1433 for the default instance. Type 1500 if you are
configuring a named instance and configured a fixed port in the previous
task. Verify that TCP is selected, and then click OK.
Connecting to the Database Engine from Another Computer
Now that you have configured the Database Engine to listen on a fixed port,
and have opened that port in the firewall, you can connect to SQL Server
from another computer.
When the SQL Server Browser service is running on the server computer, and
when the firewall has opened UDP port 1434, the connection can be made using
the computer name and instance name. To enhance security, our example does
not use the SQL Server Browser service.
To connect to the Database Engine from another computer
1. On a second computer containing the SQL Server 2005 client tools,
log in with an account authorized to connect to SQL Server, and open
Management Studio.
2. In the Connect to Server dialog box, confirm Database Engine in the
Server type box.
3. In the Server name box, type tcp: to specify the protocol, followed
by the computer name, a comma, and the port number. To connect to the
default instance, the port 1433 is implied and can be omitted, so type
tcp:<computer_name>. In our example for a named instance, type
tcp:<computer_name>,1500.
4. In the Authentication box, confirm Window Authentication, and then
click Connect.
Connecting Using the SQL Server Browser Service
The SQL Server Browser service listens for incoming requests for SQL Server
resources and provides information about SQL Server instances installed on
the computer. When the SQL Server Browser service is running, users can
connect to named instances by providing the computer name and instance name,
instead of the computer name and port number. Because SQL Server Browser
receives unauthenticated UDP requests, it is not always turned on during
setup. For a description of the service and an explanation of when it is
turned on, see SQL Server Browser Service.
To use the SQL Server Browser, you must follow the same steps as the
previous task in this lesson, and open UDP port 1434.
This concludes this brief tutorial on basic connectivity. For more
information about configuring server and client connectivity, see Database
Engine Connectivity How-to Topics.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Willy Verbiest" <willy.verbiest@.telenetnospam.be> wrote in message
news:Oo4ff.51028$Uj3.2801801@.phobos.telenet-ops.be...
> I've just installed sql server 2005 enterprise on my Windows XP
> Professional SP2 machine.
> I can't find a way to connect with it.
> I'm totaly new to SQL Server and have installed it to learn about it.
> I can' t even find out if it is running or not.
> When I do a
> c:>netstat -a
> I can't find the port number 1433 in the list.
> I've checked the services but can't find the name there
> Thanks in advance,
> Willy
>

how to connect jsp file with Microsoft SQL Server

Can anyone please teach me how to make a connection between jsp file and Microsoft SQL Server database steps by steps?

I'm using Windows XP and I found that my computer do not have JDBC (I already have ODBC). Is this mean that I have to install some JDBC or SQL driver in order to make the connection? Which driver should I install and where can I get the driver?

If possible, please show me some example so that I can understand better..Thanks a lot.

Regards,
san sanYes, you need to download a jdbc driver and include its jar in your classpath.

Below is a URL that demonstrates what you need to do.

http://www.akadia.com/services/sqlsrv_jdbc.html

How to connect database under Windows Authentication?

Hi, all. I develop my JDBC program under SQL SERVER Authentication using Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver").newInstance();
Connection con = DriverManager.getConnection("jdbc:sqlserver://dataserver:1433; DatabaseName=database", username, password);
It works well.
After my company update the database to SQL SERVER 2005 using Windows Authentication. My program sucks.
I want to know the format of JDBC connectivity code for Windows Authentication, as similar as the code I post above? Anyone can help me?

Hi there,

As far as I am aware, the SQL Server 2005 JDBC driver does not currently support Windows Authentication. Checking out the documentation I found here seems to indicate that Windows Auth doesn't work as setting the integratedSecurity property to "true" (implying Windows Auth) produces an exception.

You could try jTDS (http://jtds.sourceforge.net/faq.html). The project seems to be dead at the moment but you can still download the required files. It supports Windows Auth and in the connection string you have to use the domain property and specify what domain you are on (same domain as the SQL Server you are trying to connect to, of course).

The relevant information is all in the FAQ (the jTDS link I gave above).

Good luck & sorry I couldn't be of more help at the mo.

How to connect a workstation to SQL Server 2005 thru ODBC?

I have installed a SQL Server 2005 named instance with mixed authentication
on a Windows 2003 Standard Server. SQL Server Service is running under local
system account. I have not changed any default setting.
I want to set up a System DSN in ODBC Data Source Administrator on a Windows
XP SP2 machine to connect to the SQL Server 2005 named instance. But I get
the message Specified SQL Server not found. I have no problem in setting up
System DSN to connect to SQL Server 2000 named instances which is in another
Windows 2003 Standard Server. I have not installed anything from SQL Server
2005 onto the Windows XP machine.
Thanks for any help.
You didn't mention if the connection attempt was from the same computer. If
you are connecting from a different computer, you probably need to use the
Surface Area Configuration tool, and open the port in the Windows XP
firewall. This tutorial may help you.
Getting Started with the Database Engine
Welcome to the Getting Started with the Database Engine tutorial. This
tutorial is intended for users who are new to SQL Server 2005 and who have
installed Developer, Express, or Evaluation Edition on a computer running
Windows XP Professional Service Pack 1 (SP1).This brief tutorial helps you
get started using the Database Engine.
What You Will Learn
This tutorial shows you how to connect to the Database Engine using SQL
Server Management Studio or Management Studio Express, on both the local
computer and from another computer.
This tutorial is divided into two lessons:
Lesson 1: Connecting to the Database Engine
In this lesson, you will learn how to connect to the Database Engine and
enable additional people to connect.
Lesson 2: Connecting from Another Computer
In this lesson, you will learn how to connect to the Database Engine from a
second computer, including enabling protocols, configuring ports, and
configuring firewall settings.
Requirements
This lesson has no knowledge prerequisites.
Your system must have the following installed to use this tutorial:
a.. Internet Explorer 6.0 or later.
b.. Either SQL Server Management Studio or Management Studio Express.
Lesson 1: Connecting to the Database Engine
When you install the SQL Server 2005 Database Engine, the tools that are
installed depend upon the edition and your setup choices. This lesson
reviews the principal tools, and shows you how to connect and perform a
basic function (authorizing more users).
This lesson contains the following topics:
a.. Tools for Getting Started
b.. Connecting with Management Studio
c.. Authorizing Additional Connections
Tools for Getting Started
The SQL Server 2005 Database Engine ships with a variety of tools. This
topic describes the first tools you will need, and helps you select the
right tool for the job. All tools can be accessed from the Start menu.
Generally, tools such as SQL Server Management Studio are not installed by
default. You must select the tools as part of the client components during
setup. For complete description of the tools described below, search for
them in Books Online. SQL Server 2005 Express Edition contains only a subset
of the tools.
Basic Tools
a.. SQL Server Management Studio is the principal tool for administering
the Database Engine and writing Transact-SQL code. It is hosted in the
Visual Studio shell. It is not included in SQL Server 2005 Express Edition
or SQL Server 2005 Mobile Edition.
b.. SQL Server Management Studio Express is a free, limited version of SQL
Server Management Studio, intended for use with SQL Server 2005 Express
Edition and for users who want the basic features of Management Studio in a
lightweight tool.
c.. SQL Server Surface Area Configuration installs with SQL Server and
lets you enable the server protocols, configure services to start
automatically, and enable some optional features of the Database Engine.
d.. SQL Server Configuration Manager installs with both SQL Server and the
client tools. It lets you enable server protocols, configure protocol
options such as TCP ports, configure server services to start automatically,
and configure client computers to connect in your preferred manner.
Sample Database
SQL Server 2005 includes a sample database called AdventureWorks. This
database is not installed by default. If you wish to experiment with the
AdventureWorks database, you must select it using the Setup program. Most
examples described in Books Online use the AdventureWorks database. For more
information, see Running Setup to Install AdventureWorks Sample Databases
and Samples.
To start SQL Server Management Studio
1. On the Start menu, point to All Programs, point to Microsoft SQL
Server 2005, and then click SQL Server Management Studio.
To start SQL Server Surface Area Configuration or SQL Server Configuration
Manager
1. On the Start menu, point to All Programs, point to Microsoft SQL
Server 2005, point to Configuration Tools, and then click either SQL Server
Surface Area Configuration or SQL Server Configuration Manager.
Connecting with Management Studio
It is easy to connect to the Database Engine from tools running on the same
computer if you know the name of the instance, and if you are connecting as
a member of the Administrators group on the computer. The following
procedures must be performed on the same computer that hosts SQL Server.
To determine the name of the Database Engine instance
1. Log into Windows as a member of the Administrators group, and open
either Management Studio or Management Studio Express Edition.
The Connect to Server dialog box opens.
2. Click Cancel.
3. If Registered Servers is not displayed, on the View menu, click
Registered Servers.
4. With Database Engine selected on the Registered Servers toolbar,
right-click Database Engine, and then click Update Local Server
Registration. All instances of the Database Engine installed on the computer
are displayed. This includes instances of SQL Server 2000. Management Studio
can connect and manage instances of SQL Server 2000 as well as SQL Server
2005. The default instance is unnamed and is shown as the computer name. A
named instance displays as the computer name followed by a backward slash
(\) and then the name of the instance. For SQL Server 2005 Express Edition,
the instance is named <computer_name>\sqlexpress unless the name was changed
during setup.
To verify that the Database Engine is running
1. In Registered Servers, if the name of your instance of SQL Server
has a green dot with a white arrow next to the name, the Database Engine is
running and no further action is necessary.
2. If the name of your instance of SQL Server has a red dot with a
white square next to the name, the Database Engine is stopped. Right-click
the name of the Database Engine, and then click Start. After a confirmation
dialog box, the Database Engine should start and the circle should turn
green.
To connect to the Database Engine
1. On the File menu, click Connect Object Explorer.
The Connect to Server dialog box opens. The Server type box displays the
type that was last used.
2. Select Database Engine.
3. In the Server name box, type the name of the Database Engine
instance.
4. Click Connect.
Authorizing Additional Connections
Now that you have connected to SQL Server as an administrator, one of your
first tasks is to authorize other users to connect. You do this by creating
a login and authorizing that login to access a database as a user. Logins
can be either Windows Authentication logins, which use your Windows
credentials, or SQL Server Authentication logins, which store the
authentication information in SQL Server and are independent of your network
credentials. Use Windows Authentication whenever possible.
Create a Windows Authentication login
1. In the previous task, you connected to the Database Engine using
Management Studio. In Object Explorer, expand your server instance, expand
Security, right-click Logins, and then click New Login.
The Login - New dialog box appears.
2. On the General page, in the Login name box, type a Windows login in
the format <domain>\<login>.
3. In the Default database box, select AdventureWorks if available.
Otherwise select master.
4. On the Server Roles page, if the new login is to be an
administrator, click sysadmin, otherwise leave this blank.
5. On the User Mapping page, select Map for the AdventureWorks
database if it is available. Otherwise select master. Note that the User box
is populated with the login. When closed, the dialog box will create this
user in the database.
6. In the Default Schema box, type dbo to map the login to the
database administrator schema.
7. Accept the default settings for the Securables and Status boxes and
click OK to create the login.
Note:
This is basic information to get you started. SQL Server provides a
rich security environment, and security is obviously an important aspect of
database operations. For more information about security, read the security
sections of Books Online, starting with Security Considerations for
Databases and Database Applications.
Lesson 2: Connecting from Another Computer
To enhance security, the Database Engine of SQL Server 2005 Developer,
Express, and Evaluation Editions cannot be accessed from another computer
when initially installed. This lesson shows you how to enable the protocols,
configure the ports, and configure the Windows Firewall for connecting from
other computers.
This lesson contains the following topics:
a.. Enabling Protocols
b.. Configuring a Fixed Port
c.. Opening Ports in the Firewall
d.. Connecting to the Database Engine from Another Computer
e.. Connecting Using the SQL Server Browser Service
Enabling Protocols
To enhance security, SQL Server 2005 Express Edition Developer Edition and
Evaluation Edition install with only limited network connectivity.
Connections to the Database Engine can be made from tools running the same
computer, but not from other computers. If you are planning to do your
development work on the same computer as the Database Engine, you're done.
Management Studio or Management Studio Express Edition will connect to the
Database Engine using the shared memory protocol, which is already enabled.
If you plan to connect to the Database Engine from another computer, you
must enable a protocol, such as TCP/IP.
How to enable TCP/IP connections from another computer
1. Start SQL Server Surface Area Configuration, and click Surface Area
Configuration for Services.
2. In the Surface Area Configuration for Services and Connections box,
the View by Instance box lists the instances of the Database Engine
installed on the computer. The default instance (an unnamed instance) is
listed as MSSQLSERVER. If you installed a named instance, the name you
provided is listed. SQL Server 2005 Express Edition installs as SQLEXPRESS
unless you changed the name during setup. In the View by Instance box,
expand the instance you wish to configure, expand Database Engine, and then
click Remote Connections.
3. Click Local and remote connections, click Using TCP/IP only, then
click OK and close the tool.
Configuring a Fixed Port
To enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
the Windows Firewall. When SQL Server 2005 Developer, Express, or Evaluation
Edition is running on Windows XP Professional, and you wish to connect to it
from another computer, you must open a communication port in the firewall.
The default instance of the Database Engine listens on port 1433, so you do
not need to configure a fixed port, but named instances including SQL Server
2005 Express Edition listen on dynamic ports. Before you can open a port in
the firewall, you must first configure the Database Engine to listen on a
specific port; otherwise the Database Engine may listen on a different port
each time it is started.
Configure SQL Server to listen on a specific port
1. In SQL Server Configuration Manager, expand SQL Server 2005 Network
Configuration, and then click on the server instance you wish to configure.
2. In the right pane, double-click TCP/IP.
3. In the TCP/IP Properties dialog box, click the IP Addresses tab.
4. In the TCP Port box of the IPAll section, type an available port
number. For this tutorial, we will use 1500.
5. Click OK to close the dialog box, and click OK to the warning that
the service must be restarted.
6. In the left pane, click SQL Server 2005 Services.
7. In the right pane, right-click the instance of SQL Server, and then
click Restart. When the Database Engine restarts, it will listen on port
1500.
Opening Ports in the Firewall
Firewall systems prevent unauthorized access to computer resources. To
enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
Windows Firewall. To connect to SQL Server from another computer, you must
open a port in the firewall.
Important:
Opening ports in your firewall can leave your server exposed to
malicious attacks. Be sure to understand firewall systems before opening
ports. For more information, see Security Considerations for a SQL Server
Installation.
After configuring the Database Engine to use a fixed port, follow the
following instructions to open that port in your Windows Firewall. (You do
not need to configure a fixed port for the default instance, because it is
already fixed on port 1433.)
To open a port in Windows Firewall
1. On the Start menu, click Control Panel.
2. In Control Panel, click Network and Internet Connections, and then
open Windows Firewall.
3. In Windows Firewall, click the Exceptions tab, and then click Add
Port.
4. In the Add a Port dialog box, in the Name box, type SQL Server
<instanceName>.
5. In the Port number box, type the port number of the Database Engine
instance. Use 1433 for the default instance. Type 1500 if you are
configuring a named instance and configured a fixed port in the previous
task. Verify that TCP is selected, and then click OK.
Connecting to the Database Engine from Another Computer
Now that you have configured the Database Engine to listen on a fixed port,
and have opened that port in the firewall, you can connect to SQL Server
from another computer.
When the SQL Server Browser service is running on the server computer, and
when the firewall has opened UDP port 1434, the connection can be made using
the computer name and instance name. To enhance security, our example does
not use the SQL Server Browser service.
To connect to the Database Engine from another computer
1. On a second computer containing the SQL Server 2005 client tools,
log in with an account authorized to connect to SQL Server, and open
Management Studio.
2. In the Connect to Server dialog box, confirm Database Engine in the
Server type box.
3. In the Server name box, type tcp: to specify the protocol, followed
by the computer name, a comma, and the port number. To connect to the
default instance, the port 1433 is implied and can be omitted, so type
tcp:<computer_name>. In our example for a named instance, type
tcp:<computer_name>,1500.
4. In the Authentication box, confirm Window Authentication, and then
click Connect.
Connecting Using the SQL Server Browser Service
The SQL Server Browser service listens for incoming requests for SQL Server
resources and provides information about SQL Server instances installed on
the computer. When the SQL Server Browser service is running, users can
connect to named instances by providing the computer name and instance name,
instead of the computer name and port number. Because SQL Server Browser
receives unauthenticated UDP requests, it is not always turned on during
setup. For a description of the service and an explanation of when it is
turned on, see SQL Server Browser Service.
To use the SQL Server Browser, you must follow the same steps as the
previous task in this lesson, and open UDP port 1434.
This concludes this brief tutorial on basic connectivity. For more
information about configuring server and client connectivity, see Database
Engine Connectivity How-to Topics.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:1ED4DC95-43E3-4647-92B7-2B11D1A2A28C@.microsoft.com...
>I have installed a SQL Server 2005 named instance with mixed authentication
> on a Windows 2003 Standard Server. SQL Server Service is running under
> local
> system account. I have not changed any default setting.
> I want to set up a System DSN in ODBC Data Source Administrator on a
> Windows
> XP SP2 machine to connect to the SQL Server 2005 named instance. But I
> get
> the message Specified SQL Server not found. I have no problem in setting
> up
> System DSN to connect to SQL Server 2000 named instances which is in
> another
> Windows 2003 Standard Server. I have not installed anything from SQL
> Server
> 2005 onto the Windows XP machine.
> Thanks for any help.
|||Hi Rick,
I have actually read this tutorial but I believe it is based on the scenario
that the client computer will have SQL Server 2005 component installed. I'm
trying to connect from a different computer which has no SQL Server 2005
component installed. If I understand correctly, SQL Native Client is
required if I'm trying to use new features in SQL Server 2005.
Environment:
Developer edition of SQL Server 2005 is installed on a Windows 2003 Standard
Edition with SP1 machine which has no Windows Firewall/ICS service running.
I have enabled the TCP/IP protocol through SQL Server Surface Area
Configuration. I'm trying to connect from a Windows XP Professional with SP2
machine which has the following exceptions in the Windows Firewall:
File and Printer Sharing
Remote Assistance
MSN Messenger 7.5
Remote Desktop
Please note that I have NOT installed anything from SQL Server 2005 CD onto
the Windows XP SP2 machine. I'm trying the connection in the ODBC
Administrator using SQL Server driver 2000.85.1117.00.
Thanks,
Peter
"Rick Byham [MS]" wrote:

> You didn't mention if the connection attempt was from the same computer. If
> you are connecting from a different computer, you probably need to use the
> Surface Area Configuration tool, and open the port in the Windows XP
> firewall. This tutorial may help you.
> Getting Started with the Database Engine
> Welcome to the Getting Started with the Database Engine tutorial. This
> tutorial is intended for users who are new to SQL Server 2005 and who have
> installed Developer, Express, or Evaluation Edition on a computer running
> Windows XP Professional Service Pack 1 (SP1).This brief tutorial helps you
> get started using the Database Engine.
> What You Will Learn
> This tutorial shows you how to connect to the Database Engine using SQL
> Server Management Studio or Management Studio Express, on both the local
> computer and from another computer.
> This tutorial is divided into two lessons:
> Lesson 1: Connecting to the Database Engine
> In this lesson, you will learn how to connect to the Database Engine and
> enable additional people to connect.
> Lesson 2: Connecting from Another Computer
> In this lesson, you will learn how to connect to the Database Engine from a
> second computer, including enabling protocols, configuring ports, and
> configuring firewall settings.
> Requirements
> This lesson has no knowledge prerequisites.
> Your system must have the following installed to use this tutorial:
> a.. Internet Explorer 6.0 or later.
> b.. Either SQL Server Management Studio or Management Studio Express.
> Lesson 1: Connecting to the Database Engine
> When you install the SQL Server 2005 Database Engine, the tools that are
> installed depend upon the edition and your setup choices. This lesson
> reviews the principal tools, and shows you how to connect and perform a
> basic function (authorizing more users).
> This lesson contains the following topics:
> a.. Tools for Getting Started
> b.. Connecting with Management Studio
> c.. Authorizing Additional Connections
> Tools for Getting Started
> The SQL Server 2005 Database Engine ships with a variety of tools. This
> topic describes the first tools you will need, and helps you select the
> right tool for the job. All tools can be accessed from the Start menu.
> Generally, tools such as SQL Server Management Studio are not installed by
> default. You must select the tools as part of the client components during
> setup. For complete description of the tools described below, search for
> them in Books Online. SQL Server 2005 Express Edition contains only a subset
> of the tools.
> Basic Tools
> a.. SQL Server Management Studio is the principal tool for administering
> the Database Engine and writing Transact-SQL code. It is hosted in the
> Visual Studio shell. It is not included in SQL Server 2005 Express Edition
> or SQL Server 2005 Mobile Edition.
> b.. SQL Server Management Studio Express is a free, limited version of SQL
> Server Management Studio, intended for use with SQL Server 2005 Express
> Edition and for users who want the basic features of Management Studio in a
> lightweight tool.
> c.. SQL Server Surface Area Configuration installs with SQL Server and
> lets you enable the server protocols, configure services to start
> automatically, and enable some optional features of the Database Engine.
> d.. SQL Server Configuration Manager installs with both SQL Server and the
> client tools. It lets you enable server protocols, configure protocol
> options such as TCP ports, configure server services to start automatically,
> and configure client computers to connect in your preferred manner.
> Sample Database
> SQL Server 2005 includes a sample database called AdventureWorks. This
> database is not installed by default. If you wish to experiment with the
> AdventureWorks database, you must select it using the Setup program. Most
> examples described in Books Online use the AdventureWorks database. For more
> information, see Running Setup to Install AdventureWorks Sample Databases
> and Samples.
> To start SQL Server Management Studio
> 1. On the Start menu, point to All Programs, point to Microsoft SQL
> Server 2005, and then click SQL Server Management Studio.
> To start SQL Server Surface Area Configuration or SQL Server Configuration
> Manager
> 1. On the Start menu, point to All Programs, point to Microsoft SQL
> Server 2005, point to Configuration Tools, and then click either SQL Server
> Surface Area Configuration or SQL Server Configuration Manager.
> Connecting with Management Studio
> It is easy to connect to the Database Engine from tools running on the same
> computer if you know the name of the instance, and if you are connecting as
> a member of the Administrators group on the computer. The following
> procedures must be performed on the same computer that hosts SQL Server.
> To determine the name of the Database Engine instance
> 1. Log into Windows as a member of the Administrators group, and open
> either Management Studio or Management Studio Express Edition.
> The Connect to Server dialog box opens.
> 2. Click Cancel.
> 3. If Registered Servers is not displayed, on the View menu, click
> Registered Servers.
> 4. With Database Engine selected on the Registered Servers toolbar,
> right-click Database Engine, and then click Update Local Server
> Registration. All instances of the Database Engine installed on the computer
> are displayed. This includes instances of SQL Server 2000. Management Studio
> can connect and manage instances of SQL Server 2000 as well as SQL Server
> 2005. The default instance is unnamed and is shown as the computer name. A
> named instance displays as the computer name followed by a backward slash
> (\) and then the name of the instance. For SQL Server 2005 Express Edition,
> the instance is named <computer_name>\sqlexpress unless the name was changed
> during setup.
> To verify that the Database Engine is running
> 1. In Registered Servers, if the name of your instance of SQL Server
> has a green dot with a white arrow next to the name, the Database Engine is
> running and no further action is necessary.
> 2. If the name of your instance of SQL Server has a red dot with a
> white square next to the name, the Database Engine is stopped. Right-click
> the name of the Database Engine, and then click Start. After a confirmation
> dialog box, the Database Engine should start and the circle should turn
> green.
> To connect to the Database Engine
> 1. On the File menu, click Connect Object Explorer.
> The Connect to Server dialog box opens. The Server type box displays the
> type that was last used.
> 2. Select Database Engine.
> 3. In the Server name box, type the name of the Database Engine
> instance.
> 4. Click Connect.
> Authorizing Additional Connections
> Now that you have connected to SQL Server as an administrator, one of your
> first tasks is to authorize other users to connect. You do this by creating
> a login and authorizing that login to access a database as a user. Logins
> can be either Windows Authentication logins, which use your Windows
> credentials, or SQL Server Authentication logins, which store the
> authentication information in SQL Server and are independent of your network
> credentials. Use Windows Authentication whenever possible.
> Create a Windows Authentication login
> 1. In the previous task, you connected to the Database Engine using
> Management Studio. In Object Explorer, expand your server instance, expand
> Security, right-click Logins, and then click New Login.
> The Login - New dialog box appears.
> 2. On the General page, in the Login name box, type a Windows login in
> the format <domain>\<login>.
> 3. In the Default database box, select AdventureWorks if available.
> Otherwise select master.
> 4. On the Server Roles page, if the new login is to be an
> administrator, click sysadmin, otherwise leave this blank.
> 5. On the User Mapping page, select Map for the AdventureWorks
> database if it is available. Otherwise select master. Note that the User box
> is populated with the login. When closed, the dialog box will create this
> user in the database.
> 6. In the Default Schema box, type dbo to map the login to the
> database administrator schema.
> 7. Accept the default settings for the Securables and Status boxes and
> click OK to create the login.
> Note:
> This is basic information to get you started. SQL Server provides a
> rich security environment, and security is obviously an important aspect of
> database operations. For more information about security, read the security
> sections of Books Online, starting with Security Considerations for
> Databases and Database Applications.
>
> Lesson 2: Connecting from Another Computer
> To enhance security, the Database Engine of SQL Server 2005 Developer,
> Express, and Evaluation Editions cannot be accessed from another computer
> when initially installed. This lesson shows you how to enable the protocols,
> configure the ports, and configure the Windows Firewall for connecting from
> other computers.
> This lesson contains the following topics:
> a.. Enabling Protocols
> b.. Configuring a Fixed Port
> c.. Opening Ports in the Firewall
> d.. Connecting to the Database Engine from Another Computer
> e.. Connecting Using the SQL Server Browser Service
> Enabling Protocols
> To enhance security, SQL Server 2005 Express Edition Developer Edition and
> Evaluation Edition install with only limited network connectivity.
> Connections to the Database Engine can be made from tools running the same
> computer, but not from other computers. If you are planning to do your
> development work on the same computer as the Database Engine, you're done.
> Management Studio or Management Studio Express Edition will connect to the
> Database Engine using the shared memory protocol, which is already enabled.
> If you plan to connect to the Database Engine from another computer, you
> must enable a protocol, such as TCP/IP.
> How to enable TCP/IP connections from another computer
> 1. Start SQL Server Surface Area Configuration, and click Surface Area
> Configuration for Services.
> 2. In the Surface Area Configuration for Services and Connections box,
> the View by Instance box lists the instances of the Database Engine
> installed on the computer. The default instance (an unnamed instance) is
> listed as MSSQLSERVER. If you installed a named instance, the name you
> provided is listed. SQL Server 2005 Express Edition installs as SQLEXPRESS
> unless you changed the name during setup. In the View by Instance box,
> expand the instance you wish to configure, expand Database Engine, and then
> click Remote Connections.
> 3. Click Local and remote connections, click Using TCP/IP only, then
> click OK and close the tool.
> Configuring a Fixed Port
> To enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
> the Windows Firewall. When SQL Server 2005 Developer, Express, or Evaluation
> Edition is running on Windows XP Professional, and you wish to connect to it
> from another computer, you must open a communication port in the firewall.
> The default instance of the Database Engine listens on port 1433, so you do
> not need to configure a fixed port, but named instances including SQL Server
> 2005 Express Edition listen on dynamic ports. Before you can open a port in
> the firewall, you must first configure the Database Engine to listen on a
> specific port; otherwise the Database Engine may listen on a different port
> each time it is started.
> Configure SQL Server to listen on a specific port
> 1. In SQL Server Configuration Manager, expand SQL Server 2005 Network
> Configuration, and then click on the server instance you wish to configure.
> 2. In the right pane, double-click TCP/IP.
> 3. In the TCP/IP Properties dialog box, click the IP Addresses tab.
> 4. In the TCP Port box of the IPAll section, type an available port
> number. For this tutorial, we will use 1500.
> 5. Click OK to close the dialog box, and click OK to the warning that
> the service must be restarted.
> 6. In the left pane, click SQL Server 2005 Services.
> 7. In the right pane, right-click the instance of SQL Server, and then
> click Restart. When the Database Engine restarts, it will listen on port
> 1500.
> Opening Ports in the Firewall
> Firewall systems prevent unauthorized access to computer resources. To
> enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
> Windows Firewall. To connect to SQL Server from another computer, you must
> open a port in the firewall.
> Important:
> Opening ports in your firewall can leave your server exposed to
> malicious attacks. Be sure to understand firewall systems before opening
> ports. For more information, see Security Considerations for a SQL Server
> Installation.
>
> After configuring the Database Engine to use a fixed port, follow the
> following instructions to open that port in your Windows Firewall. (You do
> not need to configure a fixed port for the default instance, because it is
> already fixed on port 1433.)
> To open a port in Windows Firewall
> 1. On the Start menu, click Control Panel.
> 2. In Control Panel, click Network and Internet Connections, and then
> open Windows Firewall.
> 3. In Windows Firewall, click the Exceptions tab, and then click Add
> Port.
> 4. In the Add a Port dialog box, in the Name box, type SQL Server
> <instanceName>.
> 5. In the Port number box, type the port number of the Database Engine
> instance. Use 1433 for the default instance. Type 1500 if you are
> configuring a named instance and configured a fixed port in the previous
> task. Verify that TCP is selected, and then click OK.
> Connecting to the Database Engine from Another Computer
> Now that you have configured the Database Engine to listen on a fixed port,
|||I have done this same thing and without incident. SQL 2000 client will
connect SQL 2005.
I don't know how to fix your problem but I know it can be fixed.
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:3EC1A2E1-85C8-4525-B25D-6A29287996A2@.microsoft.com...[vbcol=seagreen]
> Hi Rick,
> I have actually read this tutorial but I believe it is based on the
> scenario
> that the client computer will have SQL Server 2005 component installed.
> I'm
> trying to connect from a different computer which has no SQL Server 2005
> component installed. If I understand correctly, SQL Native Client is
> required if I'm trying to use new features in SQL Server 2005.
> Environment:
> Developer edition of SQL Server 2005 is installed on a Windows 2003
> Standard
> Edition with SP1 machine which has no Windows Firewall/ICS service
> running.
> I have enabled the TCP/IP protocol through SQL Server Surface Area
> Configuration. I'm trying to connect from a Windows XP Professional with
> SP2
> machine which has the following exceptions in the Windows Firewall:
> File and Printer Sharing
> Remote Assistance
> MSN Messenger 7.5
> Remote Desktop
> Please note that I have NOT installed anything from SQL Server 2005 CD
> onto
> the Windows XP SP2 machine. I'm trying the connection in the ODBC
> Administrator using SQL Server driver 2000.85.1117.00.
>
> Thanks,
> Peter
> "Rick Byham [MS]" wrote:

How to connect a workstation to SQL Server 2005 thru ODBC?

I have installed a SQL Server 2005 named instance with mixed authentication
on a Windows 2003 Standard Server. SQL Server Service is running under loca
l
system account. I have not changed any default setting.
I want to set up a System DSN in ODBC Data Source Administrator on a Windows
XP SP2 machine to connect to the SQL Server 2005 named instance. But I get
the message Specified SQL Server not found. I have no problem in setting u
p
System DSN to connect to SQL Server 2000 named instances which is in another
Windows 2003 Standard Server. I have not installed anything from SQL Serve
r
2005 onto the Windows XP machine.
Thanks for any help.You didn't mention if the connection attempt was from the same computer. If
you are connecting from a different computer, you probably need to use the
Surface Area Configuration tool, and open the port in the Windows XP
firewall. This tutorial may help you.
Getting Started with the Database Engine
Welcome to the Getting Started with the Database Engine tutorial. This
tutorial is intended for users who are new to SQL Server 2005 and who have
installed Developer, Express, or Evaluation Edition on a computer running
Windows XP Professional Service Pack 1 (SP1).This brief tutorial helps you
get started using the Database Engine.
What You Will Learn
This tutorial shows you how to connect to the Database Engine using SQL
Server Management Studio or Management Studio Express, on both the local
computer and from another computer.
This tutorial is divided into two lessons:
Lesson 1: Connecting to the Database Engine
In this lesson, you will learn how to connect to the Database Engine and
enable additional people to connect.
Lesson 2: Connecting from Another Computer
In this lesson, you will learn how to connect to the Database Engine from a
second computer, including enabling protocols, configuring ports, and
configuring firewall settings.
Requirements
This lesson has no knowledge prerequisites.
Your system must have the following installed to use this tutorial:
a.. Internet Explorer 6.0 or later.
b.. Either SQL Server Management Studio or Management Studio Express.
Lesson 1: Connecting to the Database Engine
When you install the SQL Server 2005 Database Engine, the tools that are
installed depend upon the edition and your setup choices. This lesson
reviews the principal tools, and shows you how to connect and perform a
basic function (authorizing more users).
This lesson contains the following topics:
a.. Tools for Getting Started
b.. Connecting with Management Studio
c.. Authorizing Additional Connections
Tools for Getting Started
The SQL Server 2005 Database Engine ships with a variety of tools. This
topic describes the first tools you will need, and helps you select the
right tool for the job. All tools can be accessed from the Start menu.
Generally, tools such as SQL Server Management Studio are not installed by
default. You must select the tools as part of the client components during
setup. For complete description of the tools described below, search for
them in Books Online. SQL Server 2005 Express Edition contains only a subset
of the tools.
Basic Tools
a.. SQL Server Management Studio is the principal tool for administering
the Database Engine and writing Transact-SQL code. It is hosted in the
Visual Studio shell. It is not included in SQL Server 2005 Express Edition
or SQL Server 2005 Mobile Edition.
b.. SQL Server Management Studio Express is a free, limited version of SQL
Server Management Studio, intended for use with SQL Server 2005 Express
Edition and for users who want the basic features of Management Studio in a
lightweight tool.
c.. SQL Server Surface Area Configuration installs with SQL Server and
lets you enable the server protocols, configure services to start
automatically, and enable some optional features of the Database Engine.
d.. SQL Server Configuration Manager installs with both SQL Server and the
client tools. It lets you enable server protocols, configure protocol
options such as TCP ports, configure server services to start automatically,
and configure client computers to connect in your preferred manner.
Sample Database
SQL Server 2005 includes a sample database called AdventureWorks. This
database is not installed by default. If you wish to experiment with the
AdventureWorks database, you must select it using the Setup program. Most
examples described in Books Online use the AdventureWorks database. For more
information, see Running Setup to Install AdventureWorks Sample Databases
and Samples.
To start SQL Server Management Studio
1. On the Start menu, point to All Programs, point to Microsoft SQL
Server 2005, and then click SQL Server Management Studio.
To start SQL Server Surface Area Configuration or SQL Server Configuration
Manager
1. On the Start menu, point to All Programs, point to Microsoft SQL
Server 2005, point to Configuration Tools, and then click either SQL Server
Surface Area Configuration or SQL Server Configuration Manager.
Connecting with Management Studio
It is easy to connect to the Database Engine from tools running on the same
computer if you know the name of the instance, and if you are connecting as
a member of the Administrators group on the computer. The following
procedures must be performed on the same computer that hosts SQL Server.
To determine the name of the Database Engine instance
1. Log into Windows as a member of the Administrators group, and open
either Management Studio or Management Studio Express Edition.
The Connect to Server dialog box opens.
2. Click Cancel.
3. If Registered Servers is not displayed, on the View menu, click
Registered Servers.
4. With Database Engine selected on the Registered Servers toolbar,
right-click Database Engine, and then click Update Local Server
Registration. All instances of the Database Engine installed on the computer
are displayed. This includes instances of SQL Server 2000. Management Studio
can connect and manage instances of SQL Server 2000 as well as SQL Server
2005. The default instance is unnamed and is shown as the computer name. A
named instance displays as the computer name followed by a backward slash
(\) and then the name of the instance. For SQL Server 2005 Express Edition,
the instance is named <computer_name>\sqlexpress unless the name was changed
during setup.
To verify that the Database Engine is running
1. In Registered Servers, if the name of your instance of SQL Server
has a green dot with a white arrow next to the name, the Database Engine is
running and no further action is necessary.
2. If the name of your instance of SQL Server has a red dot with a
white square next to the name, the Database Engine is stopped. Right-click
the name of the Database Engine, and then click Start. After a confirmation
dialog box, the Database Engine should start and the circle should turn
green.
To connect to the Database Engine
1. On the File menu, click Connect Object Explorer.
The Connect to Server dialog box opens. The Server type box displays the
type that was last used.
2. Select Database Engine.
3. In the Server name box, type the name of the Database Engine
instance.
4. Click Connect.
Authorizing Additional Connections
Now that you have connected to SQL Server as an administrator, one of your
first tasks is to authorize other users to connect. You do this by creating
a login and authorizing that login to access a database as a user. Logins
can be either Windows Authentication logins, which use your Windows
credentials, or SQL Server Authentication logins, which store the
authentication information in SQL Server and are independent of your network
credentials. Use Windows Authentication whenever possible.
Create a Windows Authentication login
1. In the previous task, you connected to the Database Engine using
Management Studio. In Object Explorer, expand your server instance, expand
Security, right-click Logins, and then click New Login.
The Login - New dialog box appears.
2. On the General page, in the Login name box, type a Windows login in
the format <domain>\<login>.
3. In the Default database box, select AdventureWorks if available.
Otherwise select master.
4. On the Server Roles page, if the new login is to be an
administrator, click sysadmin, otherwise leave this blank.
5. On the User Mapping page, select Map for the AdventureWorks
database if it is available. Otherwise select master. Note that the User box
is populated with the login. When closed, the dialog box will create this
user in the database.
6. In the Default Schema box, type dbo to map the login to the
database administrator schema.
7. Accept the default settings for the Securables and Status boxes and
click OK to create the login.
Note:
This is basic information to get you started. SQL Server provides a
rich security environment, and security is obviously an important aspect of
database operations. For more information about security, read the security
sections of Books Online, starting with Security Considerations for
Databases and Database Applications.
Lesson 2: Connecting from Another Computer
To enhance security, the Database Engine of SQL Server 2005 Developer,
Express, and Evaluation Editions cannot be accessed from another computer
when initially installed. This lesson shows you how to enable the protocols,
configure the ports, and configure the Windows Firewall for connecting from
other computers.
This lesson contains the following topics:
a.. Enabling Protocols
b.. Configuring a Fixed Port
c.. Opening Ports in the Firewall
d.. Connecting to the Database Engine from Another Computer
e.. Connecting Using the SQL Server Browser Service
Enabling Protocols
To enhance security, SQL Server 2005 Express Edition Developer Edition and
Evaluation Edition install with only limited network connectivity.
Connections to the Database Engine can be made from tools running the same
computer, but not from other computers. If you are planning to do your
development work on the same computer as the Database Engine, you're done.
Management Studio or Management Studio Express Edition will connect to the
Database Engine using the shared memory protocol, which is already enabled.
If you plan to connect to the Database Engine from another computer, you
must enable a protocol, such as TCP/IP.
How to enable TCP/IP connections from another computer
1. Start SQL Server Surface Area Configuration, and click Surface Area
Configuration for Services.
2. In the Surface Area Configuration for Services and Connections box,
the View by Instance box lists the instances of the Database Engine
installed on the computer. The default instance (an unnamed instance) is
listed as MSSQLSERVER. If you installed a named instance, the name you
provided is listed. SQL Server 2005 Express Edition installs as SQLEXPRESS
unless you changed the name during setup. In the View by Instance box,
expand the instance you wish to configure, expand Database Engine, and then
click Remote Connections.
3. Click Local and remote connections, click Using TCP/IP only, then
click OK and close the tool.
Configuring a Fixed Port
To enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
the Windows Firewall. When SQL Server 2005 Developer, Express, or Evaluation
Edition is running on Windows XP Professional, and you wish to connect to it
from another computer, you must open a communication port in the firewall.
The default instance of the Database Engine listens on port 1433, so you do
not need to configure a fixed port, but named instances including SQL Server
2005 Express Edition listen on dynamic ports. Before you can open a port in
the firewall, you must first configure the Database Engine to listen on a
specific port; otherwise the Database Engine may listen on a different port
each time it is started.
Configure SQL Server to listen on a specific port
1. In SQL Server Configuration Manager, expand SQL Server 2005 Network
Configuration, and then click on the server instance you wish to configure.
2. In the right pane, double-click TCP/IP.
3. In the TCP/IP Properties dialog box, click the IP Addresses tab.
4. In the TCP Port box of the IPAll section, type an available port
number. For this tutorial, we will use 1500.
5. Click OK to close the dialog box, and click OK to the warning that
the service must be restarted.
6. In the left pane, click SQL Server 2005 Services.
7. In the right pane, right-click the instance of SQL Server, and then
click Restart. When the Database Engine restarts, it will listen on port
1500.
Opening Ports in the Firewall
Firewall systems prevent unauthorized access to computer resources. To
enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
Windows Firewall. To connect to SQL Server from another computer, you must
open a port in the firewall.
Important:
Opening ports in your firewall can leave your server exposed to
malicious attacks. Be sure to understand firewall systems before opening
ports. For more information, see Security Considerations for a SQL Server
Installation.
After configuring the Database Engine to use a fixed port, follow the
following instructions to open that port in your Windows Firewall. (You do
not need to configure a fixed port for the default instance, because it is
already fixed on port 1433.)
To open a port in Windows Firewall
1. On the Start menu, click Control Panel.
2. In Control Panel, click Network and Internet Connections, and then
open Windows Firewall.
3. In Windows Firewall, click the Exceptions tab, and then click Add
Port.
4. In the Add a Port dialog box, in the Name box, type SQL Server
<instanceName>.
5. In the Port number box, type the port number of the Database Engine
instance. Use 1433 for the default instance. Type 1500 if you are
configuring a named instance and configured a fixed port in the previous
task. Verify that TCP is selected, and then click OK.
Connecting to the Database Engine from Another Computer
Now that you have configured the Database Engine to listen on a fixed port,
and have opened that port in the firewall, you can connect to SQL Server
from another computer.
When the SQL Server Browser service is running on the server computer, and
when the firewall has opened UDP port 1434, the connection can be made using
the computer name and instance name. To enhance security, our example does
not use the SQL Server Browser service.
To connect to the Database Engine from another computer
1. On a second computer containing the SQL Server 2005 client tools,
log in with an account authorized to connect to SQL Server, and open
Management Studio.
2. In the Connect to Server dialog box, confirm Database Engine in the
Server type box.
3. In the Server name box, type tcp: to specify the protocol, followed
by the computer name, a comma, and the port number. To connect to the
default instance, the port 1433 is implied and can be omitted, so type
tcp:<computer_name>. In our example for a named instance, type
tcp:<computer_name>,1500.
4. In the Authentication box, confirm Window Authentication, and then
click Connect.
Connecting Using the SQL Server Browser Service
The SQL Server Browser service listens for incoming requests for SQL Server
resources and provides information about SQL Server instances installed on
the computer. When the SQL Server Browser service is running, users can
connect to named instances by providing the computer name and instance name,
instead of the computer name and port number. Because SQL Server Browser
receives unauthenticated UDP requests, it is not always turned on during
setup. For a description of the service and an explanation of when it is
turned on, see SQL Server Browser Service.
To use the SQL Server Browser, you must follow the same steps as the
previous task in this lesson, and open UDP port 1434.
This concludes this brief tutorial on basic connectivity. For more
information about configuring server and client connectivity, see Database
Engine Connectivity How-to Topics.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:1ED4DC95-43E3-4647-92B7-2B11D1A2A28C@.microsoft.com...
>I have installed a SQL Server 2005 named instance with mixed authentication
> on a Windows 2003 Standard Server. SQL Server Service is running under
> local
> system account. I have not changed any default setting.
> I want to set up a System DSN in ODBC Data Source Administrator on a
> Windows
> XP SP2 machine to connect to the SQL Server 2005 named instance. But I
> get
> the message Specified SQL Server not found. I have no problem in setting
> up
> System DSN to connect to SQL Server 2000 named instances which is in
> another
> Windows 2003 Standard Server. I have not installed anything from SQL
> Server
> 2005 onto the Windows XP machine.
> Thanks for any help.|||Hi Rick,
I have actually read this tutorial but I believe it is based on the scenario
that the client computer will have SQL Server 2005 component installed. I'
m
trying to connect from a different computer which has no SQL Server 2005
component installed. If I understand correctly, SQL Native Client is
required if I'm trying to use new features in SQL Server 2005.
Environment:
Developer edition of SQL Server 2005 is installed on a Windows 2003 Standard
Edition with SP1 machine which has no Windows Firewall/ICS service running.
I have enabled the TCP/IP protocol through SQL Server Surface Area
Configuration. I'm trying to connect from a Windows XP Professional with SP2
machine which has the following exceptions in the Windows Firewall:
File and Printer Sharing
Remote Assistance
MSN Messenger 7.5
Remote Desktop
Please note that I have NOT installed anything from SQL Server 2005 CD onto
the Windows XP SP2 machine. I'm trying the connection in the ODBC
Administrator using SQL Server driver 2000.85.1117.00.
Thanks,
Peter
"Rick Byham [MS]" wrote:
[vbcol=seagreen]
> You didn't mention if the connection attempt was from the same computer. I
f
> you are connecting from a different computer, you probably need to use the
> Surface Area Configuration tool, and open the port in the Windows XP
> firewall. This tutorial may help you.
> Getting Started with the Database Engine
> Welcome to the Getting Started with the Database Engine tutorial. This
> tutorial is intended for users who are new to SQL Server 2005 and who have
> installed Developer, Express, or Evaluation Edition on a computer running
> Windows XP Professional Service Pack 1 (SP1).This brief tutorial helps you
> get started using the Database Engine.
> What You Will Learn
> This tutorial shows you how to connect to the Database Engine using SQL
> Server Management Studio or Management Studio Express, on both the local
> computer and from another computer.
> This tutorial is divided into two lessons:
> Lesson 1: Connecting to the Database Engine
> In this lesson, you will learn how to connect to the Database Engine and
> enable additional people to connect.
> Lesson 2: Connecting from Another Computer
> In this lesson, you will learn how to connect to the Database Engine from
a
> second computer, including enabling protocols, configuring ports, and
> configuring firewall settings.
> Requirements
> This lesson has no knowledge prerequisites.
> Your system must have the following installed to use this tutorial:
> a.. Internet Explorer 6.0 or later.
> b.. Either SQL Server Management Studio or Management Studio Express.
> Lesson 1: Connecting to the Database Engine
> When you install the SQL Server 2005 Database Engine, the tools that are
> installed depend upon the edition and your setup choices. This lesson
> reviews the principal tools, and shows you how to connect and perform a
> basic function (authorizing more users).
> This lesson contains the following topics:
> a.. Tools for Getting Started
> b.. Connecting with Management Studio
> c.. Authorizing Additional Connections
> Tools for Getting Started
> The SQL Server 2005 Database Engine ships with a variety of tools. This
> topic describes the first tools you will need, and helps you select the
> right tool for the job. All tools can be accessed from the Start menu.
> Generally, tools such as SQL Server Management Studio are not installed by
> default. You must select the tools as part of the client components during
> setup. For complete description of the tools described below, search for
> them in Books Online. SQL Server 2005 Express Edition contains only a subs
et
> of the tools.
> Basic Tools
> a.. SQL Server Management Studio is the principal tool for administering
> the Database Engine and writing Transact-SQL code. It is hosted in the
> Visual Studio shell. It is not included in SQL Server 2005 Express Edition
> or SQL Server 2005 Mobile Edition.
> b.. SQL Server Management Studio Express is a free, limited version of S
QL
> Server Management Studio, intended for use with SQL Server 2005 Express
> Edition and for users who want the basic features of Management Studio in
a
> lightweight tool.
> c.. SQL Server Surface Area Configuration installs with SQL Server and
> lets you enable the server protocols, configure services to start
> automatically, and enable some optional features of the Database Engine.
> d.. SQL Server Configuration Manager installs with both SQL Server and t
he
> client tools. It lets you enable server protocols, configure protocol
> options such as TCP ports, configure server services to start automaticall
y,
> and configure client computers to connect in your preferred manner.
> Sample Database
> SQL Server 2005 includes a sample database called AdventureWorks. This
> database is not installed by default. If you wish to experiment with the
> AdventureWorks database, you must select it using the Setup program. Most
> examples described in Books Online use the AdventureWorks database. For mo
re
> information, see Running Setup to Install AdventureWorks Sample Databases
> and Samples.
> To start SQL Server Management Studio
> 1. On the Start menu, point to All Programs, point to Microsoft SQL
> Server 2005, and then click SQL Server Management Studio.
> To start SQL Server Surface Area Configuration or SQL Server Configuration
> Manager
> 1. On the Start menu, point to All Programs, point to Microsoft SQL
> Server 2005, point to Configuration Tools, and then click either SQL Serve
r
> Surface Area Configuration or SQL Server Configuration Manager.
> Connecting with Management Studio
> It is easy to connect to the Database Engine from tools running on the sam
e
> computer if you know the name of the instance, and if you are connecting a
s
> a member of the Administrators group on the computer. The following
> procedures must be performed on the same computer that hosts SQL Server.
> To determine the name of the Database Engine instance
> 1. Log into Windows as a member of the Administrators group, and ope
n
> either Management Studio or Management Studio Express Edition.
> The Connect to Server dialog box opens.
> 2. Click Cancel.
> 3. If Registered Servers is not displayed, on the View menu, click
> Registered Servers.
> 4. With Database Engine selected on the Registered Servers toolbar,
> right-click Database Engine, and then click Update Local Server
> Registration. All instances of the Database Engine installed on the comput
er
> are displayed. This includes instances of SQL Server 2000. Management Stud
io
> can connect and manage instances of SQL Server 2000 as well as SQL Server
> 2005. The default instance is unnamed and is shown as the computer name. A
> named instance displays as the computer name followed by a backward slash
> (\) and then the name of the instance. For SQL Server 2005 Express Edition
,
> the instance is named <computer_name>\sqlexpress unless the name was chang
ed
> during setup.
> To verify that the Database Engine is running
> 1. In Registered Servers, if the name of your instance of SQL Server
> has a green dot with a white arrow next to the name, the Database Engine i
s
> running and no further action is necessary.
> 2. If the name of your instance of SQL Server has a red dot with a
> white square next to the name, the Database Engine is stopped. Right-click
> the name of the Database Engine, and then click Start. After a confirmatio
n
> dialog box, the Database Engine should start and the circle should turn
> green.
> To connect to the Database Engine
> 1. On the File menu, click Connect Object Explorer.
> The Connect to Server dialog box opens. The Server type box displays the
> type that was last used.
> 2. Select Database Engine.
> 3. In the Server name box, type the name of the Database Engine
> instance.
> 4. Click Connect.
> Authorizing Additional Connections
> Now that you have connected to SQL Server as an administrator, one of your
> first tasks is to authorize other users to connect. You do this by creatin
g
> a login and authorizing that login to access a database as a user. Logins
> can be either Windows Authentication logins, which use your Windows
> credentials, or SQL Server Authentication logins, which store the
> authentication information in SQL Server and are independent of your netwo
rk
> credentials. Use Windows Authentication whenever possible.
> Create a Windows Authentication login
> 1. In the previous task, you connected to the Database Engine using
> Management Studio. In Object Explorer, expand your server instance, expand
> Security, right-click Logins, and then click New Login.
> The Login - New dialog box appears.
> 2. On the General page, in the Login name box, type a Windows login
in
> the format <domain>\<login>.
> 3. In the Default database box, select AdventureWorks if available.
> Otherwise select master.
> 4. On the Server Roles page, if the new login is to be an
> administrator, click sysadmin, otherwise leave this blank.
> 5. On the User Mapping page, select Map for the AdventureWorks
> database if it is available. Otherwise select master. Note that the User b
ox
> is populated with the login. When closed, the dialog box will create this
> user in the database.
> 6. In the Default Schema box, type dbo to map the login to the
> database administrator schema.
> 7. Accept the default settings for the Securables and Status boxes a
nd
> click OK to create the login.
> Note:
> This is basic information to get you started. SQL Server provides a
> rich security environment, and security is obviously an important aspect o
f
> database operations. For more information about security, read the securit
y
> sections of Books Online, starting with Security Considerations for
> Databases and Database Applications.
>
> Lesson 2: Connecting from Another Computer
> To enhance security, the Database Engine of SQL Server 2005 Developer,
> Express, and Evaluation Editions cannot be accessed from another computer
> when initially installed. This lesson shows you how to enable the protocol
s,
> configure the ports, and configure the Windows Firewall for connecting fro
m
> other computers.
> This lesson contains the following topics:
> a.. Enabling Protocols
> b.. Configuring a Fixed Port
> c.. Opening Ports in the Firewall
> d.. Connecting to the Database Engine from Another Computer
> e.. Connecting Using the SQL Server Browser Service
> Enabling Protocols
> To enhance security, SQL Server 2005 Express Edition Developer Edition and
> Evaluation Edition install with only limited network connectivity.
> Connections to the Database Engine can be made from tools running the same
> computer, but not from other computers. If you are planning to do your
> development work on the same computer as the Database Engine, you're done.
> Management Studio or Management Studio Express Edition will connect to the
> Database Engine using the shared memory protocol, which is already enabled
.
> If you plan to connect to the Database Engine from another computer, you
> must enable a protocol, such as TCP/IP.
> How to enable TCP/IP connections from another computer
> 1. Start SQL Server Surface Area Configuration, and click Surface Ar
ea
> Configuration for Services.
> 2. In the Surface Area Configuration for Services and Connections bo
x,
> the View by Instance box lists the instances of the Database Engine
> installed on the computer. The default instance (an unnamed instance) is
> listed as MSSQLSERVER. If you installed a named instance, the name you
> provided is listed. SQL Server 2005 Express Edition installs as SQLEXPRESS
> unless you changed the name during setup. In the View by Instance box,
> expand the instance you wish to configure, expand Database Engine, and the
n
> click Remote Connections.
> 3. Click Local and remote connections, click Using TCP/IP only, then
> click OK and close the tool.
> Configuring a Fixed Port
> To enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
> the Windows Firewall. When SQL Server 2005 Developer, Express, or Evaluati
on
> Edition is running on Windows XP Professional, and you wish to connect to
it
> from another computer, you must open a communication port in the firewall.
> The default instance of the Database Engine listens on port 1433, so you d
o
> not need to configure a fixed port, but named instances including SQL Serv
er
> 2005 Express Edition listen on dynamic ports. Before you can open a port i
n
> the firewall, you must first configure the Database Engine to listen on a
> specific port; otherwise the Database Engine may listen on a different por
t
> each time it is started.
> Configure SQL Server to listen on a specific port
> 1. In SQL Server Configuration Manager, expand SQL Server 2005 Netwo
rk
> Configuration, and then click on the server instance you wish to configure
.
> 2. In the right pane, double-click TCP/IP.
> 3. In the TCP/IP Properties dialog box, click the IP Addresses tab.
> 4. In the TCP Port box of the IPAll section, type an available port
> number. For this tutorial, we will use 1500.
> 5. Click OK to close the dialog box, and click OK to the warning tha
t
> the service must be restarted.
> 6. In the left pane, click SQL Server 2005 Services.
> 7. In the right pane, right-click the instance of SQL Server, and th
en
> click Restart. When the Database Engine restarts, it will listen on port
> 1500.
> Opening Ports in the Firewall
> Firewall systems prevent unauthorized access to computer resources. To
> enhance security, Windows XP Professional Service Pack 2 (SP2) turns on
> Windows Firewall. To connect to SQL Server from another computer, you must
> open a port in the firewall.
> Important:
> Opening ports in your firewall can leave your server exposed to
> malicious attacks. Be sure to understand firewall systems before opening
> ports. For more information, see Security Considerations for a SQL Server
> Installation.
>
> After configuring the Database Engine to use a fixed port, follow the
> following instructions to open that port in your Windows Firewall. (You do
> not need to configure a fixed port for the default instance, because it is
> already fixed on port 1433.)
> To open a port in Windows Firewall
> 1. On the Start menu, click Control Panel.
> 2. In Control Panel, click Network and Internet Connections, and the
n
> open Windows Firewall.
> 3. In Windows Firewall, click the Exceptions tab, and then click Add
> Port.
> 4. In the Add a Port dialog box, in the Name box, type SQL Server
> <instanceName>.
> 5. In the Port number box, type the port number of the Database Engi
ne
> instance. Use 1433 for the default instance. Type 1500 if you are
> configuring a named instance and configured a fixed port in the previous
> task. Verify that TCP is selected, and then click OK.
> Connecting to the Database Engine from Another Computer
> Now that you have configured the Database Engine to listen on a fixed port,[/vbcol
]|||I have done this same thing and without incident. SQL 2000 client will
connect SQL 2005.
I don't know how to fix your problem but I know it can be fixed.
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:3EC1A2E1-85C8-4525-B25D-6A29287996A2@.microsoft.com...[vbcol=seagreen]
> Hi Rick,
> I have actually read this tutorial but I believe it is based on the
> scenario
> that the client computer will have SQL Server 2005 component installed.
> I'm
> trying to connect from a different computer which has no SQL Server 2005
> component installed. If I understand correctly, SQL Native Client is
> required if I'm trying to use new features in SQL Server 2005.
> Environment:
> Developer edition of SQL Server 2005 is installed on a Windows 2003
> Standard
> Edition with SP1 machine which has no Windows Firewall/ICS service
> running.
> I have enabled the TCP/IP protocol through SQL Server Surface Area
> Configuration. I'm trying to connect from a Windows XP Professional with
> SP2
> machine which has the following exceptions in the Windows Firewall:
> File and Printer Sharing
> Remote Assistance
> MSN Messenger 7.5
> Remote Desktop
> Please note that I have NOT installed anything from SQL Server 2005 CD
> onto
> the Windows XP SP2 machine. I'm trying the connection in the ODBC
> Administrator using SQL Server driver 2000.85.1117.00.
>
> Thanks,
> Peter
> "Rick Byham [MS]" wrote:
>