how to connect to ssis service - The RPC server is unavailable err

Hi
I am trying to connect to ssis service on remote machine using the sql 2005
management studio
I get the following error :
TITLE: Connect to Server
Cannot connect to <servername>.
Connect to SSIS Service on machine "<servername>" failed:
The RPC server is unavailable.
What do I miss please help
Best regards
Meron FridmanDid you figure out a solution ' I have the same problem
--
homebre
----
homebrew's Profile: http://www.dbtalk.net/m5
View this thread: http://www.dbtalk.net/t29008|||I've got the same problem in a two-node active/active environment.
Anyone got any further info?
"homebrew" wrote:
> Did you figure out a solution ' I have the same problem.
>
> --
> homebrew
> ---
> homebrew's Profile: http://www.dbtalk.net/m55
> View this thread: http://www.dbtalk.net/t290084
> .
>|||I found out that one of our developers (developer #1) wasn't having an
problems, and that he had used a different disk to install on hi
desktop. So then developer #2 used his disk, and her problem went away
I had already put in a call to Microsoft, and we tested my RPC port
and they seemed fine. So I think I got a bad disk ... perhaps som
file is corrupted ?
Then he had another utility for me to try, but I haven't bothered yet
since I'm pretty sure it's the disk, and not something on my desktop
--
homebre
----
homebrew's Profile: http://www.dbtalk.net/m5
View this thread: http://www.dbtalk.net/t29008sql

how to connect to ssis service - The RPC server is unavailable err

Hi
I am trying to connect to ssis service on remote machine using the sql 2005
management studio
I get the following error :
TITLE: Connect to Server
Cannot connect to <servername>.
Connect to SSIS Service on machine "<servername>" failed:
The RPC server is unavailable.
What do I miss please help
Best regards
Meron Fridman
Did you figure out a solution ? I have the same problem.
homebrew
homebrew's Profile: http://www.dbtalk.net/m55
View this thread: http://www.dbtalk.net/t290084

how to connect to ssis service - The RPC server is unavailable err

Hi
I am trying to connect to ssis service on remote machine using the sql 2005
management studio
I get the following error :
TITLE: Connect to Server
Cannot connect to <servername>.
Connect to SSIS Service on machine "<servername>" failed:
The RPC server is unavailable.
What do I miss please help
Best regards
Meron FridmanDid you figure out a solution ' I have the same problem.
homebrew
---
homebrew's Profile: http://www.dbtalk.net/m55
View this thread: http://www.dbtalk.net/t290084|||I found out that one of our developers (developer #1) wasn't having any
problems, and that he had used a different disk to install on his
desktop. So then developer #2 used his disk, and her problem went away.
I had already put in a call to Microsoft, and we tested my RPC ports
and they seemed fine. So I think I got a bad disk ... perhaps some
file is corrupted ?
Then he had another utility for me to try, but I haven't bothered yet,
since I'm pretty sure it's the disk, and not something on my desktop.
homebrew
---
homebrew's Profile: http://www.dbtalk.net/m55
View this thread: http://www.dbtalk.net/t290084

How to connect to sql server on another machine through asp.net

Hi All,

I have been struggling with this problem for quite some time. Basically
i have an asp page (on the ISP server) that I want to connect to a sql
server on another machine (on my server) and I have been trying to
figure out how to do this. I tried to connect using an ip address in
the data source and it did not work. The asp.net code looks something
like this:

Conn.Open ("Provider=SQLOLEDB;Password=xxxx;Persist Security
Info=True;User ID=xxxx;Initial Catalog=mssqlxxx;Data
Source=xx.xxx.xxx.xxx,1433;Network Library=dbmssocn")

That did not work. Gave me an access denied or sql server does not
exist error. I tried playing around with or without the 1433 port,
still no luck.

Is there something I need to set up on sql server in order for me to
connect to this?? Can someone give me some suggestion how i can connect
to another computer?

My ISP offers sql server support and they give me an ip address to
connect directly to the sql server, code looks something like this:

conMyData = New SqlConnection( "Server=xxxxxxxxx.registeredsite.com;
UID=userxxxxxx; PWD=xxxxxx;Database=samplecom" )

now, my question is, how do I set up my sql server to have an ip
address so i can connect??

so i see 2 possible w ays to do this but i have no clue to make this
work. Any help is appreciated.This article might be useful:

http://www.aspfaq.com/show.asp?id=2126

Simon

How to connect to SQL Server 2K without the machine name ?

With SQL Server 7, I could connect to a "local" server

driver={SQL Server};server={Local};uid=sa;pwd=password;

with SQL Server 2K it seems to need the computer name

driver={SQL Server};server=MachineName\InstanceName;uid=sa;pwd =password;

How can I replace "MachineName\InstanceName" by "{Local}"Originally posted by Karolyn
With SQL Server 7, I could connect to a "local" server

driver={SQL Server};server={Local};uid=sa;pwd=password;

with SQL Server 2K it seems to need the computer name

driver={SQL Server};server=MachineName\InstanceName;uid=sa;pwd =password;

How can I replace "MachineName\InstanceName" by "{Local}"

Is the machine you connecting to your local machine?|||yeap !|||if its the default instance of sql server 2000

Provider=SQLOLEDB.1;Persist Security Info=False;Connect Timeout=0;User ID=user;Initial Catalog=dbname;Data Source=local;PASSWORD=password;

else

Provider=SQLOLEDB.1;Persist Security Info=False;Connect Timeout=0;User ID=user;Initial Catalog=dbname;Data Source=local\instancename;PASSWORD=password;|||Originally posted by Karolyn
yeap !

did you try editing your sql server properties?? are you using the right password? cause when you connect to your local machine you normally use use windows and not sql and windows to connect ...try connecting with windows authentication...hope this helps..it should work ..that is what i did...providing other users dont connect to your local machine|||Data Source=local\mercure

The connection does'nt find the server|||Originally posted by Karolyn
Data Source=local\mercure

The connection does'nt find the server

Edit your sql server properties|||where do I get them edited ?|||1
ProductName NULL Microsoft SQL Server 2
ProductVersion 524288 8.00.760 3
Language 1036 Franais (France) 4
Platform NULL NT INTEL X86 5
Comments NULL NT INTEL X86 6
CompanyName NULL Microsoft Corporation 7
FileDescription NULL SQL Server Windows NT 8
FileVersion NULL 2000.080.0760.00 9
InternalName NULL SQLSERVR 10
LegalCopyright NULL 1988-2003 Microsoft Corp. All rights reserved. 11
LegalTrademarks NULL Microsoft is a registered trademark of Microsoft Corporation. Windows(TM) is a trademark of Microsoft Corporation 12
OriginalFilename NULL SQLSERVR.EXE 13
PrivateBuild NULL NULL 14
SpecialBuild 49807360 NULL 15
WindowsVersion 170393861 5.1 (2600) 16
ProcessorCount 1 1 17
ProcessorActiveMask 1 00000001 18
ProcessorType 586 PROCESSOR_INTEL_PENTIUM 19
PhysicalMemory 503 503 (527941632) 20
Product ID NULL NULL|||Originally posted by Karolyn
where do I get them edited ?

right click on (local)windows nt then go to edit sql server properties and change it theresql

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 to my MSDE 2000 Rel A

Hi,

I only have Framework installed on my machine, and I also installed MSDE 2000 Rel. A, using the following command:
C:\MSDERelA\setup.exe SAPWD="myPass" INSTANCENAME="myXP"

I can see that the service for this app is running. Though, I could not connect to it using oSql command like the following:
osql -S(local)\myXP -E
or
osql -S(local)\myXP -Usa, and supply the password "myPass".

The message was:
[DBMSLPCN]SQL Server does not exist or access denied.
[DBMSLPCN]ConnectionOpen (Connect()).

Any response would be appreciated.

---

Subi_IHave you tried

osql -L

to verify the instance name?

If that doesn't help you may also want to check out this link|||Hi McMurdo,

Thanks. The command did help to find my database (my initial post was wrong in specifying the instance name).
And the link really helps for managing MSDE without UI tools.

Thanks,

---

Subi_I

How to Connect to Analysis Services from Client Management Studio?

From my client machine, I have no trouble accessing the Database Engine of my 2005 server in SQL Server Management Studio since I can use SQL Server Authentication. However, Analysis Services (at least how my server is configured right now) only allows Windows Authentication and I can connect. For what it's worth, I can't connect to the Database Engine either on my client using Windows Authentication.

What do I need to do to connect to Analysis Services from my client Management Studio?Like AS2K (and in fact all previous versions of OLAP and Analysis Services), we only support trusted connections from users to AS (both for queries and for administration/operators).

When Analysis Services itself connects to the backend RDBMS, that can be either trusted or SQL logins.

_-_-_ Dave|||

Dave Wickert wrote:

Like AS2K (and in fact all previous versions of OLAP and Analysis Services), we only support trusted connections from users to AS (both for queries and for administration/operators).

When Analysis Services itself connects to the backend RDBMS, that can be either trusted or SQL logins.

_-_-_ Dave

Dave, thanks for the reply. So how do I enable "trusted" logins for AS, if that's possible that is?|||I figured it out.
I had to make an exception for port 2383 (or whatever the default port is for Analysis Services) in Windows Firewall on the Analysis Services server.|||

Dear Dave ,

I am slightly less experienced , and wonder if you could answer some questions for me .

I am running MsSQL2005 and AS on a server .I have built cubes in server .Have had great difficulty in browsing the cube from any remote machine .

Initial problems were associated with the AS server not being able to authenticate the client .

I then put the server and client into the same domain .

I registered an existing user in the domain , into the server users , as member of the various sql groups (olap and other ) .

In the server (AS) user groups , should there be an OLAP administrator group.? I see only an OLAP user group ?

I also granted this domain user login to the sqlserver .

The client is now able to connect to the sqlserver and the Analysis server , using "windows authentication" with one catch .(Previously the cliebnt could connect to the sqlserver using username -pwd authentication .

There are no AS databases listed , no cubes shown etc . The client also has no authority to create a new database in the analysis server .

I am just wondering , what are all the prerequisites to get the client to be able to view the analysis service cubes ?

How can one verify that you have correctly setup the windows authentication required for AS , while you are logged into the server and sql manager ?

What is the correct setting for datasource property ?

Sorry for making such a long story .

any comments appreciated

How to Connect to Analysis Services from Client Management Studio?

From my client machine, I have no trouble accessing the Database Engine of my 2005 server in SQL Server Management Studio since I can use SQL Server Authentication. However, Analysis Services (at least how my server is configured right now) only allows Windows Authentication and I can connect. For what it's worth, I can't connect to the Database Engine either on my client using Windows Authentication.

What do I need to do to connect to Analysis Services from my client Management Studio?
Like AS2K (and in fact all previous versions of OLAP and Analysis Services), we only support trusted connections from users to AS (both for queries and for administration/operators).

When Analysis Services itself connects to the backend RDBMS, that can be either trusted or SQL logins.

_-_-_ Dave|||

Dave Wickert wrote:

Like AS2K (and in fact all previous versions of OLAP and Analysis Services), we only support trusted connections from users to AS (both for queries and for administration/operators).

When Analysis Services itself connects to the backend RDBMS, that can be either trusted or SQL logins.

_-_-_ Dave

Dave, thanks for the reply. So how do I enable "trusted" logins for AS, if that's possible that is?
|||I figured it out.
I had to make an exception for port 2383 (or whatever the default port is for Analysis Services) in Windows Firewall on the Analysis Services server.
|||

Dear Dave ,

I am slightly less experienced , and wonder if you could answer some questions for me .

I am running MsSQL2005 and AS on a server .I have built cubes in server .Have had great difficulty in browsing the cube from any remote machine .

Initial problems were associated with the AS server not being able to authenticate the client .

I then put the server and client into the same domain .

I registered an existing user in the domain , into the server users , as member of the various sql groups (olap and other ) .

In the server (AS) user groups , should there be an OLAP administrator group.? I see only an OLAP user group ?

I also granted this domain user login to the sqlserver .

The client is now able to connect to the sqlserver and the Analysis server , using "windows authentication" with one catch .(Previously the cliebnt could connect to the sqlserver using username -pwd authentication .

There are no AS databases listed , no cubes shown etc . The client also has no authority to create a new database in the analysis server .

I am just wondering , what are all the prerequisites to get the client to be able to view the analysis service cubes ?

How can one verify that you have correctly setup the windows authentication required for AS , while you are logged into the server and sql manager ?

What is the correct setting for datasource property ?

Sorry for making such a long story .

any comments appreciated

How to Connect to a SQL Server thru a firewall

Hi, Guru,
I have a SQL Server running behind a firewall. I also have a client
installed on my local machine. How should I configure the client to
connect to the server? What port do I need to ask the network/security
admin to open on the firewall? All installation on the server and on the
client are default. I am not familiar with SQL Server, but I have some
common sense. What should I put in the "Server Alias"? The IP of the SQL
Server? What if I run a named instance on the server. Any special
configuration I need to do on Client Network Utility?
If you could show me step by step, it would be great. If you can point me
to some online reference, it will be also great.
Any of you help is appreciated.
ChopinThe default sql server tcp port is 1433. So if you have to connect to a
server behind a firewall, you have to ask the network team to open this
port. To make sure it's working you can run the following command from the
client machine:
telnet servername_or_ip 1433
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"Chopin Hu" <huchopin@.yahoo.com> wrote in message
news:ux7cmyGAEHA.3452@.TK2MSFTNGP11.phx.gbl...
> Hi, Guru,
> I have a SQL Server running behind a firewall. I also have a client
> installed on my local machine. How should I configure the client to
> connect to the server? What port do I need to ask the network/security
> admin to open on the firewall? All installation on the server and on the
> client are default. I am not familiar with SQL Server, but I have some
> common sense. What should I put in the "Server Alias"? The IP of the
SQL
> Server? What if I run a named instance on the server. Any special
> configuration I need to do on Client Network Utility?
> If you could show me step by step, it would be great. If you can point
me
> to some online reference, it will be also great.
> Any of you help is appreciated.
> Chopin
>|||try this
http://support.microsoft.com/defaul...kb;en-us;287932
Br,
Mark.
"Chopin Hu" <huchopin@.yahoo.com> wrote in message
news:ux7cmyGAEHA.3452@.TK2MSFTNGP11.phx.gbl...
> Hi, Guru,
> I have a SQL Server running behind a firewall. I also have a client
> installed on my local machine. How should I configure the client to
> connect to the server? What port do I need to ask the network/security
> admin to open on the firewall? All installation on the server and on the
> client are default. I am not familiar with SQL Server, but I have some
> common sense. What should I put in the "Server Alias"? The IP of the
SQL
> Server? What if I run a named instance on the server. Any special
> configuration I need to do on Client Network Utility?
> If you could show me step by step, it would be great. If you can point
me
> to some online reference, it will be also great.
> Any of you help is appreciated.
> Chopin
>sql

How to Connect to a SQL Server thru a firewall

Hi, Guru,
I have a SQL Server running behind a firewall. I also have a client
installed on my local machine. How should I configure the client to
connect to the server? What port do I need to ask the network/security
admin to open on the firewall? All installation on the server and on the
client are default. I am not familiar with SQL Server, but I have some
common sense. What should I put in the "Server Alias"? The IP of the SQL
Server? What if I run a named instance on the server. Any special
configuration I need to do on Client Network Utility?
If you could show me step by step, it would be great. If you can point me
to some online reference, it will be also great.
Any of you help is appreciated.
ChopinThe default sql server tcp port is 1433. So if you have to connect to a
server behind a firewall, you have to ask the network team to open this
port. To make sure it's working you can run the following command from the
client machine:
telnet servername_or_ip 1433
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"Chopin Hu" <huchopin@.yahoo.com> wrote in message
news:ux7cmyGAEHA.3452@.TK2MSFTNGP11.phx.gbl...
> Hi, Guru,
> I have a SQL Server running behind a firewall. I also have a client
> installed on my local machine. How should I configure the client to
> connect to the server? What port do I need to ask the network/security
> admin to open on the firewall? All installation on the server and on the
> client are default. I am not familiar with SQL Server, but I have some
> common sense. What should I put in the "Server Alias"? The IP of the
SQL
> Server? What if I run a named instance on the server. Any special
> configuration I need to do on Client Network Utility?
> If you could show me step by step, it would be great. If you can point
me
> to some online reference, it will be also great.
> Any of you help is appreciated.
> Chopin
>|||try this
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
Br,
Mark.
"Chopin Hu" <huchopin@.yahoo.com> wrote in message
news:ux7cmyGAEHA.3452@.TK2MSFTNGP11.phx.gbl...
> Hi, Guru,
> I have a SQL Server running behind a firewall. I also have a client
> installed on my local machine. How should I configure the client to
> connect to the server? What port do I need to ask the network/security
> admin to open on the firewall? All installation on the server and on the
> client are default. I am not familiar with SQL Server, but I have some
> common sense. What should I put in the "Server Alias"? The IP of the
SQL
> Server? What if I run a named instance on the server. Any special
> configuration I need to do on Client Network Utility?
> If you could show me step by step, it would be great. If you can point
me
> to some online reference, it will be also great.
> Any of you help is appreciated.
> Chopin
>

How to Connect to a SQL server on a deferent machine using ASP.Net?

Hi,

I am trying to connect to a SQL server on a deferent machine using ASP.Net written in C#. The machine on which the SQL server reside dose not have the ASPNET user and the authentication is falling. Any ideas on how to connect using a different User. I changed the ASP.Net service on my machine to run as a deferent user MyUser, which is a domain user that have access to the server machine?

Note: We can not change the privileges on the server side.

Thanks.

RH

Hi,

I am looking to run a web service as a deferent user; it is running, as ASPNET and I would like it to run as a domain user. I am not sure if this is a configuration issue in the Dev studio. Please help.

Thanks.

Rafat

|||

You should post on an ASP.Net forum for instructions on how to set a specific login to be used by your application for connecting to SQL Server.

If you have questions about how to setup such a login in SQL Server, let us know.

Thanks
Laurentiu

|||

Please don't open different threads on the same topic.

Thanks
Laurentiu

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 Access database to SQL server

Hai,
I want to Convert remote Ms access data to sqlserver data.
Here i am using FTP Task in DTS for downloading Ms Access database to local machine.
After that, I convert it to sql data.
But, most of time, With download the mdb file, the message 'Opreation sucessfully' display.
Please give solution for this.
With regards,
dharmaprakash.
**********************************************************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...Please do not post separately in different groups.
Whats the matter if its performed successfully.
Jens Süßmeyer.

How to configure sql server

Hi All,

Here is my question

What might you configure on a SQL Server so that a Web server running
on the same machine, with limited memory, will continue to perform
optimally?

Thank you
Rajuraju.angani@.gmail.com (Raju) wrote in message news:<4bf5a0e7.0409291458.336cc521@.posting.google.com>...
> Hi All,
> Here is my question
> What might you configure on a SQL Server so that a Web server running
> on the same machine, with limited memory, will continue to perform
> optimally?
> Thank you
> Raju

Hallo,
My configuration of server: dual PentiumIII(copermine)/768MB RAM/
On it IIS 6.0 runing.

How to configure connection string for remote server?

Sorry for the newbie question, but...

I have developed a website on my local development machine. When I create the connections string VS automatically creates a path to my local hard drive inside the string.

Data Source=.\SQLEXPRESS;AttachDbFilename="C:\Documents and Settings\Mike\My Documents\Visual Studio 2005\WebSites\PostAlertz\App_Data\PADatabase.mdf";Integrated Security=True;Connect Timeout=30;User Instance=True

However, when I deploy this website to a remote server, SQLExpress tries to attach to the file using the wrong path. How do I fix this?

Your patience is appreciated...

Hi

Here is a sample connection string,and you can find more onhttp://www.connectionstrings.com/:

Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;

HOW-TO: Database from VWD to Shared Host tells you how to copy database to share host.

Hope this helps.

|||If you have SQL Express instance installed on the remote server, just set the correct path for the mdf file like:

data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|PADatabase.mdf;User Instance=true

How to clean machine for SQL2005 Reporting Services RTM

hi all,

I am trying to get Reporting Services to install on a machine that previously had the September CTP install on it.

The SQL Server part of the install has been fine and all seems to be operational as expected but the Reporting Services fails to install with the following errors:

"An instance of the same name is already installed on this computer..."

This is thrown out of the ValidateInstanceName func in the MSI. I am telling it to use the Default Instance as there is only one SQL instance running (to my knowledge).

How do I clean up the machine so that it does not think another instance is present? I have tried MSIZAP and that has not helped. I have removed references from IIS, COM+, file system and registry.. but there must be some I am missing. Does anyone know what ValidateInstanceName is actually looking at/for?

Thanks
PaulIf in doubt..

Uninstall SQL Server 2005 and remove every reference to SQL (as far as possible) from the registry..

Fixed the issue.

How to check which port that SQL Server currently using?

Hi, I'm trying to connect to MS SQL server using PHP Pear DB package. I
have 2 SQL server running on different machine. 1 is using SQL Server
2000 Standard Edition and the other is SQL server from .NET SDK.
I can connect to the standard edition but not to SQL Server from .net
SDK. Did they use different port? if it is, what is default port for SQL
server from .net sdk? or how to check which port did my sql server is
using right now.
thanks
To view or even specify the port an instance is usin use Server Network
Utility -
http://msdn.microsoft.com/library/de...rver_2epl.asp.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"ricard" <ricard_notrealmail@.example.com> wrote in message
news:uv3x7rhlEHA.2340@.TK2MSFTNGP11.phx.gbl...
> Hi, I'm trying to connect to MS SQL server using PHP Pear DB package. I
> have 2 SQL server running on different machine. 1 is using SQL Server
> 2000 Standard Edition and the other is SQL server from .NET SDK.
> I can connect to the standard edition but not to SQL Server from .net
> SDK. Did they use different port? if it is, what is default port for SQL
> server from .net sdk? or how to check which port did my sql server is
> using right now.
> thanks