report pack for iis - report generation taking long?

I've got this installed and the sample database was working fine. I then
imported about a weeks worth from two iis servers (grew the DB to about 5
GB) and now pulling up any of the default 12 reports takes at least 30
minutes to an hour or longer. Is this normal? The SQL server is a dual
xeon, 2 GB of RAM, 3 disk (15k rpm) raid 5 with SQL 2000 SP3 and Reporting
Services SP2.Try to do a select of the same data and see how long it takes...RS will be
slower than that of course - but will not be faster than your select when it
queries the data..
Ensure you have properly indexed tables.
You may also wish to run the query on a schedule and deliver it from cache -
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Joe" <joe@.do.not.email.me> wrote in message
news:%23%234FpU4qFHA.248@.TK2MSFTNGP14.phx.gbl...
> I've got this installed and the sample database was working fine. I then
> imported about a weeks worth from two iis servers (grew the DB to about 5
> GB) and now pulling up any of the default 12 reports takes at least 30
> minutes to an hour or longer. Is this normal? The SQL server is a dual
> xeon, 2 GB of RAM, 3 disk (15k rpm) raid 5 with SQL 2000 SP3 and Reporting
> Services SP2.
>

Report Model (Data Source View) issue

We've built an oltp that uses nothing but synonyms that reach out to various DB's in the organization thru linked servers.

The issue that we are having is Data Source Views can only see tables and views. Is it possible to use synonyms? If not what would be a work around.

Please advise. Thanks

Steve

I use linked servers in reports (actually, let's be honest, I use linked servers pretty much ALL THE TIME ).

I haven't done this with Report Models that I can recall. But I am pretty sure that what works for me would work in Report Models.

There are a couple of things you can do as a workaround:

1. If you don't have other uses for the synonyms, eliminate the synonym from the equation entirely and just use fully-qualified syntax in views, for example (and of course you don't have to use * here!) :

CREATE VIEW vw_Synonym1 AS SELECT * FROM MyLinkedServer.MyDB1.dbo.MyTable

2. I'm not entirely sure that the models can't use synonyms! It's likely that they can but the wizards and interfaces that you're given in the designer cannot. If I'm right, you just need to write something to handle the model XML directly to get what you want.

I am not going to mess with this to test it out, because I don't spend a lot of time with report models, but start with the XSD (which must be published) and figure out whether the appropriate values should go. Then alter a copy of an existing model that you have to test -- I bet it works. If you want to go this route and get stuck on the details, holler. <g>

3. If you do have other uses for the synonyms, as apparently you do, and if you don't want to mess with the model xml, you can create a view that represents each synonym in a one-to-one relationship. IOW, pretty much CREATE VIEW vw_Synonym1 AS SELECT * FROM Synonym1. Again I know that * is evil but you get the picture <s>. Extend this properly as follows:

You can avoid the evil "*" by interrogating the properties of the thing underneath. You can automate all current synonyms to create new views (and leverage the interrogation code you just wrote) by examining SELECT * FROM sys.synonyms and writing code that works through the list. You can automate all future synonyms you create to do the same thing automatically by using a database trigger. Here is a sketch:

Report Manager Web Client Security Error

I am attempting to access an Access database file located on one of our
servers on the network through Reporting Services Report Manager and am
receiving the error below. I have already setup our Report Server
Service account to a domain account that has full Access to the file. I
am able to run the report from Visual Studio.Net on my local machine. I
have setup and successfully deployed numerous SQL Server based reports
and am able to run an Access based report as long as it's located on my
report server. Any help anyone could provide is extremely appreciated.
============================================== Reporting Services Error
----
An error has occurred during report processing. (rsProcessingAborted)
Get Online Help
Cannot create a connection to data source 'DataSource1'.
(rsErrorOpeningConnection) Get Online Help
The Microsoft Jet database engine cannot open the file
'\\Server02\PhoneBook\PhoneBook.mdb'. It is already opened exclusively
by another user, or you need permission to view its data.
----
Microsoft Reporting Services
==============================================Have you tried running it with Vis Studio closed?
I have not done this with RS, but I did have many problems connecting
asp pages to access using a DSN.
I ended up using a DSN-Less connection and it worked. I am not sure if
that is an option in RS though.
"Leo" <leo_olden@.yahoo.com> wrote in message news:leo_olden@.yahoo.com:
> I am attempting to access an Access database file located on one of our
> servers on the network through Reporting Services Report Manager and am
> receiving the error below. I have already setup our Report Server
> Service account to a domain account that has full Access to the file. I
> am able to run the report from Visual Studio.Net on my local machine. I
> have setup and successfully deployed numerous SQL Server based reports
> and am able to run an Access based report as long as it's located on my
> report server. Any help anyone could provide is extremely appreciated.
> ==============================================> Reporting Services Error
> ----
> --
> An error has occurred during report processing. (rsProcessingAborted)
> Get Online Help
> Cannot create a connection to data source 'DataSource1'.
> (rsErrorOpeningConnection) Get Online Help
> The Microsoft Jet database engine cannot open the file
> '\\Server02\PhoneBook\PhoneBook.mdb'. It is already opened exclusively
> by another user, or you need permission to view its data.
> ----
> --
> Microsoft Reporting Services
> ==============================================|||Thanks for your reply John. I actually did some further research and
found that the problem I'm experiencing is a known problem with Access
and the Microsoft Jet database engine. My workaround was to create a
batch file on my report server that copies in the original Access
database file to the report server every hour. My datasource now
resides on my report server and is therefore accessible.

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.

Report Formatting Differently on different servers with same RDL

This is a good one:

Same RDL, 2 different servers. I run the report on my computer and export to PDF, it prints properly. When the customer runs the report on their server (SSRS 2K5 SP1, same as mine), they get it displayed differently. The columns on the report extend to the next page and the lines are thicker.

Is this a formatting issue on the customer's PC? It uses standard fonts (Tahoma, Sans-serif).

Any ideas?

maybe you are using a matrix on the report and the customer has different data (more data) that makes the matrix extend?

lines are thicker? I can't think of anything there unless it is the fonts, but you look ok with that.

|||

No, it is not a matrix report. It is a standard layout table that is 10 inches wide, it's set for landscape with .5in margins.

|||I did some more research and started a new report from scratch and the same issue occurs.