clear log: instance

Showing posts with label instance. Show all posts

Wednesday, March 28, 2012

How to connect?

Hi All,
I'd like to connect to a SQL Server 2000 instance which listens to not the
default 1433 port. Can anyone help me with how to register the server in EM
and how to connect to the server with QA?
Thanks.
Kolos
Hello,
1 option:- Create a client Alias using Client Network Utility defining the
correct PORT and then use the Alias to register and use in Query Analyzer
2 option: While connecting give IPADDRESS,Port number in the server window.
(Eg: 10.222.1.100,1522)
Thanks
Hari
"Kolos" <Kolos@.discussions.microsoft.com> wrote in message
news:0AE8AA45-09F8-43F3-9CE7-ADCD224DB393@.microsoft.com...
> Hi All,
> I'd like to connect to a SQL Server 2000 instance which listens to not the
> default 1433 port. Can anyone help me with how to register the server in
> EM
> and how to connect to the server with QA?
> Thanks.
> Kolos

How to connect?

Hi All,
I'd like to connect to a SQL Server 2000 instance which listens to not the
default 1433 port. Can anyone help me with how to register the server in EM
and how to connect to the server with QA?
Thanks.
KolosHello,
1 option:- Create a client Alias using Client Network Utility defining the
correct PORT and then use the Alias to register and use in Query Analyzer
2 option: While connecting give IPADDRESS,Port number in the server window.
(Eg: 10.222.1.100,1522)
Thanks
Hari
"Kolos" <Kolos@.discussions.microsoft.com> wrote in message
news:0AE8AA45-09F8-43F3-9CE7-ADCD224DB393@.microsoft.com...
> Hi All,
> I'd like to connect to a SQL Server 2000 instance which listens to not the
> default 1433 port. Can anyone help me with how to register the server in
> EM
> and how to connect to the server with QA?
> Thanks.
> Kolos

how to connect to SQL server express 2005 database at the same time from both SSMSE and VB2005 a

Here is the situation:

I have SQL server express 2005 installed on my pc as instance SQLEXPRESS.

I have created a Visual Basic applicaion with the following as connection to the SQL server express 2005 running on the same PC:
****************************************************************************************************
Dim lconnectionString As String
Dim builder As New SqlConnectionStringBuilder
Dim cmd As New SqlCommand
Dim reader As SqlDataReader
Dim parameter As SqlParameter

builder("Data Source") = ".\SQLEXPRESS"
builder("Initial Catalog") = ""
builder("AttachDbFilename") = "C:\My Documents\Visual Studio 2005\Projects\abc\abc\abc.mdf"
builder("Integrated Security") = True
builder("User Instance") = True
lconnectionString = builder.ConnectionString

Dim sqlConnection1 As New SqlConnection(lconnectionString)

cmd.CommandText = "SP_add_collection"
cmd.CommandType = CommandType.StoredProcedure
cmd.Connection = sqlConnection1

sqlConnection1.Open()
*******************************************************************************************************************

It seems that i can not connect to the abc.mdf in SSMSE while the VB program is running. (ERROR:
Database 'C:\My Documents\Visual Studio 2005\Projects\abc\abc\abc.mdf' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. (.Net SqlClient Data Provider) )

If i connect to the abc.mdf first in SSMSE, then run the VB program afterwards, it gives me the error on this line -- sqlConnection1.Open()

I want to be able to access the abc.mdf database with both SSMSE and VB at the same time. Could anyone help me on this ?

Thanks very much !

apple

I'll go out on a limb here and assume that you've attached the .mdf to SSMSE which is essentially just a pointer to the db. It is not technically a SQL database.

When you're connecting the .mdf through code, use the same connection as if you were connecting to MS Access.

If you have a stored procedure that uses the .mdf, use a sql connection.

Good luck,

Adamus

|||yes, i attached the .mdf file to the SSMSE. and i call the stored procedures in the VB application.

I want to see the result of data change of the VB application in the SSMSE right away, while the application updates the date in the table. is it possible ?|||

Yes it's possible but you have to connect directly to the .mdf not SSMS.

Adamus

sql

how to connect to SQL server express 2005 database at the same time from both SSMSE and VB20

