clear log: service

Showing posts with label service. Show all posts

Wednesday, March 28, 2012

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

Monday, March 26, 2012

How to connect to Remote SQL Server database using SQL Server 2005 Express

Hi,

I've an account with a hosting service provider online for SQL Server database. I've downloaded SQL Server 2005 Express from ASP.Net. How can I use it to connect to my SQL Server Database which is sitting on remote server? The hosting provider gave me following things to connect to the remote database.

Server Name
Database Name
User Name
Password

Regards,
A.K.R

Anyone?

|||I don't want to ask the obvious, but is there not a Read Me fileincluded with the download of SQL Express which would explain how toconnect?

Sorry I can't be more helpful, but I've only ever briefly looked at SQLExpress and decided to stick to MSDE since I could not see any benefitof using Express when MSDE is a cheap but far more powerful option thanSQL Express.

How to connect to Analysis Service Database through reporting service?

Hello,

In our project, we would like to use the same data source for our analysis service database cubes and for our reporting service reports.

I created the analysis service project first, deployed successfully. When trying to setting up the data source in the report model project, I selected the "create a data source based on another object", and then selected the "create a data source based on an analysis service project". However, there is no analysis service project to select, and no browse button to see where the reporting service is looking for analysis service project either.

I have tried creating a new analysis service project with data source views, cubes, dimensions and all the stuff, but still cannot see the analysis service project in the drop down box to be selected for my reporting model project data source.

As I am fairly new to the reporting service, I'm sure I'm missing something, but couldn't find much information in the help or on the web. Any suggestion would be much appreciated.

Thank you very much,

Annie

To create a model based on an Analysis Services cube, use Report Manager. First create a data source which points to the cube, then click "Generate Model" on the data source properties page. AS models can't be edited. Full details are in Books Online, under "Reporting Services How-To Topics".

If you just want to create a report which uses the same data source as your cube, you do not need a report model project. Instead create a report project, add a new report, and create a report data source which uses the same connection settings as the cube data source.

-Albert

|||Can you tell me how to open up the report manager?|||http://<your server name>/reports|||It doesn't work for http://localhsot/reportssql

How to connect to Analysis Service Database through reporting service?

Hello,

In our project, we would like to use the same data source for our analysis service database cubes and for our reporting service reports.

As I am fairly new to the reporting service, I'm sure I'm missing something, but couldn't find much information in the help or on the web. Any suggestion would be much appreciated.

Thank you very much,

Annie

-Albert

|||Can you tell me how to open up the report manager?|||http://<your server name>/reports|||It doesn't work for http://localhsot/reports

How to connect to a dedicated m/c

Hi,
Recently i installed SQL server 2000(EE)on my remote dedicated server( win
2003). I haven't installed ant Service packs. Now the problem is i am not
able to connect to the SQL server either thru Query Analyzer or thru the
application. I have disabled the firewall, still no use. Can anyone help
me.But thru remote desktop, i was able to connect to the server m/c by
putting the ip address .
regards lara
First thing to do is install SP3. SQL2000 RTM isn't supported on
Windows 2003.
David Portas
SQL Server MVP
|||Hi,
I've installed SP3
This is what i get when i run SELECT @.@.Version
"
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
"
I've disabled the firewall, enaled TCP/IP, set default port to 1433. and no
use till now
The same error is diplaying again and again 'Server Msg 17, Level 16, State
1
MS [ODBC Sql Server][DBNETLIB]SQL Server does not exist or access denied'
regards lara
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1119436842.190857.7930@.o13g2000cwo.googlegrou ps.com...
> First thing to do is install SP3. SQL2000 RTM isn't supported on
> Windows 2003.
> --
> David Portas
> SQL Server MVP
> --
>
|||Hi,
I've installed SP3
This is what i get when i run SELECT @.@.Version
"
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
"
I've disabled the firewall, enaled TCP/IP, set default port to 1433. and no
use till now
The same error is diplaying again and again 'Server Msg 17, Level 16, State
1
MS [ODBC Sql Server][DBNETLIB]SQL Server does not exist or access denied'
regards lara

