Reporting Services 2005 & IE7 Beta

When trying to print an RS2005 report, I keep getting the error "Unable to
load client print control". This is because the RSClientPrint ActiveX
control is not loaded. I have noticed that in IE7 Beta is not automatically
prompting to download the control. Has anyone been successful in running
this under IE7? I am using 7.0.5112.0, Beta 1.
* "Enable download for the ActiveX client print control" is enabled on the
server.
* Report Server added to the Trusted Sites list
* Download Signed ActiveX Controls = Enable
* Script ActiveX Controls Marked Safe for Scripting = Enable
* Automatic Prompting for ActiveX Controls = Enable
Works fine under IE6.
Thanks,
-sYou may want to insure that it is enabled.
Tools->Internet Options->Programs->Manage Add-ons
If RSCleintPrint Class is enabled, you may want to delete it and allow
it to be reinstalled.
Hope you get it to working,
Lonsql

Reporting Services 2005 - Problems displaying a report via a ReportViewer control.

I have a report that displays fine in VS 2005 (in the Preview tab), and if I hit it via a URL in IE as a deployed report. However, when I embed it in a ReportViewer control for display on a web site, I get no data back for the report. I am using an Oracle database for the data source. None of the the logs in reporting services show anything wrong, there are no events in the event viewer to indicate any problems, Oracle logs also show no problems and no errors are returned to the page when the "View Report" button is clicked.

Anyone out there have a clue? I certainly don't.

Mike

The web site is executing the report viewer control with a certain (ASP.NET) user context. Most likely this account does not have any permissions to access the installation of the Oracle client software (or the Oracle client software is not installed at all on the web server).

Check this KB article for more details how to configure directory security: http://support.microsoft.com/?kbid=870668

-- Robert

|||