Here is the situation:

I have SQL server express 2005 installed on my pc as instance SQLEXPRESS.

If i connect to the abc.mdf first in SSMSE, then run the VB program afterwards, it gives me the error on this line -- sqlConnection1.Open()

I want to be able to access the abc.mdf database with both SSMSE and VB at the same time. Could anyone help me on this ?

Thanks very much !

apple

I'll go out on a limb here and assume that you've attached the .mdf to SSMSE which is essentially just a pointer to the db. It is not technically a SQL database.

When you're connecting the .mdf through code, use the same connection as if you were connecting to MS Access.

If you have a stored procedure that uses the .mdf, use a sql connection.

Good luck,

Adamus

|||yes, i attached the .mdf file to the SSMSE. and i call the stored procedures in the VB application.

I want to see the result of data change of the VB application in the SSMSE right away, while the application updates the date in the table. is it possible ?|||

Yes it's possible but you have to connect directly to the .mdf not SSMS.

Adamus

How to connect to SQL Server 2000 and SQL Server 2005 in one computer??

Hi All!!!

In my Computer has MS SQL Server 2000(with default Instance) and now I Install MS SQL server 2005(with Instance name: SQL2005 ). Now I want to write Web Application to connect to the both databases (SQL Server 2000 and MS SQL Server 2005), How to Add connection string in my web.config to do it.

Help me ?

Thanks & Regards,

You can put the two connection strings in the web.config file and use either in your code..

|||

Hi !!!

Thanks for your support !!! Please give me the connection string to connect to SQL Server 2000 & SQL Server 2005.

Thanks

|||

check out www.connectionstrings.com

Friday, March 23, 2012

How to connect second instance if server has two instance?