How to connect to a dedicated m/c

Hi,
Recently i installed SQL server 2000(EE)on my remote dedicated server( win
2003). I haven't installed ant Service packs. Now the problem is i am not
able to connect to the SQL server either thru Query Analyzer or thru the
application. I have disabled the firewall, still no use. Can anyone help
me.But thru remote desktop, i was able to connect to the server m/c by
putting the ip address .
regards laraFirst thing to do is install SP3. SQL2000 RTM isn't supported on
Windows 2003.
David Portas
SQL Server MVP
--|||Hi,
I've installed SP3
This is what i get when i run SELECT @.@.Version
"
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
"
I've disabled the firewall, enaled TCP/IP, set default port to 1433. and no
use till now
The same error is diplaying again and again 'Server Msg 17, Level 16, State
1
MS [ODBC Sql Server][DBNETLIB]SQL Server does not exist or access de
nied'
regards lara
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1119436842.190857.7930@.o13g2000cwo.googlegroups.com...
> First thing to do is install SP3. SQL2000 RTM isn't supported on
> Windows 2003.
> --
> David Portas
> SQL Server MVP
> --
>|||Hi,
I've installed SP3
This is what i get when i run SELECT @.@.Version
"
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
"
I've disabled the firewall, enaled TCP/IP, set default port to 1433. and no
use till now
The same error is diplaying again and again 'Server Msg 17, Level 16, State
1
MS [ODBC Sql Server][DBNETLIB]SQL Server does not exist or access de
nied'
regards lara

Friday, March 23, 2012

How to connect Oracle Data Source for Reporting Service

I have the problem to connect Oracle data for my Report designer.

1st I used ODBC, it does not work, and my reference book "MS SQL server 2000 Reporting service step by step" tells me that I must select Oracle data provide instead of the generic ODBC.

I created a new data source and after I enter the userId/pswd and click "Test Connection" button, it is OK. But when I click "run" icon to try, it gives me the following error messages:

An error occurred while executing the query, ORA-00936:Missing expression

Additiona information:

ORA-00936:missing expression(system.Data.OracleClient)

My version of reporting service is 2005. The setting of "Connection Properties" as follows:

