Report Parameter Length

We are planning on passing in an XML document as a report parameter but have
not been able to determine if there is a maximum parameter length. Does SQL
Reporting Services 2000 have a maximum parameter length?
Thanks.I can only partially answer your question... If you are passing the parameter
via URL then you are constrained by the max URL length ( might be 255 I
think)..
YOu can pass the info INSIDE the HTML which removes the URL restriction...
There are examples in Books on line - search for URL under Reporting Services
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"RobinB" wrote:
> We are planning on passing in an XML document as a report parameter but have
> not been able to determine if there is a maximum parameter length. Does SQL
> Reporting Services 2000 have a maximum parameter length?
> Thanks.

Report Manager web site doesn't work in FireFox...

But with some simple changes to ReportingServices.js it does.
1: Replace all instances of "document.all" with "document.getElementById".
2: Add in this:
window.navigate = function(url)
{
window.location = url;
}
I don't know why the author didn't just use getElementById from the
get-go. Also, the second function is because the navigation depends on
"window.navigate", which doesn't exist--except in IE. If I find
anything else, I'll try to remember to post updates.
Granger<sigh> Nevermind. I forgot about the "event" object in IE. There's no
quick fix on that one. ...except if you disabled the Javascript
validation routines. Once again, the application disappoints.
Granger Godbold wrote:
> But with some simple changes to ReportingServices.js it does.
>
> 1: Replace all instances of "document.all" with "document.getElementById".
> 2: Add in this:
> window.navigate = function(url)
> {
> window.location = url;
> }
>
> I don't know why the author didn't just use getElementById from the
> get-go. Also, the second function is because the navigation depends on
> "window.navigate", which doesn't exist--except in IE. If I find
> anything else, I'll try to remember to post updates.
> Granger

Report is rssuccess but browser continues until time out (no document returned)

Hi,
Basically, we're having a problem on our production servers, that is
that a report is running for 2h (this is expected, large data set) and
IE6 is setup up for a 4h timeout (via a registry entry). The browser
will display the spinning report generation icon for the entire 4h
before timing out. However, the server log is reporting that the report
had succeeded (rssuccess), 1.5 hours BEFORE the browser fails.
Servers/Services are Win2003, Reporting Services SP2, SQL Server 2000
SP3
The machines sit behind a load balancer, which might be important (HTTP
requests etc.).
We're stumped :-(
Any ideas?
Thanks
RolandoWhat happens after the browser fails? What indication points out that
the browser fails?
It gives you a "This application needs to be closed" error?
Is there a different error? It just freezes?|||Sorcerdon,
When the browsers times out at its designated timeout value (4 hours),
we get the standard IE6 "Page cannot be displayed" page.
Do you have some idea of what might be going on?
Thanks|||Try running it and turn off "Show friendly HTTP messeges" in the
browser options.
Go to Options --> ADvanced tab --> Its under Browsing.
This will provide you with a more detailed error messege.
BTW, where is this error show up? in the actual report window? or it
redirects to the error page?
regards,
Stas K.