We have one sql server 2005 machine which have two instance named:
DEVSQL(default server named when first installed) and DEVSQL\TESTING (second
installed). On the client, I can connect default instance, but the second
instance cannot connect. What settings I should to do?
Hi,
you will have to provide either the instancename or the portnumber in
the conenctionstring or you connection dialog of choice:
Servername\InstanceName (If SQL Browser is activated it will redirect
the request to the appropiate listerner of the instance
or
Servername,portnumber
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de

How to connect remote SQL Server?

I wnat to connect to remote sql server 2005, I do the following steps:

Enable remote connections on the instance of SQL Server that you want to connect to from a remote computer.
Turn on the SQL Server Browser service.
Configure the firewall to allow network traffic that is related to SQL Server and to the SQL Server Browser service.

sp_addlogin 'Wind','ack@.123','db'

but still can't login,tips as follwing:

Error:18452

Why? Must use "SQL Server Authentication" connect?

YOu are trying to connect with SQL Server Authenitcation, but you only have Windows Authentication enabled. See the Screencast on my site for more information how to switch the Authentication mode.

Jens K. Suessmeyer

http://www.sqlserver2005.de

Wednesday, March 21, 2012

How to connect instance on local server

hi!
I have a question about connecting instance on local server
I install MS SQL Server 2000 first
and then install MS SQL Server 2005.
2005 has an instance name called "2005"
I use Microsoft SQL Server Management Studio and log into 2000
I want to select data from 2005
so I write a script "SELECT * FROM [local\2005].TESTDB.dbo.TEST
but it fail..
I also try following name
[local$2005].TESTDB.dbo.TEST but also fail
How can I connect these two SQL Server?
Can anyone give me a advice?
Thanks a lot!You can create a likned server between the two instances. register either
the 2000 in 2005 or the other way around. Once a linked server is created,
you can execute a query similar to this
SELECT something FROM [server\instance].db.schema.table
You can do a lot of things in here - create a network alias for an instance
name to make it simple if you don't want to use a server\instance name
calls, create a DNS entry that points to the instance name, etc.
"YesGoGoGo" <YesGoGoGo@.gmail.com> wrote in message
news:1185939323.853710.99990@.e16g2000pri.googlegroups.com...
> hi!
> I have a question about connecting instance on local server
> I install MS SQL Server 2000 first
> and then install MS SQL Server 2005.
> 2005 has an instance name called "2005"
> I use Microsoft SQL Server Management Studio and log into 2000
> I want to select data from 2005
> so I write a script "SELECT * FROM [local\2005].TESTDB.dbo.TEST
> but it fail..
> I also try following name
> [local$2005].TESTDB.dbo.TEST but also fail
> How can I connect these two SQL Server?
> Can anyone give me a advice?
> Thanks a lot!
>

How to connect instance on local server

hi!
I have a question about connecting instance on local server
I install MS SQL Server 2000 first
and then install MS SQL Server 2005.
2005 has an instance name called "2005"
I use Microsoft SQL Server Management Studio and log into 2000
I want to select data from 2005
so I write a script "SELECT * FROM [local\2005].TESTDB.dbo.TEST
but it fail..
I also try following name
[local$2005].TESTDB.dbo.TEST but also fail
How can I connect these two SQL Server?
Can anyone give me a advice?
Thanks a lot!
You can create a likned server between the two instances. register either
the 2000 in 2005 or the other way around. Once a linked server is created,
you can execute a query similar to this
SELECT something FROM [server\instance].db.schema.table
You can do a lot of things in here - create a network alias for an instance
name to make it simple if you don't want to use a server\instance name
calls, create a DNS entry that points to the instance name, etc.
"YesGoGoGo" <YesGoGoGo@.gmail.com> wrote in message
news:1185939323.853710.99990@.e16g2000pri.googlegro ups.com...
> hi!
> I have a question about connecting instance on local server
> I install MS SQL Server 2000 first
> and then install MS SQL Server 2005.
> 2005 has an instance name called "2005"
> I use Microsoft SQL Server Management Studio and log into 2000
> I want to select data from 2005
> so I write a script "SELECT * FROM [local\2005].TESTDB.dbo.TEST
> but it fail..
> I also try following name
> [local$2005].TESTDB.dbo.TEST but also fail
> How can I connect these two SQL Server?
> Can anyone give me a advice?
> Thanks a lot!
>

How to connect instance on local server

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:
>

Friday, February 24, 2012

how to combine two different SQL server data instance into one db?

I'd like to know how I can combine two tables from two different sql instances ito one db?

thanks.

Volkan, can you provide a little more info?

Are you trying move the data from sql instance 1 and sql instance 2 into a new database on sql instance 3?

Are you asking how you can query the data from two different instances?

You can query separate instances by using a four-part qualifier if the instances are defined as linked servers.

select * from [servername].[databasename].[schema].[tablename]

Example: server = MySQL1, database = MyDatabase, schema = dbo, table = MyTable

select * from MySQL1.MyDatabase.dbo.MyTable

|||

If both the DBs are on same Server and the current user have access permission on both database then you can use the following query..

Select SomeColumns From CurrentDBName..TableName
Select SomeColumns From OtherDBName..TableName

If the databases are on different Server then you have to use the Linked Server..

EXEC sp_addlinkedserver @.server = 'SERVER', @.provider = 'SQLOLEDB.1', @.srvproduct = '', @.provstr = 'Privider=SQLOLEDB.1;Data Source=TargetServer;Initial Catalog=Database'

go
Exec sp_addlinkedsrvlogin @.rmtsrvname = 'SERVER', @.useself = true, @.locallogin = null, @.rmtuser = 'Userid', @.rmtpassword = 'Password'

On your SP you can use..

Select * From OpenQuery(MyRemoteServer, 'Select * From Sysobjects')

--OR

Select * From MyRemoteServer.DatabaseName.dbo.Sysobjects

Wednesday, March 28, 2012

How to connect?

How to connect?

how to connect to SQL server express 2005 database at the same time from both SSMSE and VB2005 a

how to connect to SQL server express 2005 database at the same time from both SSMSE and VB20

How to connect to SQL Server 2000 and SQL Server 2005 in one computer??

Friday, March 23, 2012

How to connect second instance if server has two instance?

How to connect remote SQL Server?

Wednesday, March 21, 2012

How to connect instance on local server

How to connect instance on local server

How to connect instance on local server

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

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

Friday, February 24, 2012

how to combine two different SQL server data instance into one db?

clear log

Blog Archive

About Me