I thought the same thing at first, but permissions checked out fine. I found out that the problem is a rather esoteric interaction of Div and Table HTML element display characteristics during report generation (at least that's what the MSDN article says at http://msdn2.microsoft.com/en-us/library/ms252090.aspx).

The gist of it is that when you have the ReportViewer control properties set to render Asynchronously and have the height set to a '%' value (I was using 100%), the calculated height passed in the HTML is set to '0' so no report displays. You have the choice of using a fixed height and Asynchronous rendering or a percentage height and synchronous rendering.

Mike

|||

Thanks for posting your findings!

-- Robert

sql

Reporting Services : Exporting Report To Excel (SubReport)

Hi All,

Issue : While Exporting Report to Excel (Report contains SubReport)

Advance Thanks

In Reporint Services, I am using Table control to display the data.

In that control footer section i added one subreport that accessing the value from the Footer Section of the table(like Total ..) Report is generating.

While exporing that report, it is giving exception like : "Sub Report in Table Cell could not be shown."

Any idea/ suggestion to resolve this issue.

I believe export to excel does not support this.

Reporting Services - Local Report - Memory & Session Usage

Hello there, I'm currently experiencing some issues with Reporting
Services' ReportViewer Control. When running the control without a Reporting
Server in 'Local' processing mode we cannot serve very many simultaneous
requests. Worse, if a single user opens several reports one after the other
they can easily get an OutOfMemory exception from the w3wp.exe (Attempting to
serialize something?). I've debugged the page and supporting code and looked
at some output from CLRProfiler with no obvious leaks. I have noticed
something though, after each report is loaded, another ReportHierarchy object
is stored in the user's Session server side. Is the report control storing
the data in session?
-- page code --
...AutoEventWireup="true"....
...
<rsweb:ReportViewer
Width="100%"
runat="server"
AsyncRendering="true"
ShowPrintButton="true"
ShowRefreshButton="false"
ID="<blahblah>"
ShowExportControls="true"
ExportContentDisposition="AlwaysInline">
</rsweb:ReportViewer>
-- page behind code --
reportControl.Reset();
reportControl.ShowPrintButton = true;
reportControl.ShowRefreshButton = false;
reportControl.LocalReport.LoadReportDefinition(<stream>);
reportControl.LocalReport.DisplayName = "My Report";
reportControl.LocalReport.DataSources.Clear();
reportControl.LocalReport.DataSources.Add(new
ReportDataSource(ReportDefinitionGenerator.DYNA_DATASET_NAME,
<DataTable>.DefaultView));
reportControl.SizeToReportContent = true;
Cheers
AntonyStill waiting? Any advice? We're looking at changing the design and
moving away from running reports in 'Local' Processing mode but that would
require making a staging area for the data that the Reporting Services Server
could also access.
;(
"Antony" wrote:
> Hello there, I'm currently experiencing some issues with Reporting
> Services' ReportViewer Control. When running the control without a Reporting
> Server in 'Local' processing mode we cannot serve very many simultaneous
> requests. Worse, if a single user opens several reports one after the other
> they can easily get an OutOfMemory exception from the w3wp.exe (Attempting to
> serialize something?). I've debugged the page and supporting code and looked
> at some output from CLRProfiler with no obvious leaks. I have noticed
> something though, after each report is loaded, another ReportHierarchy object
> is stored in the user's Session server side. Is the report control storing
> the data in session?
> -- page code --
> ...AutoEventWireup="true"....
> ...
> <rsweb:ReportViewer
> Width="100%"
> runat="server"
> AsyncRendering="true"
> ShowPrintButton="true"
> ShowRefreshButton="false"
> ID="<blahblah>"
> ShowExportControls="true"
> ExportContentDisposition="AlwaysInline">
> </rsweb:ReportViewer>
> -- page behind code --
> reportControl.Reset();
> reportControl.ShowPrintButton = true;
> reportControl.ShowRefreshButton = false;
> reportControl.LocalReport.LoadReportDefinition(<stream>);
> reportControl.LocalReport.DisplayName = "My Report";
> reportControl.LocalReport.DataSources.Clear();
> reportControl.LocalReport.DataSources.Add(new
> ReportDataSource(ReportDefinitionGenerator.DYNA_DATASET_NAME,
> <DataTable>.DefaultView));
> reportControl.SizeToReportContent = true;
>
> Cheers
> Antony
>|||I looked at doing local reports and decided against it due to a variety of
reasons. One, designing and testing is a lot harder. Subreports are a pain.
Lots more mucking around.
The local report mode is not intended to be a replacement for the server
based product. If it was, then why buy the server (seeing as how the control
comes with VS and does not require any licensing). So, it does not surprise
me that it has limitations under load.
There is a major shift in how you design. You are used to creating the
tablesets, responding to events etc. With the server based product you
design the dataset and let RS get the data. You do not respond to events.
Yes, you can write a data processing extension if you want but it is
non-trivial and I would only go that way if you absolutely must. Otherwise,
in the report definition define the datasets by putting in the SQL or
referring to a stored procedure.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Antony" <alovric@.trialstat.com(do not spam)> wrote in message
news:83063161-C816-4E81-AB16-3CE47C4277C5@.microsoft.com...
> Still waiting? Any advice? We're looking at changing the design and
> moving away from running reports in 'Local' Processing mode but that would
> require making a staging area for the data that the Reporting Services
> Server
> could also access.
> ;(
>
> "Antony" wrote:
>> Hello there, I'm currently experiencing some issues with Reporting
>> Services' ReportViewer Control. When running the control without a
>> Reporting
>> Server in 'Local' processing mode we cannot serve very many simultaneous
>> requests. Worse, if a single user opens several reports one after the
>> other
>> they can easily get an OutOfMemory exception from the w3wp.exe
>> (Attempting to
>> serialize something?). I've debugged the page and supporting code and
>> looked
>> at some output from CLRProfiler with no obvious leaks. I have noticed
>> something though, after each report is loaded, another ReportHierarchy
>> object
>> is stored in the user's Session server side. Is the report control
>> storing
>> the data in session?
>> -- page code --
>> ...AutoEventWireup="true"....
>> ...
>> <rsweb:ReportViewer
>> Width="100%"
>> runat="server"
>> AsyncRendering="true"
>> ShowPrintButton="true"
>> ShowRefreshButton="false"
>> ID="<blahblah>"
>> ShowExportControls="true"
>> ExportContentDisposition="AlwaysInline">
>> </rsweb:ReportViewer>
>> -- page behind code --
>> reportControl.Reset();
>> reportControl.ShowPrintButton = true;
>> reportControl.ShowRefreshButton = false;
>> reportControl.LocalReport.LoadReportDefinition(<stream>);
>> reportControl.LocalReport.DisplayName = "My Report";
>> reportControl.LocalReport.DataSources.Clear();
>> reportControl.LocalReport.DataSources.Add(new
>> ReportDataSource(ReportDefinitionGenerator.DYNA_DATASET_NAME,
>> <DataTable>.DefaultView));
>> reportControl.SizeToReportContent = true;
>>
>> Cheers
>> Antony
>>|||Thanks Bruce, sorry, I just noticed that I didn't reply to you sooner. Do
you know if the persistance of the ReportHierarchy obj in session is
intentional?
Cheers
Antony
--
;)
"Bruce L-C [MVP]" wrote:
> I looked at doing local reports and decided against it due to a variety of
> reasons. One, designing and testing is a lot harder. Subreports are a pain.
> Lots more mucking around.
> The local report mode is not intended to be a replacement for the server
> based product. If it was, then why buy the server (seeing as how the control
> comes with VS and does not require any licensing). So, it does not surprise
> me that it has limitations under load.
> There is a major shift in how you design. You are used to creating the
> tablesets, responding to events etc. With the server based product you
> design the dataset and let RS get the data. You do not respond to events.
> Yes, you can write a data processing extension if you want but it is
> non-trivial and I would only go that way if you absolutely must. Otherwise,
> in the report definition define the datasets by putting in the SQL or
> referring to a stored procedure.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Antony" <alovric@.trialstat.com(do not spam)> wrote in message
> news:83063161-C816-4E81-AB16-3CE47C4277C5@.microsoft.com...
> > Still waiting? Any advice? We're looking at changing the design and
> > moving away from running reports in 'Local' Processing mode but that would
> > require making a staging area for the data that the Reporting Services
> > Server
> > could also access.
> >
> > ;(
> >
> >
> > "Antony" wrote:
> >
> >> Hello there, I'm currently experiencing some issues with Reporting
> >> Services' ReportViewer Control. When running the control without a
> >> Reporting
> >> Server in 'Local' processing mode we cannot serve very many simultaneous
> >> requests. Worse, if a single user opens several reports one after the
> >> other
> >> they can easily get an OutOfMemory exception from the w3wp.exe
> >> (Attempting to
> >> serialize something?). I've debugged the page and supporting code and
> >> looked
> >> at some output from CLRProfiler with no obvious leaks. I have noticed
> >> something though, after each report is loaded, another ReportHierarchy
> >> object
> >> is stored in the user's Session server side. Is the report control
> >> storing
> >> the data in session?
> >>
> >> -- page code --
> >> ...AutoEventWireup="true"....
> >> ...
> >> <rsweb:ReportViewer
> >> Width="100%"
> >> runat="server"
> >> AsyncRendering="true"
> >> ShowPrintButton="true"
> >> ShowRefreshButton="false"
> >> ID="<blahblah>"
> >> ShowExportControls="true"
> >> ExportContentDisposition="AlwaysInline">
> >> </rsweb:ReportViewer>
> >>
> >> -- page behind code --
> >> reportControl.Reset();
> >> reportControl.ShowPrintButton = true;
> >> reportControl.ShowRefreshButton = false;
> >> reportControl.LocalReport.LoadReportDefinition(<stream>);
> >> reportControl.LocalReport.DisplayName = "My Report";
> >> reportControl.LocalReport.DataSources.Clear();
> >> reportControl.LocalReport.DataSources.Add(new
> >> ReportDataSource(ReportDefinitionGenerator.DYNA_DATASET_NAME,
> >> <DataTable>.DefaultView));
> >> reportControl.SizeToReportContent = true;
> >>
> >>
> >> Cheers
> >> Antony
> >>
> >>
>
>|||Were you able to resolve your performance issues when using the ReportViewer
control in Local Mode? If so, what steps did you take?
We are considering doing the same but are concerned about performance
degradation as well.
Thanks for any information you can provide.
"Antony" wrote:
> Thanks Bruce, sorry, I just noticed that I didn't reply to you sooner. Do
> you know if the persistance of the ReportHierarchy obj in session is
> intentional?
> Cheers
> Antony
> --
> ;)
>
> "Bruce L-C [MVP]" wrote:
> > I looked at doing local reports and decided against it due to a variety of
> > reasons. One, designing and testing is a lot harder. Subreports are a pain.
> > Lots more mucking around.
> >
> > The local report mode is not intended to be a replacement for the server
> > based product. If it was, then why buy the server (seeing as how the control
> > comes with VS and does not require any licensing). So, it does not surprise
> > me that it has limitations under load.
> >
> > There is a major shift in how you design. You are used to creating the
> > tablesets, responding to events etc. With the server based product you
> > design the dataset and let RS get the data. You do not respond to events.
> > Yes, you can write a data processing extension if you want but it is
> > non-trivial and I would only go that way if you absolutely must. Otherwise,
> > in the report definition define the datasets by putting in the SQL or
> > referring to a stored procedure.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Antony" <alovric@.trialstat.com(do not spam)> wrote in message
> > news:83063161-C816-4E81-AB16-3CE47C4277C5@.microsoft.com...
> > > Still waiting? Any advice? We're looking at changing the design and
> > > moving away from running reports in 'Local' Processing mode but that would
> > > require making a staging area for the data that the Reporting Services
> > > Server
> > > could also access.
> > >
> > > ;(
> > >
> > >
> > > "Antony" wrote:
> > >
> > >> Hello there, I'm currently experiencing some issues with Reporting
> > >> Services' ReportViewer Control. When running the control without a
> > >> Reporting
> > >> Server in 'Local' processing mode we cannot serve very many simultaneous
> > >> requests. Worse, if a single user opens several reports one after the
> > >> other
> > >> they can easily get an OutOfMemory exception from the w3wp.exe
> > >> (Attempting to
> > >> serialize something?). I've debugged the page and supporting code and
> > >> looked
> > >> at some output from CLRProfiler with no obvious leaks. I have noticed
> > >> something though, after each report is loaded, another ReportHierarchy
> > >> object
> > >> is stored in the user's Session server side. Is the report control
> > >> storing
> > >> the data in session?
> > >>
> > >> -- page code --
> > >> ...AutoEventWireup="true"....
> > >> ...
> > >> <rsweb:ReportViewer
> > >> Width="100%"
> > >> runat="server"
> > >> AsyncRendering="true"
> > >> ShowPrintButton="true"
> > >> ShowRefreshButton="false"
> > >> ID="<blahblah>"
> > >> ShowExportControls="true"
> > >> ExportContentDisposition="AlwaysInline">
> > >> </rsweb:ReportViewer>
> > >>
> > >> -- page behind code --
> > >> reportControl.Reset();
> > >> reportControl.ShowPrintButton = true;
> > >> reportControl.ShowRefreshButton = false;
> > >> reportControl.LocalReport.LoadReportDefinition(<stream>);
> > >> reportControl.LocalReport.DisplayName = "My Report";
> > >> reportControl.LocalReport.DataSources.Clear();
> > >> reportControl.LocalReport.DataSources.Add(new
> > >> ReportDataSource(ReportDefinitionGenerator.DYNA_DATASET_NAME,
> > >> <DataTable>.DefaultView));
> > >> reportControl.SizeToReportContent = true;
> > >>
> > >>
> > >> Cheers
> > >> Antony
> > >>
> > >>
> >
> >
> >

Reporting Service Table control - question...is this possible?!?

Hi, on my local SSRS (RDLC), I have a table which presents several

items, however these are not sequential data from a table on my DB, are

fields of only one row of a table on my DB. More specificly, I have a

table with the fields issue1, description1, issue2,

description2...until 6! I want to present those fields six times (the

same times as they appear on the DB), however, I only want them to

appear is the issuex (which is an integer) is greater than 0. So to

guarantee that each field only appears one time, I do this:

=First(Fields!issue1.Value)

to each table line

And

what I want to do on each line is IIF(Fields!issue1.Value >

0,True,False) to make that line visible or not, however, if I apply

this to a line it automatically applies it to the complete table, and

if only one of this conditions returns false the complete table becomes

invisible.

Is there anyway to make this work dynamically?!?Thanks a lot!

The first mistake in your hidden expression is that your true and false results are exchanged. As per your first sentence, you want to show the row when issue>0 which means hidden should be false. so your hidden expression for table row should like this: IIf(Fields!issue1.Value>0, false, true)

To achieve the result you want, create 6 table detail rows and control the visibility of these rows based on the corresponding issue number. For example, first row will check for issue1 > 0, second row will check for issue 2 >0 etc until 6th row..

Shyam

Reporting Service Performance

I have developed a Windows Forms Control that renders ReportingService reports as a metafile, This way the reports can be shown on as 'Crystal Reports' does in the wysiwyg way. But when the reports contain some hundered pages (and that happens often) the rendering of one page takes up to 3 seconds. The reason for this is not the SQL statement (it is a simple listing of 15000 records in one table). Is there a way to speed this up without using caches or snapshots? The Controls main feature must be that it can easily show and print reports.
The Control is based on the following code: http://blogs.msdn.com/bryanke/articles/71491.aspxThe image rendering extension was not really designed to be used this way
and is known to have issues with large reports. Bryan's code is a interim
approach until we have the supported set of report controls available in VS
Whidbey.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dasirr" <Dasirr@.discussions.microsoft.com> wrote in message
news:0BE027EA-51C5-4B4E-BC32-2CC51EE01E0C@.microsoft.com...
>I have developed a Windows Forms Control that renders ReportingService
>reports as a metafile, This way the reports can be shown on as 'Crystal
>Reports' does in the wysiwyg way. But when the reports contain some
>hundered pages (and that happens often) the rendering of one page takes up
>to 3 seconds. The reason for this is not the SQL statement (it is a simple
>listing of 15000 records in one table). Is there a way to speed this up
>without using caches or snapshots? The Controls main feature must be that
>it can easily show and print reports.
> The Control is based on the following code:
> http://blogs.msdn.com/bryanke/articles/71491.aspx

Reporting Service and Source Control

Hi

We have encountered a problem using source control with reporting services. Im writing this post to find out whether we are doing something wrong, or reporting service just don't store everything in source control.

My problem is as follows.

My collegue creates a report with a dataset and this report contains several parameters. He tests this, deploys it, and checks it into the source control through Visual Studio.

The following day I get responsibility to alter something in this report. I checks out everything from source control, starts Visual Studio. But... A few important things are missing. The credentials for the dataset for once (this is a minor issue) since these might not should be stored in source control anyways. What is worse is that all the parameter settings are missing. What was entered was a query to a stored procedure where e.g 5 parameters in the report was mapped to parameters in the stored procedure. Now the query has been changed to text type, and the parameter mapping is missing.

This does make it impossible to cooperate on creating reports. If I now make a change in the parameter configuration, my collegue won't receive this when synchronizing source control, and the risk of deploying something incorrect is too high.

Can anyone help enlighten us. Are we doing something wrong? Is there some manual step that needs to be done to ensure that everything is stored in source control? Or is it just something we have to live with, not being able to trust source control when doing Reporting Services?

Best regards

/Anders

After a little more thourough investigation I have found out what have caused this.

The credentials in the dataset (.rds) is not stored in source control. As i mentioned above this is actually ok, since credentials should not be stored in clear text in source control.

But, if you "forget" to enter the credentials before opening a report (.rdl), this report will "reset" the settings for the strored procedure, and changing the dataset to text type instead of stored procedure.

The current solution for us, is to close the report without saving it, enter correct credentials, and then reopen the report fresh from source control. Then all is as it should be.

I will not consider this to be an actual bug, but i definitely find it to be a inappropriate behaviour. In my world it would be nice for reporting services just to state that the dataset cant be loaded - but it should definitely not alter my report just because of that.

But now the post is here - if anyways encounters the same "problem". I willl expect this to happen only the first time a new collegue should work on a report solution, since after this he will have correct credentials entered, and thus not encounter this strange behaviour.

Best regards

/Anders

Reporting service access control

Were working on a classic asp app and are trying to implement some
reports through reporting service. I have a few questions.
First the application were working on will have multiple instances, so
one a single server there can be upto 15 identical apps connecting to
different databases, is there a way to have reporting service limit
what data source reporting service can access depending on what IIS
website/application pool the browsers are accessing?
Badgers.servername.com/reportserver should open the reports with the
badgers db
Squirrels.servername.com/reportserver db=squirrels
Servername.com:54333 db=badgers
Servername.com:54334 db=squirrelsNot automatically but you can pass a parameter that is used by your report
to use the appropriate datasource.
In RS 2005 you can use an expression for your data source. Which if you
write your reports to expect a parameter (say DBParam) then you can do
exactly what you want. From Books OnLine:
>>>>>>
Data Source Expressions
You can put an expression into a connection string to allow users to select
the data source at run time. For example, suppose a multinational firm has
data servers in several countries. With an expression-based connection
string, a user who is running a sales report can select a data source for a
particular country before running the report.
The following example illustrates the use of a data source expression in a
SQL Server connection string. The example assumes you have created a report
parameter named ServerName:
Copy Code
="data source=" & Parameters!ServerName.Value & ";initial
catalog=AdventureWorks
Data source expressions are processed at run time or when a report is
previewed. The expression must be written in Visual Basic. Use the following
guidelines when defining a data source expression:
a.. Design the report using a static connection string. A static
connection string refers to a connection string that is not set through an
expression (for example, when you follow the steps for creating a
report-specific or shared data source, you are defining a static connection
string). Using a static connection string allows you to connect to the data
source in Report Designer so that you can get the query results you need to
create the report.
b.. When defining the data source connection, do not use a shared data
source. You cannot use a data source expression in a shared data source. You
must define a report-specific data source for the report.
c.. Specify credentials separately from the connection string. You can use
stored credentials, prompted credentials, or integrated security.
d.. Add a report parameter to specify a data source. For parameter values,
you can either provide a static list of available values (in this case, the
available values should be data sources you can use with the report) or
define a query that retrieves a list of data sources at run time.
e.. Be sure that the list of data sources shares the same database schema.
All report design begins with schema information. If there is a mismatch
between the schema used to define the report and the actual schema used by
the report at run time, the report might not run.
f.. Before publishing the report, replace the static connection string
with an expression. Wait until you are finished designing the report before
you replace the static connection string with an expression. Once you use an
expression, you cannot execute the query in Report Designer. Furthermore,
the field list in the Datasets window and the Parameters list will not
update automatically.
>>>>>>>
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<lance.sanchez@.gmail.com> wrote in message
news:1190052200.309137.245860@.d55g2000hsg.googlegroups.com...
> Were working on a classic asp app and are trying to implement some
> reports through reporting service. I have a few questions.
> First the application were working on will have multiple instances, so
> one a single server there can be upto 15 identical apps connecting to
> different databases, is there a way to have reporting service limit
> what data source reporting service can access depending on what IIS
> website/application pool the browsers are accessing?
> Badgers.servername.com/reportserver should open the reports with the
> badgers db
> Squirrels.servername.com/reportserver db=squirrels
> Servername.com:54333 db=badgers
> Servername.com:54334 db=squirrels
>
begin 666 copycode.gif
M1TE&.#EA#P`/`.9F`).BM[+"V*[$\(&NY:Z_U'.AWER,VIBKQBE4JIFLQ_S]
M_LO/U)*P[8JN_,73\JFXSF2%R=;>[/;Y_>OO]BM7L6Z<VB)&CZ:]["!!AJ"Y
M[VB7U9RPSM+;\9>FNZ.RR"-(EOGZ_")%CIRKP;+)\*[0_Z^^U#5EQ2E4K*FY
MSX*?V,_9YM+6W9JMRFZ7YV".Y\S7[-'ZINOS)"JX+K:_^KO^R5,FR=0HIJN
MRI:FN^;J\^#F\25-G25*F+_+W=+>\,#*X,+.Y/7V^[K%U/O]_B-'DG^G\_#T
M^\?2X7.2T4=NNI_%^B%#B=OD]_?X^Z_#[?#R^)>IQ*K![XZX\"%#BIRUYZ*Q
MQV:"I?#S^*.RQYJNS*O"[]/>]55YP2I7LW*:ZH6GZR=0I%MRC[[.\#5)8U&#
MT?_______P``````````````````````````````````````````````````
M`````````````````````````````````````````````````"'Y! $``&8`
M+ `````/``\```>?@.&:"@.X2%AH>"`0$$! \>*X@.!99-E558+AR64"CA"89B%
M*&4S)#X``EI1&0P,+X)8DR!/.0*495\F0&8B94I2`P47MEXC%#\="D$3.A%4
M90T-'"Y=)V `3< 5&C*41DP.63L`5S J1STI944M!F1D-SP`8_/S2&5#-%MB
F3@.E$AA!EVKDC<R"$(2X2-L1@.D> `E"6&DB! 8*/&!PM3, 0"`#L`
`
end|||Thank you, is there a way to tie it into the IIS session so someone
would generate an error if they tried to change the parameter to
something else?
On Sep 17, 11:29 am, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> Not automatically but you can pass a parameter that is used by your report
> to use the appropriate datasource.
> In RS 2005 you can use an expression for your data source. Which if you
> write your reports to expect a parameter (say DBParam) then you can do
> exactly what you want. From Books OnLine:
> Data Source Expressions
> You can put an expression into a connection string to allow users to select
> the data source at run time. For example, suppose a multinational firm has
> data servers in several countries. With an expression-based connection
> string, a user who is running a sales report can select a data source for a
> particular country before running the report.
> The following example illustrates the use of a data source expression in a
> SQL Server connection string. The example assumes you have created a report
> parameter named ServerName:
> Copy Code
> ="data source=" & Parameters!ServerName.Value & ";initial
> catalog=AdventureWorks
> Data source expressions are processed at run time or when a report is
> previewed. The expression must be written in Visual Basic. Use the following
> guidelines when defining a data source expression:
> a.. Design the report using a static connection string. A static
> connection string refers to a connection string that is not set through an
> expression (for example, when you follow the steps for creating a
> report-specific or shared data source, you are defining a static connection
> string). Using a static connection string allows you to connect to the data
> source in Report Designer so that you can get the query results you need to
> create the report.
> b.. When defining the data source connection, do not use a shared data
> source. You cannot use a data source expression in a shared data source. You
> must define a report-specific data source for the report.
> c.. Specify credentials separately from the connection string. You can use
> stored credentials, prompted credentials, or integrated security.
> d.. Add a report parameter to specify a data source. For parameter values,
> you can either provide a static list of available values (in this case, the
> available values should be data sources you can use with the report) or
> define a query that retrieves a list of data sources at run time.
> e.. Be sure that the list of data sources shares the same database schema.
> All report design begins with schema information. If there is a mismatch
> between the schema used to define the report and the actual schema used by
> the report at run time, the report might not run.
> f.. Before publishing the report, replace the static connection string
> with an expression. Wait until you are finished designing the report before
> you replace the static connection string with an expression. Once you use an
> expression, you cannot execute the query in Report Designer. Furthermore,
> the field list in the Datasets window and the Parameters list will not
> update automatically.
> >>>>>>>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <lance.sanc...@.gmail.com> wrote in message
> news:1190052200.309137.245860@.d55g2000hsg.googlegroups.com...
>
> > Were working on a classic asp app and are trying to implement some
> > reports through reporting service. I have a few questions.
> > First the application were working on will have multiple instances, so
> > one a single server there can be upto 15 identical apps connecting to
> > different databases, is there a way to have reporting service limit
> > what data source reporting service can access depending on what IIS
> > website/application pool the browsers are accessing?
> > Badgers.servername.com/reportserver should open the reports with the
> > badgers db
> > Squirrels.servername.com/reportserver db=squirrels
> > Servername.com:54333 db=badgers
> > Servername.com:54334 db=squirrels
> begin 666 copycode.gif
> M1TE&.#EA#P`/`.9F`).BM[+"V*[$\(&NY:Z_U'.AWER,VIBKQBE4JIFLQ_S]
> M_LO/U)*P[8JN_,73\JFXSF2%R=;>[/;Y_>OO]BM7L6Z<VB)&CZ:]["!!AJ"Y
> M[VB7U9RPSM+;\9>FNZ.RR"-(EOGZ_")%CIRKP;+)\*[0_Z^^U#5EQ2E4K*FY
> MSX*?V,_9YM+6W9JMRFZ7YV".Y\S7[-'ZINOS)"JX+K:_^KO^R5,FR=0HIJN
> MRI:FN^;J\^#F\25-G25*F+_+W=+>\,#*X,+.Y/7V^[K%U/O]_B-'DG^G\_#T
> M^\?2X7.2T4=NNI_%^B%#B=OD]_?X^Z_#[?#R^)>IQ*K![XZX\"%#BIRUYZ*Q
> MQV:"I?#S^*.RQYJNS*O"[]/>]55YP2I7LW*:ZH6GZR=0I%MRC[[.\#5)8U&#
> MT?_______P``````````````````````````````````````````````````
> M`````````````````````````````````````````````````"'Y! $``&8`
> M+ `````/``\```>?@.&:"@.X2%AH>"`0$$! \>*X@.!99-E558+AR64"CA"89B%
> M*&4S)#X``EI1&0P,+X)8DR!/.0*495\F0&8B94I2`P47MEXC%#\="D$3.A%4
> M90T-'"Y=)V `3< 5&C*41DP.63L`5S J1STI944M!F1D-SP`8_/S2&5#-%MB
> F3@.E$AA!EVKDC<R"$(2X2-L1@.D> `E"6&DB! 8*/&!PM3, 0"`#L`
> `
> end|||You are getting into a complicated environment. If your asp applications are
on a different server than RS you are going to run into the double hop
problem. That is a windows issue where someone who is recognized by your web
app as one person then is not recognized when credentials hop from one
server to another. This requires kerboros to work. I am just giving you a
heads up. This is only an issue if you are using integrated security. If you
are using forms based security (i.e. role your own credentials) then it is
not an issue.
A parameter can be hidden so if someone goes directly to report manager
(portal for RS) they will not see the parameter. OR, you can also tie the
report to the user. RS has a global variable called userid that gives the
domain and userid of the user running the report. You could use this to only
allow users to see the data they should.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<lance.sanchez@.gmail.com> wrote in message
news:1190054179.058425.32890@.50g2000hsm.googlegroups.com...
> Thank you, is there a way to tie it into the IIS session so someone
> would generate an error if they tried to change the parameter to
> something else?
>
> On Sep 17, 11:29 am, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
> wrote:
>> Not automatically but you can pass a parameter that is used by your
>> report
>> to use the appropriate datasource.
>> In RS 2005 you can use an expression for your data source. Which if you
>> write your reports to expect a parameter (say DBParam) then you can do
>> exactly what you want. From Books OnLine:
>> Data Source Expressions
>> You can put an expression into a connection string to allow users to
>> select
>> the data source at run time. For example, suppose a multinational firm
>> has
>> data servers in several countries. With an expression-based connection
>> string, a user who is running a sales report can select a data source for
>> a
>> particular country before running the report.
>> The following example illustrates the use of a data source expression in
>> a
>> SQL Server connection string. The example assumes you have created a
>> report
>> parameter named ServerName:
>> Copy Code
>> ="data source=" & Parameters!ServerName.Value & ";initial
>> catalog=AdventureWorks
>> Data source expressions are processed at run time or when a report is
>> previewed. The expression must be written in Visual Basic. Use the
>> following
>> guidelines when defining a data source expression:
>> a.. Design the report using a static connection string. A static
>> connection string refers to a connection string that is not set through
>> an
>> expression (for example, when you follow the steps for creating a
>> report-specific or shared data source, you are defining a static
>> connection
>> string). Using a static connection string allows you to connect to the
>> data
>> source in Report Designer so that you can get the query results you need
>> to
>> create the report.
>> b.. When defining the data source connection, do not use a shared data
>> source. You cannot use a data source expression in a shared data source.
>> You
>> must define a report-specific data source for the report.
>> c.. Specify credentials separately from the connection string. You can
>> use
>> stored credentials, prompted credentials, or integrated security.
>> d.. Add a report parameter to specify a data source. For parameter
>> values,
>> you can either provide a static list of available values (in this case,
>> the
>> available values should be data sources you can use with the report) or
>> define a query that retrieves a list of data sources at run time.
>> e.. Be sure that the list of data sources shares the same database
>> schema.
>> All report design begins with schema information. If there is a mismatch
>> between the schema used to define the report and the actual schema used
>> by
>> the report at run time, the report might not run.
>> f.. Before publishing the report, replace the static connection string
>> with an expression. Wait until you are finished designing the report
>> before
>> you replace the static connection string with an expression. Once you use
>> an
>> expression, you cannot execute the query in Report Designer. Furthermore,
>> the field list in the Datasets window and the Parameters list will not
>> update automatically.
>> >>>>>>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> <lance.sanc...@.gmail.com> wrote in message
>> news:1190052200.309137.245860@.d55g2000hsg.googlegroups.com...
>>
>> > Were working on a classic asp app and are trying to implement some
>> > reports through reporting service. I have a few questions.
>> > First the application were working on will have multiple instances, so
>> > one a single server there can be upto 15 identical apps connecting to
>> > different databases, is there a way to have reporting service limit
>> > what data source reporting service can access depending on what IIS
>> > website/application pool the browsers are accessing?
>> > Badgers.servername.com/reportserver should open the reports with the
>> > badgers db
>> > Squirrels.servername.com/reportserver db=squirrels
>> > Servername.com:54333 db=badgers
>> > Servername.com:54334 db=squirrels
>> begin 666 copycode.gif
>> M1TE&.#EA#P`/`.9F`).BM[+"V*[$\(&NY:Z_U'.AWER,VIBKQBE4JIFLQ_S]
>> M_LO/U)*P[8JN_,73\JFXSF2%R=;>[/;Y_>OO]BM7L6Z<VB)&CZ:]["!!AJ"Y
>> M[VB7U9RPSM+;\9>FNZ.RR"-(EOGZ_")%CIRKP;+)\*[0_Z^^U#5EQ2E4K*FY
>> MSX*?V,_9YM+6W9JMRFZ7YV".Y\S7[-'ZINOS)"JX+K:_^KO^R5,FR=0HIJN
>> MRI:FN^;J\^#F\25-G25*F+_+W=+>\,#*X,+.Y/7V^[K%U/O]_B-'DG^G\_#T
>> M^\?2X7.2T4=NNI_%^B%#B=OD]_?X^Z_#[?#R^)>IQ*K![XZX\"%#BIRUYZ*Q
>> MQV:"I?#S^*.RQYJNS*O"[]/>]55YP2I7LW*:ZH6GZR=0I%MRC[[.\#5)8U&#
>> MT?_______P``````````````````````````````````````````````````
>> M`````````````````````````````````````````````````"'Y! $``&8`
>> M+ `````/``\```>?@.&:"@.X2%AH>"`0$$! \>*X@.!99-E558+AR64"CA"89B%
>> M*&4S)#X``EI1&0P,+X)8DR!/.0*495\F0&8B94I2`P47MEXC%#\="D$3.A%4
>> M90T-'"Y=)V `3< 5&C*41DP.63L`5S J1STI944M!F1D-SP`8_/S2&5#-%MB
>> F3@.E$AA!EVKDC<R"$(2X2-L1@.D> `E"6&DB! 8*/&!PM3, 0"`#L`
>> `
>> end
>|||Thank you once again, no the reports and the database are on the same
server and we are using forms based authentication, or i should say we
will be when i implement it.
one last question if you don't mind. i'm working some some complex
layouts that i have only been able to accomplish with sub reports, is
there a way to pass a parameter from a list object into a dataset?
hmm, i'm not happy with that question, let me give an example. we have
a root table, it has many tables that are related to it with a foreign
key. I have found that when trying to do it with a single report (a
single query with outer joins) that reporting services runs out of
memory when there are 20-30 tables all returning rows (and the unique
attribute set on the tables in reporting services), a way to get
around this has been to make sub reports that I pass the ID from the
root table to and have it render the page, but this is taking a Large
number of sub reports and i fear there is a lot of room for an error.
so instead of passing the ID to another report can it be passed to a
record set thats runs an additional query per ID?
On Sep 17, 2:02 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> You are getting into a complicated environment. If your asp applications are
> on a different server than RS you are going to run into the double hop
> problem. That is a windows issue where someone who is recognized by your web
> app as one person then is not recognized when credentials hop from one
> server to another. This requires kerboros to work. I am just giving you a
> heads up. This is only an issue if you are using integrated security. If you
> are using forms based security (i.e. role your own credentials) then it is
> not an issue.
> A parameter can be hidden so if someone goes directly to report manager
> (portal for RS) they will not see the parameter. OR, you can also tie the
> report to the user. RS has a global variable called userid that gives the
> domain and userid of the user running the report. You could use this to only
> allow users to see the data they should.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <lance.sanc...@.gmail.com> wrote in message
> news:1190054179.058425.32890@.50g2000hsm.googlegroups.com...
> > Thank you, is there a way to tie it into the IIS session so someone
> > would generate an error if they tried to change the parameter to
> > something else?
> > On Sep 17, 11:29 am, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
> > wrote:
> >> Not automatically but you can pass a parameter that is used by your
> >> report
> >> to use the appropriate datasource.
> >> In RS 2005 you can use an expression for your data source. Which if you
> >> write your reports to expect a parameter (say DBParam) then you can do
> >> exactly what you want. From Books OnLine:
> >> Data Source Expressions
> >> You can put an expression into a connection string to allow users to
> >> select
> >> the data source at run time. For example, suppose a multinational firm
> >> has
> >> data servers in several countries. With an expression-based connection
> >> string, a user who is running a sales report can select a data source for
> >> a
> >> particular country before running the report.
> >> The following example illustrates the use of a data source expression in
> >> a
> >> SQL Server connection string. The example assumes you have created a
> >> report
> >> parameter named ServerName:
> >> Copy Code
> >> ="data source=" & Parameters!ServerName.Value & ";initial
> >> catalog=AdventureWorks
> >> Data source expressions are processed at run time or when a report is
> >> previewed. The expression must be written in Visual Basic. Use the
> >> following
> >> guidelines when defining a data source expression:
> >> a.. Design the report using a static connection string. A static
> >> connection string refers to a connection string that is not set through
> >> an
> >> expression (for example, when you follow the steps for creating a
> >> report-specific or shared data source, you are defining a static
> >> connection
> >> string). Using a static connection string allows you to connect to the
> >> data
> >> source in Report Designer so that you can get the query results you need
> >> to
> >> create the report.
> >> b.. When defining the data source connection, do not use a shared data
> >> source. You cannot use a data source expression in a shared data source.
> >> You
> >> must define a report-specific data source for the report.
> >> c.. Specify credentials separately from the connection string. You can
> >> use
> >> stored credentials, prompted credentials, or integrated security.
> >> d.. Add a report parameter to specify a data source. For parameter
> >> values,
> >> you can either provide a static list of available values (in this case,
> >> the
> >> available values should be data sources you can use with the report) or
> >> define a query that retrieves a list of data sources at run time.
> >> e.. Be sure that the list of data sources shares the same database
> >> schema.
> >> All report design begins with schema information. If there is a mismatch
> >> between the schema used to define the report and the actual schema used
> >> by
> >> the report at run time, the report might not run.
> >> f.. Before publishing the report, replace the static connection string
> >> with an expression. Wait until you are finished designing the report
> >> before
> >> you replace the static connection string with an expression. Once you use
> >> an
> >> expression, you cannot execute the query in Report Designer. Furthermore,
> >> the field list in the Datasets window and the Parameters list will not
> >> update automatically.
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >> <lance.sanc...@.gmail.com> wrote in message
> >>news:1190052200.309137.245860@.d55g2000hsg.googlegroups.com...
> >> > Were working on a classic asp app and are trying to implement some
> >> > reports through reporting service. I have a few questions.
> >> > First the application were working on will have multiple instances, so
> >> > one a single server there can be upto 15 identical apps connecting to
> >> > different databases, is there a way to have reporting service limit
> >> > what data source reporting service can access depending on what IIS
> >> > website/application pool the browsers are accessing?
> >> > Badgers.servername.com/reportserver should open the reports with the
> >> > badgers db
> >> > Squirrels.servername.com/reportserver db=squirrels
> >> > Servername.com:54333 db=badgers
> >> > Servername.com:54334 db=squirrels
> >> begin 666 copycode.gif
> >> M1TE&.#EA#P`/`.9F`).BM[+"V*[$\(&NY:Z_U'.AWER,VIBKQBE4JIFLQ_S]
> >> M_LO/U)*P[8JN_,73\JFXSF2%R=;>[/;Y_>OO]BM7L6Z<VB)&CZ:]["!!AJ"Y
> >> M[VB7U9RPSM+;\9>FNZ.RR"-(EOGZ_")%CIRKP;+)\*[0_Z^^U#5EQ2E4K*FY
> >> MSX*?V,_9YM+6W9JMRFZ7YV".Y\S7[-'ZINOS)"JX+K:_^KO^R5,FR=0HIJN
> >> MRI:FN^;J\^#F\25-G25*F+_+W=+>\,#*X,+.Y/7V^[K%U/O]_B-'DG^G\_#T
> >> M^\?2X7.2T4=NNI_%^B%#B=OD]_?X^Z_#[?#R^)>IQ*K![XZX\"%#BIRUYZ*Q
> >> MQV:"I?#S^*.RQYJNS*O"[]/>]55YP2I7LW*:ZH6GZR=0I%MRC[[.\#5)8U&#
> >> MT?_______P``````````````````````````````````````````````````
> >> M`````````````````````````````````````````````````"'Y! $``&8`
> >> M+ `````/``\```>?@.&:"@.X2%AH>"`0$$! \>*X@.!99-E558+AR64"CA"89B%
> >> M*&4S)#X``EI1&0P,+X)8DR!/.0*495\F0&8B94I2`P47MEXC%#\="D$3.A%4
> >> M90T-'"Y=)V `3< 5&C*41DP.63L`5S J1STI944M!F1D-SP`8_/S2&5#-%MB
> >> F3@.E$AA!EVKDC<R"$(2X2-L1@.D> `E"6&DB! 8*/&!PM3, 0"`#L`
> >> `
> >> end|||never mind, i'm going through olderposts and I do belive someone else
was trying to do the same thing and you said data regions cannot do a
parent child relationship that I need.
On Sep 17, 3:22 pm, "lance.sanc...@.gmail.com"
<lance.sanc...@.gmail.com> wrote:
> Thank you once again, no the reports and the database are on the same
> server and we are using forms based authentication, or i should say we
> will be when i implement it.
> one last question if you don't mind. i'm working some some complex
> layouts that i have only been able to accomplish with sub reports, is
> there a way to pass a parameter from a list object into a dataset?
> hmm, i'm not happy with that question, let me give an example. we have
> a root table, it has many tables that are related to it with a foreign
> key. I have found that when trying to do it with a single report (a
> single query with outer joins) that reporting services runs out of
> memory when there are 20-30 tables all returning rows (and the unique
> attribute set on the tables in reporting services), a way to get
> around this has been to make sub reports that I pass the ID from the
> root table to and have it render the page, but this is taking a Large
> number of sub reports and i fear there is a lot of room for an error.
> so instead of passing the ID to another report can it be passed to a
> record set thats runs an additional query per ID?
> On Sep 17, 2:02 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
> wrote:
> > You are getting into a complicated environment. If your asp applications are
> > on a different server than RS you are going to run into the double hop
> > problem. That is a windows issue where someone who is recognized by your web
> > app as one person then is not recognized when credentials hop from one
> > server to another. This requires kerboros to work. I am just giving you a
> > heads up. This is only an issue if you are using integrated security. If you
> > are using forms based security (i.e. role your own credentials) then it is
> > not an issue.
> > A parameter can be hidden so if someone goes directly to report manager
> > (portal for RS) they will not see the parameter. OR, you can also tie the
> > report to the user. RS has a global variable called userid that gives the
> > domain and userid of the user running the report. You could use this to only
> > allow users to see the data they should.
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> > <lance.sanc...@.gmail.com> wrote in message
> >news:1190054179.058425.32890@.50g2000hsm.googlegroups.com...
> > > Thank you, is there a way to tie it into the IIS session so someone
> > > would generate an error if they tried to change the parameter to
> > > something else?
> > > On Sep 17, 11:29 am, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
> > > wrote:
> > >> Not automatically but you can pass a parameter that is used by your
> > >> report
> > >> to use the appropriate datasource.
> > >> In RS 2005 you can use an expression for your data source. Which if you
> > >> write your reports to expect a parameter (say DBParam) then you can do
> > >> exactly what you want. From Books OnLine:
> > >> Data Source Expressions
> > >> You can put an expression into a connection string to allow users to
> > >> select
> > >> the data source at run time. For example, suppose a multinational firm
> > >> has
> > >> data servers in several countries. With an expression-based connection
> > >> string, a user who is running a sales report can select a data source for
> > >> a
> > >> particular country before running the report.
> > >> The following example illustrates the use of a data source expression in
> > >> a
> > >> SQL Server connection string. The example assumes you have created a
> > >> report
> > >> parameter named ServerName:
> > >> Copy Code
> > >> ="data source=" & Parameters!ServerName.Value & ";initial
> > >> catalog=AdventureWorks
> > >> Data source expressions are processed at run time or when a report is
> > >> previewed. The expression must be written in Visual Basic. Use the
> > >> following
> > >> guidelines when defining a data source expression:
> > >> a.. Design the report using a static connection string. A static
> > >> connection string refers to a connection string that is not set through
> > >> an
> > >> expression (for example, when you follow the steps for creating a
> > >> report-specific or shared data source, you are defining a static
> > >> connection
> > >> string). Using a static connection string allows you to connect to the
> > >> data
> > >> source in Report Designer so that you can get the query results you need
> > >> to
> > >> create the report.
> > >> b.. When defining the data source connection, do not use a shared data
> > >> source. You cannot use a data source expression in a shared data source.
> > >> You
> > >> must define a report-specific data source for the report.
> > >> c.. Specify credentials separately from the connection string. You can
> > >> use
> > >> stored credentials, prompted credentials, or integrated security.
> > >> d.. Add a report parameter to specify a data source. For parameter
> > >> values,
> > >> you can either provide a static list of available values (in this case,
> > >> the
> > >> available values should be data sources you can use with the report) or
> > >> define a query that retrieves a list of data sources at run time.
> > >> e.. Be sure that the list of data sources shares the same database
> > >> schema.
> > >> All report design begins with schema information. If there is a mismatch
> > >> between the schema used to define the report and the actual schema used
> > >> by
> > >> the report at run time, the report might not run.
> > >> f.. Before publishing the report, replace the static connection string
> > >> with an expression. Wait until you are finished designing the report
> > >> before
> > >> you replace the static connection string with an expression. Once you use
> > >> an
> > >> expression, you cannot execute the query in Report Designer. Furthermore,
> > >> the field list in the Datasets window and the Parameters list will not
> > >> update automatically.
> > >> --
> > >> Bruce Loehle-Conger
> > >> MVP SQL Server Reporting Services
> > >> <lance.sanc...@.gmail.com> wrote in message
> > >>news:1190052200.309137.245860@.d55g2000hsg.googlegroups.com...
> > >> > Were working on a classic asp app and are trying to implement some
> > >> > reports through reporting service. I have a few questions.
> > >> > First the application were working on will have multiple instances, so
> > >> > one a single server there can be upto 15 identical apps connecting to
> > >> > different databases, is there a way to have reporting service limit
> > >> > what data source reporting service can access depending on what IIS
> > >> > website/application pool the browsers are accessing?
> > >> > Badgers.servername.com/reportserver should open the reports with the
> > >> > badgers db
> > >> > Squirrels.servername.com/reportserver db=squirrels
> > >> > Servername.com:54333 db=badgers
> > >> > Servername.com:54334 db=squirrels
> > >> begin 666 copycode.gif
> > >> M1TE&.#EA#P`/`.9F`).BM[+"V*[$\(&NY:Z_U'.AWER,VIBKQBE4JIFLQ_S]
> > >> M_LO/U)*P[8JN_,73\JFXSF2%R=;>[/;Y_>OO]BM7L6Z<VB)&CZ:]["!!AJ"Y
> > >> M[VB7U9RPSM+;\9>FNZ.RR"-(EOGZ_")%CIRKP;+)\*[0_Z^^U#5EQ2E4K*FY
> > >> MSX*?V,_9YM+6W9JMRFZ7YV".Y\S7[-'ZINOS)"JX+K:_^KO^R5,FR=0HIJN
> > >> MRI:FN^;J\^#F\25-G25*F+_+W=+>\,#*X,+.Y/7V^[K%U/O]_B-'DG^G\_#T
> > >> M^\?2X7.2T4=NNI_%^B%#B=OD]_?X^Z_#[?#R^)>IQ*K![XZX\"%#BIRUYZ*Q
> > >> MQV:"I?#S^*.RQYJNS*O"[]/>]55YP2I7LW*:ZH6GZR=0I%MRC[[.\#5)8U&#
> > >> MT?_______P``````````````````````````````````````````````````
> > >> M`````````````````````````````````````````````````"'Y! $``&8`
> > >> M+ `````/``\```>?@.&:"@.X2%AH>"`0$$! \>*X@.!99-E558+AR64"CA"89B%
> > >> M*&4S)#X``EI1&0P,+X)8DR!/.0*495\F0&8B94I2`P47MEXC%#\="D$3.A%4
> > >> M90T-'"Y=)V `3< 5&C*41DP.63L`5S J1STI944M!F1D-SP`8_/S2&5#-%MB
> > >> F3@.E$AA!EVKDC<R"$(2X2-L1@.D> `E"6&DB! 8*/&!PM3, 0"`#L`
> > >> `
> > >> end|||you can use a DNS round robin.
setup your report data source like:
data source=MyServer.mydomain.com
in the dns server, setup 2 different IP addresses for MyServer.mydomain.com.
insure that the round robin option is setup in the DNS server.
now some accesses go to the first server and some others will go through
the second one.
you can also do this using the NLB feature (network load balancing) to
spread the traffic to multiple servers.
maybe these options will helps you.
<lance.sanchez@.gmail.com> wrote in message
news:1190052200.309137.245860@.d55g2000hsg.googlegroups.com...
> Were working on a classic asp app and are trying to implement some
> reports through reporting service. I have a few questions.
> First the application were working on will have multiple instances, so
> one a single server there can be upto 15 identical apps connecting to
> different databases, is there a way to have reporting service limit
> what data source reporting service can access depending on what IIS
> website/application pool the browsers are accessing?
> Badgers.servername.com/reportserver should open the reports with the
> badgers db
> Squirrels.servername.com/reportserver db=squirrels
> Servername.com:54333 db=badgers
> Servername.com:54334 db=squirrels
>|||Correct.
I really recommend that you stay away from your outer join technique. You
need to limit the amount of data that is rendered. Subreports is really the
way to go. Also, consider changing your design that you don't show all the
data at once and instead use drill through. I.e. you create a link, they
click on the link if they want additional data (just make the text of the
field to click on blue and underline, users are used to clicking on that
visual clue) they click on it. I think the idea of showing everything is a
holdover from older reporting solutions. RS is ideal for showing just the
data you need to see and then click on a link for additional data. It is
very easy to do (jump to report action) and very fast way of showing the
data.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<lance.sanchez@.gmail.com> wrote in message
news:1190069078.994657.163370@.w3g2000hsg.googlegroups.com...
> never mind, i'm going through olderposts and I do belive someone else
> was trying to do the same thing and you said data regions cannot do a
> parent child relationship that I need.
> On Sep 17, 3:22 pm, "lance.sanc...@.gmail.com"
> <lance.sanc...@.gmail.com> wrote:
>> Thank you once again, no the reports and the database are on the same
>> server and we are using forms based authentication, or i should say we
>> will be when i implement it.
>> one last question if you don't mind. i'm working some some complex
>> layouts that i have only been able to accomplish with sub reports, is
>> there a way to pass a parameter from a list object into a dataset?
>> hmm, i'm not happy with that question, let me give an example. we have
>> a root table, it has many tables that are related to it with a foreign
>> key. I have found that when trying to do it with a single report (a
>> single query with outer joins) that reporting services runs out of
>> memory when there are 20-30 tables all returning rows (and the unique
>> attribute set on the tables in reporting services), a way to get
>> around this has been to make sub reports that I pass the ID from the
>> root table to and have it render the page, but this is taking a Large
>> number of sub reports and i fear there is a lot of room for an error.
>> so instead of passing the ID to another report can it be passed to a
>> record set thats runs an additional query per ID?
>> On Sep 17, 2:02 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
>> wrote:
>> > You are getting into a complicated environment. If your asp
>> > applications are
>> > on a different server than RS you are going to run into the double hop
>> > problem. That is a windows issue where someone who is recognized by
>> > your web
>> > app as one person then is not recognized when credentials hop from one
>> > server to another. This requires kerboros to work. I am just giving you
>> > a
>> > heads up. This is only an issue if you are using integrated security.
>> > If you
>> > are using forms based security (i.e. role your own credentials) then it
>> > is
>> > not an issue.
>> > A parameter can be hidden so if someone goes directly to report manager
>> > (portal for RS) they will not see the parameter. OR, you can also tie
>> > the
>> > report to the user. RS has a global variable called userid that gives
>> > the
>> > domain and userid of the user running the report. You could use this to
>> > only
>> > allow users to see the data they should.
>> > --
>> > Bruce Loehle-Conger
>> > MVP SQL Server Reporting Services
>> > <lance.sanc...@.gmail.com> wrote in message
>> >news:1190054179.058425.32890@.50g2000hsm.googlegroups.com...
>> > > Thank you, is there a way to tie it into the IIS session so someone
>> > > would generate an error if they tried to change the parameter to
>> > > something else?
>> > > On Sep 17, 11:29 am, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
>> > > wrote:
>> > >> Not automatically but you can pass a parameter that is used by your
>> > >> report
>> > >> to use the appropriate datasource.
>> > >> In RS 2005 you can use an expression for your data source. Which if
>> > >> you
>> > >> write your reports to expect a parameter (say DBParam) then you can
>> > >> do
>> > >> exactly what you want. From Books OnLine:
>> > >> Data Source Expressions
>> > >> You can put an expression into a connection string to allow users to
>> > >> select
>> > >> the data source at run time. For example, suppose a multinational
>> > >> firm
>> > >> has
>> > >> data servers in several countries. With an expression-based
>> > >> connection
>> > >> string, a user who is running a sales report can select a data
>> > >> source for
>> > >> a
>> > >> particular country before running the report.
>> > >> The following example illustrates the use of a data source
>> > >> expression in
>> > >> a
>> > >> SQL Server connection string. The example assumes you have created a
>> > >> report
>> > >> parameter named ServerName:
>> > >> Copy Code
>> > >> ="data source=" & Parameters!ServerName.Value & ";initial
>> > >> catalog=AdventureWorks
>> > >> Data source expressions are processed at run time or when a report
>> > >> is
>> > >> previewed. The expression must be written in Visual Basic. Use the
>> > >> following
>> > >> guidelines when defining a data source expression:
>> > >> a.. Design the report using a static connection string. A static
>> > >> connection string refers to a connection string that is not set
>> > >> through
>> > >> an
>> > >> expression (for example, when you follow the steps for creating a
>> > >> report-specific or shared data source, you are defining a static
>> > >> connection
>> > >> string). Using a static connection string allows you to connect to
>> > >> the
>> > >> data
>> > >> source in Report Designer so that you can get the query results you
>> > >> need
>> > >> to
>> > >> create the report.
>> > >> b.. When defining the data source connection, do not use a shared
>> > >> data
>> > >> source. You cannot use a data source expression in a shared data
>> > >> source.
>> > >> You
>> > >> must define a report-specific data source for the report.
>> > >> c.. Specify credentials separately from the connection string. You
>> > >> can
>> > >> use
>> > >> stored credentials, prompted credentials, or integrated security.
>> > >> d.. Add a report parameter to specify a data source. For parameter
>> > >> values,
>> > >> you can either provide a static list of available values (in this
>> > >> case,
>> > >> the
>> > >> available values should be data sources you can use with the report)
>> > >> or
>> > >> define a query that retrieves a list of data sources at run time.
>> > >> e.. Be sure that the list of data sources shares the same database
>> > >> schema.
>> > >> All report design begins with schema information. If there is a
>> > >> mismatch
>> > >> between the schema used to define the report and the actual schema
>> > >> used
>> > >> by
>> > >> the report at run time, the report might not run.
>> > >> f.. Before publishing the report, replace the static connection
>> > >> string
>> > >> with an expression. Wait until you are finished designing the report
>> > >> before
>> > >> you replace the static connection string with an expression. Once
>> > >> you use
>> > >> an
>> > >> expression, you cannot execute the query in Report Designer.
>> > >> Furthermore,
>> > >> the field list in the Datasets window and the Parameters list will
>> > >> not
>> > >> update automatically.
>> > >> --
>> > >> Bruce Loehle-Conger
>> > >> MVP SQL Server Reporting Services
>> > >> <lance.sanc...@.gmail.com> wrote in message
>> > >>news:1190052200.309137.245860@.d55g2000hsg.googlegroups.com...
>> > >> > Were working on a classic asp app and are trying to implement some
>> > >> > reports through reporting service. I have a few questions.
>> > >> > First the application were working on will have multiple
>> > >> > instances, so
>> > >> > one a single server there can be upto 15 identical apps connecting
>> > >> > to
>> > >> > different databases, is there a way to have reporting service
>> > >> > limit
>> > >> > what data source reporting service can access depending on what
>> > >> > IIS
>> > >> > website/application pool the browsers are accessing?
>> > >> > Badgers.servername.com/reportserver should open the reports with
>> > >> > the
>> > >> > badgers db
>> > >> > Squirrels.servername.com/reportserver db=squirrels
>> > >> > Servername.com:54333 db=badgers
>> > >> > Servername.com:54334 db=squirrels
>> > >> begin 666 copycode.gif
>> > >> M1TE&.#EA#P`/`.9F`).BM[+"V*[$\(&NY:Z_U'.AWER,VIBKQBE4JIFLQ_S]
>> > >> M_LO/U)*P[8JN_,73\JFXSF2%R=;>[/;Y_>OO]BM7L6Z<VB)&CZ:]["!!AJ"Y
>> > >> M[VB7U9RPSM+;\9>FNZ.RR"-(EOGZ_")%CIRKP;+)\*[0_Z^^U#5EQ2E4K*FY
>> > >> MSX*?V,_9YM+6W9JMRFZ7YV".Y\S7[-'ZINOS)"JX+K:_^KO^R5,FR=0HIJN
>> > >> MRI:FN^;J\^#F\25-G25*F+_+W=+>\,#*X,+.Y/7V^[K%U/O]_B-'DG^G\_#T
>> > >> M^\?2X7.2T4=NNI_%^B%#B=OD]_?X^Z_#[?#R^)>IQ*K![XZX\"%#BIRUYZ*Q
>> > >> MQV:"I?#S^*.RQYJNS*O"[]/>]55YP2I7LW*:ZH6GZR=0I%MRC[[.\#5)8U&#
>> > >> MT?_______P``````````````````````````````````````````````````
>> > >> M`````````````````````````````````````````````````"'Y! $``&8`
>> > >> M+ `````/``\```>?@.&:"@.X2%AH>"`0$$! \>*X@.!99-E558+AR64"CA"89B%
>> > >> M*&4S)#X``EI1&0P,+X)8DR!/.0*495\F0&8B94I2`P47MEXC%#\="D$3.A%4
>> > >> M90T-'"Y=)V `3< 5&C*41DP.63L`5S J1STI944M!F1D-SP`8_/S2&5#-%MB
>> > >> F3@.E$AA!EVKDC<R"$(2X2-L1@.D> `E"6&DB! 8*/&!PM3, 0"`#L`
>> > >> `
>> > >> end
>

Reporting Server 2000 Authentication Issue

Hi,

I have installed the eval version of Reporting Services 2000 on my pc. And i've used the report viewer control to view the report on a ASP.NET Page. When i view that .ASPX page, i get a windows authentication window before it opens the actual report.

Is there any way to disable this windows authentication dialouge box?

Regards,

PS: in the viewer i gave the path of the report as http://localhost/Rerport/ABC.rdl
I also tried with the ip address in place of localhost.
The ReportViewer control that ships with Visual Studio 2005 does not support Reporting Services 2000.

-Lukasz