Data Source: Oracle (OracleClient) Server name: creonpra Log On to the database: UserId/Pswd= qmprodviewer/*********

I have very less knowledge about Oracle. I do not know Oracle Client software's coverage. I checked my program and only find Oracle 8i of "Net8 Assistant", "Net8 Config Assistant" and Oracle ODBC test" on my desktop PC.

Please help me to resolve the problem

Hi,

This looks like a query syntax error.

Did you use the query builder to create your Oracle query?

If you paste your query in a new database project can you execute it?

I would recommand to use the database project or Toad to debug the query, then when it is working, paste it back to your report dataset.

Philippe

|||

Yes definitely a syntax problem. Along with the other suggestion of trying it in the Oracle also try simple expressions first like...

select * from Table1

etc.

If your still stuck past the Syntax here and I can have a look at it since I connect primarily to Oracle DB's using the Oracle connection.

Craig

How to connect on shared memory?

I finally installed service pack 3, and I am told that I Can still access SQL server locally thru shared memory interfaces, if I turn off the Named Pipes and TCP/IP network libraries, thereby stopping UDP port 1434 from listening. This does, indeed stop port 1434 from listening but I can't use Enterprise manager to connect to the server anymore. How to I get it to connect on shared memory?Shared memory only works from the SQL Server itself. Not terribly useful for a networked application, but there it is. If you are trying to connect from a client machine, you will nee to turn on either TCP/IP or Named Pipes. Then make sure that the client machine is using the same protocol.

If you are attempting to access the SQL Server locally, you can use the Client Network Utility (in start menu) to reset your default protocol to Shared Memory (or TCP/IP, Named Pipes, etc.)

Hope this helps.|||Indeed it did. I found this out myself last night. Of course, remote clients can't connect. But, the purpose of this server is not for remote clients. I'm using it for IIS to connect to, so I can write ASP.Net scripts. There's a checkbox in the Client Network Utility titled "Enable Shared Memory Protocol" that allows you to do this, for future reference if anyone else has this problem.

Wednesday, March 21, 2012

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

Monday, March 19, 2012

How to configure SQL Server report server?

Hello, everyone
My company is planning to run SQL Server Service. We have SQL Server 2005. What softwares are needed to install on Report Server?
Thanks
ZYTHi ZYT

How detailed would you like your answer ?

This is a good link http://www.sqlservercentral.com/columnists/rpearl/installingandupgradingtosqlserver2005.asp

Installation setup itself does quite a good job notifying you of Prerequisites

Basically Latest service Packs for the server & IIS for Reports Server

GW

How to configure Reporting service for SMTP server located remotly.

Hi
I have one problem which i am not able to solve regardig the reporting
service SMTP services.
One of our client is using the SQL server 2000 along with Microsoft
Reporting Services. They need to configure SQL Reporting services for
sending reports through emails using subscription services. They don't
have any SMTP server located in their local network.
They are using external SMTP server for sending & receiving mails. How
to configure the RSReportServer.config file for the same? If we refer
documentation available in Reporting Service Books Online, it states
that we can configure using SMTPAuthenticate settings by using
"SENDUSERNAME" & "SENDPASSWORD".
ms-help://MS.RSBOL80.1033/rsadmin/htm/arp_configserver_v1_4bzl.htm
"SendUsing"
Specifies which method to use for sending messages.
To send report subscriptions through e-mail using a local POP3 server
hosted on a Windows 2003 server, you must set the value to 1.
1=sends a message using the local SMTP service pickup directory.
2=sends the message using the network SMTP service.
"SMTPAuthenticate "
Specifies an integer value that indicates the kind of authentication to
use when sending messages to an SMTP service over a TCP/IP connection.
0=no authentication.
1=basic authentication. Credentials are passed in clear text using
either sendusername and senduserpassword, or postusername and
postuserpassword fields.
2= NTML (NT LanMan) authentication. The security context of the current
process is used to authenticate the service.
If We Refer the MSDN online it states SMTPAuthenticate authorization is
not
supported.
http://msdn2.microsoftcom/ms157273.aspx
SendUsing
Specifies which method to use for sending messages. Valid values
include the following:
1=Sends a message from the local SMTP service pickup directory.
2=Sends the message from the network SMTP service.
SMTPAuthenticate
Specifies an integer value that indicates the kind of authentication to
use when sending messages to an SMTP service over a TCP/IP connection.
Valid values include the following:
0=No authentication.
1= (not supported).
2= NTLM (NT LanMan) authentication. The security context of the Report
Server Windows service is used to connect to the network SMTP server.
Please help me in matter to solve the problem. We are unable to send
mails using reporting service by using the settings stated in the
Reporting Service Books Online. Please solve the following problems.
1. Whether it is possible to use SMTP server outside the network or
not?
2. If yes what is the method of configuring SMTP services?
3. How can we send username & password to authenticate the user?
4. Send us sample RSReportServer.config if possible for the same.
Thanking youYou might want to start with checking if the firewall is allowing traffic
out of this server.
On your server, try using telnet to check for traffic.
Open command prompt.Try to type what I write after the (type)...
(Type) Telnet your-mail-server 25
reply 220 your-mail-server Microsoft ESMTP MAIL Service, Version:
5.0.2195.6713
ready at Mon, 24 Oct 2005 15:43:27 +0200
(Type) HELO your-domain
250 your-mail-server Hello [10.61.120.21]
(Type) MAIL FROM: you@.youradress.com
250 2.1.0 you@.youradress.com... Sender OK
(Type) RCPT TO: someone.else@.youradress.com
250 2.1.5 someone.else@.youraddress.com
(Type) DATA
354 Start mail input; end with <CRLF>.<CRLF>
(Type) THis is my message!
.
250 2.6.0 your-mail-server> Queued mail for delivery
Type quit to end the telnet session.
If you can't send an e-mail by telnet, your reporting services server
probably can't either.
Kaisa M. Lindahl Lervik
"msinghindia" <msinghindia@.gmail.com> wrote in message
news:1140695688.842888.246030@.f14g2000cwb.googlegroups.com...
> Hi
> I have one problem which i am not able to solve regardig the reporting
> service SMTP services.
> One of our client is using the SQL server 2000 along with Microsoft
> Reporting Services. They need to configure SQL Reporting services for
> sending reports through emails using subscription services. They don't
> have any SMTP server located in their local network.
> They are using external SMTP server for sending & receiving mails. How
> to configure the RSReportServer.config file for the same? If we refer
> documentation available in Reporting Service Books Online, it states
> that we can configure using SMTPAuthenticate settings by using
> "SENDUSERNAME" & "SENDPASSWORD".
> ms-help://MS.RSBOL80.1033/rsadmin/htm/arp_configserver_v1_4bzl.htm
> "SendUsing"
> Specifies which method to use for sending messages.
> To send report subscriptions through e-mail using a local POP3 server
> hosted on a Windows 2003 server, you must set the value to 1.
> 1=sends a message using the local SMTP service pickup directory.
> 2=sends the message using the network SMTP service.
> "SMTPAuthenticate "
> Specifies an integer value that indicates the kind of authentication to
> use when sending messages to an SMTP service over a TCP/IP connection.
> 0=no authentication.
> 1=basic authentication. Credentials are passed in clear text using
> either sendusername and senduserpassword, or postusername and
> postuserpassword fields.
> 2= NTML (NT LanMan) authentication. The security context of the current
> process is used to authenticate the service.
>
> If We Refer the MSDN online it states SMTPAuthenticate authorization is
> not
> supported.
> http://msdn2.microsoftcom/ms157273.aspx
> SendUsing
> Specifies which method to use for sending messages. Valid values
> include the following:
> 1=Sends a message from the local SMTP service pickup directory.
> 2=Sends the message from the network SMTP service.
> SMTPAuthenticate
> Specifies an integer value that indicates the kind of authentication to
> use when sending messages to an SMTP service over a TCP/IP connection.
> Valid values include the following:
> 0=No authentication.
> 1= (not supported).
> 2= NTLM (NT LanMan) authentication. The security context of the Report
> Server Windows service is used to connect to the network SMTP server.
> Please help me in matter to solve the problem. We are unable to send
> mails using reporting service by using the settings stated in the
> Reporting Service Books Online. Please solve the following problems.
> 1. Whether it is possible to use SMTP server outside the network or
> not?
> 2. If yes what is the method of configuring SMTP services?
> 3. How can we send username & password to authenticate the user?
> 4. Send us sample RSReportServer.config if possible for the same.
> Thanking you
>|||Thnks for early reply.
I followed your steps. When type RCPT TO: mail@.domain.com gives the
following error.
"Relaying Denied...proper authentication required."
Please ! It will be great if you could let me know the reasons behind
the error.
Thanks in Advance
Manjeet|||Relaying is often used for spamming - someone sends out loads of email from
a mail server they don't own. So a lot of email providers will configure
their server to not allow relaying.
You might want to check with the owners of your smtp server what settings
you should use, and how to authenticate proberly remotely.
Kaisa M. Lindahl Lervik
"msinghindia" <msinghindia@.gmail.com> wrote in message
news:1140704270.023492.174060@.j33g2000cwa.googlegroups.com...
> Thnks for early reply.
> I followed your steps. When type RCPT TO: mail@.domain.com gives the
> following error.
> "Relaying Denied...proper authentication required."
> Please ! It will be great if you could let me know the reasons behind
> the error.
> Thanks in Advance
> Manjeet
>|||I have checked with the owners of the server. They can not enable
relaying since it will create problem of SPAM mails as server is live
on internet. So i can not send mails without authorization. So i need
to send username & password to SMTP server when Reporting Server send
mails? But how to do that '
If i refer documents of reporting service for rsconfig file it says
using "sendusername" and "senduserpassword". But it is not working.
When i refer MSDN online it says these is not Supported.
Please any body know how to authorize SQL Reporting Service for sending
mails'
Thanks in advance.

How to configure Report Server in SQL Server 2005?

Hello, everyone:

I hope my question is clear.

I have SQl Server 2005 installed in local computer. I am planning to create report by Report Service so a report server is needed by which I can deploy report from my local computer to that server. How to intall the report server in another computer/

Thanks

ZYTZYT,
Your question is clear, but it doesn't look like you've done any research on the subject. There are plenty of KB articles and technical support documents regarding Reporting Services on the Microsoft website and numerous books exist on the subject.
If you encounter a specific problem when trying to implement Reporting Services having done the necessary research, people are more likely to help you, but they won't generally do all your work for you!

Lempster :S

Monday, March 12, 2012

how to conditionally get the data

Hi,

In Reporting Service, how to conditionally get the data? Let's say, I don't want the line

when the Status field is "inactive" and Eff_Date<"1/1/2006"

I conditionally hided the Visibility of this line. But when i tried to get the subtotal, this line's Quantity info still was included into the subtotal.

I tried to use the Filter box of the dataset to do it, but don't know how.

Can anybody please help me out?

Thanks a lot.

What kind of datasource are you using?

Friday, March 9, 2012

How to compress text before storing in DB?

I was planning on running a service where thousands of text messages are stored. Obviously I'd want to make the most of my DB space, and was wondering if there's some way for SQL to compress text down to the smallest space possible. If not, is there some kind of ASP component I could download to do this? Failing that, I could always write a simple one, which takes the most common letter combinations, and shortens them down to a single character.

Any advice?Space is cheap. Use it. Otherwise, your data will be dependent on whatever compression algorithm you use, and everyone will have to consult with you to read the data. Of course, if you're a consultant focused on billable hours, writing some hair-brained compression may be just what you want.

Either don't worry about space (have you done the math on what this gives you vs. buying the adequate space?), or store your text outside the db on a compressed drive.|||I don't have to consult with anyone :) It's a one-man project, just something I'm building for consumers, there's no income involved. And space is cheap, yes, if I'm hosting this solution myself. But I'm not. And SQL Server 2000 DB storage does not come cheaply at a good, reliable host.|||Anyone else? Anyone?|||Maybe this will get you to drink the water: Video on Hotmail Architecture (http://channel9.msdn.com/ShowPost.aspx?PostID=39016)

Friday, February 24, 2012

How to combine Multiple Dataset result in each row of the report

Hi,

I need to produce a report in MS SQL Server Reporting Service 2005 which has some date fields & need to pass these date fields to find out the no_of_User on that date from another database. For example

Itemid

Availabilty_Start_Dt

Availabilty_End_Dt

User_On_St_DT (this info is in another DB & need to pass Availabilty_Start_Dt )

User_On_ED_DT (this info is in another DB & need to pass Availabilty_Start_Dt )

I am facing two problem here. Since hereis two different dataset needed how can I combine the dataset result to produce each row of the report.

REally appreciate if anyone can show me some light on it.

Regards,

write a strored procedure in the backend and try to write the two queries and combine the results and store in a temp table.

use the stored procedure in the reporting services. Backend is the best solution for it.

Wednesday, March 28, 2012

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

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

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

Monday, March 26, 2012

How to connect to Remote SQL Server database using SQL Server 2005 Express

How to connect to Analysis Service Database through reporting service?

How to connect to Analysis Service Database through reporting service?

How to connect to a dedicated m/c

How to connect to a dedicated m/c

Friday, March 23, 2012

How to connect Oracle Data Source for Reporting Service

How to connect on shared memory?

Wednesday, March 21, 2012

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

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

Monday, March 19, 2012

How to configure SQL Server report server?

How to configure Reporting service for SMTP server located remotly.

How to configure Report Server in SQL Server 2005?

Monday, March 12, 2012

how to conditionally get the data

Friday, March 9, 2012

How to compress text before storing in DB?

Friday, February 24, 2012

How to combine Multiple Dataset result in each row of the report

clear log

Blog Archive

About Me