Reporting services 2005 crashes

Hi All ,
I installed SQL server 2005 Enterprise edition 64 bit on windows server 2003
enterprise edition 64 bit machine.
I created a project and using a wizard created a report with Analysis
services cube as a datasource.Preview works fine but when I try to fix the
fonts or add elements and try to save it it crashes.How ever with out saving
I build the report or use the debug it works fine for the first time the next
time all the columns are deleted from the dataset.
I reproduced this problem thrice using diffrent prifile logons and creating
the project in different drives.
Thank you .
Rose.Applied Service pack noweverything seems good.
"Rose" wrote:
> Hi All ,
> I installed SQL server 2005 Enterprise edition 64 bit on windows server 2003
> enterprise edition 64 bit machine.
> I created a project and using a wizard created a report with Analysis
> services cube as a datasource.Preview works fine but when I try to fix the
> fonts or add elements and try to save it it crashes.How ever with out saving
> I build the report or use the debug it works fine for the first time the next
> time all the columns are deleted from the dataset.
> I reproduced this problem thrice using diffrent prifile logons and creating
> the project in different drives.
>
> Thank you .
> Rose.

Reporting Services - Overload and OutofMemoryException - Workaround?

We're having a good bit of trouble with a deployed report overloading
the server during times of heavy use. The report renders directly
from an external app to Excel, running the report by way of URL. I
haven't found any tuning that helps us - we have about 1200 clients
who try to run the report in a 2-hour span. Sometimes it seems like
they're all hitting it in the same 10 minutes. I can see the activity
in the performance monitor. Once active report requests reach 40 or
so, we usually get an OutOfMemory exception and RS recycles. It picks
back up, but the users who were waiting all get errors.
I couldn't find a metering option to force requests into a 'holding'
queue if active requests reach a threshold, so I'm trying to build a
workaround. I'm posting the basics of it here, in case it might help
anyone else.
' This code will go into the page that redirects users
' to the report. The page will either prompt the user
' to refresh or will have a refresh META tag
Dim rs As New sqlrpts.ReportingService
rs.Credentials = New System.Net.NetworkCredential _
("userid", "password", "domain")
' or - System.Net.CredentialCache.DefaultCredentials()
Dim jobs As sqlrpts.Job
Dim intx As Int16 = 0
For Each jobs In rs.ListJobs
intx = intx + 1
Next
' If intx is above the threshold we'll set (probably 25-30),
' we'll display a 'please wait' message. Otherwise, we'll
' redirect to the report URL
If anyone knows a better way around this, please reply on this thread
or email me.
Thanks!
Tim ShayHi Tim,
Just need to check with you quickly, which counter are you using to
determine the OutOfMemory exception and RS recycle?
Also, have you tried using ACT to test the report URL and see how many
RPS it can process? Coz we're having similar problem and is wondering
why RS cannot process concurrent user requests for the web application
we're developing.
Appreciate your input, thanks!
CCC
tshay@.foodlion.com (TShay) wrote in message news:<1fe4fd2c.0409100828.795a3ae3@.posting.google.com>...
> We're having a good bit of trouble with a deployed report overloading
> the server during times of heavy use. The report renders directly
> from an external app to Excel, running the report by way of URL. I
> haven't found any tuning that helps us - we have about 1200 clients
> who try to run the report in a 2-hour span. Sometimes it seems like
> they're all hitting it in the same 10 minutes. I can see the activity
> in the performance monitor. Once active report requests reach 40 or
> so, we usually get an OutOfMemory exception and RS recycles. It picks
> back up, but the users who were waiting all get errors.
> I couldn't find a metering option to force requests into a 'holding'
> queue if active requests reach a threshold, so I'm trying to build a
> workaround. I'm posting the basics of it here, in case it might help
> anyone else.
> ' This code will go into the page that redirects users
> ' to the report. The page will either prompt the user
> ' to refresh or will have a refresh META tag
> Dim rs As New sqlrpts.ReportingService
> rs.Credentials = New System.Net.NetworkCredential _
> ("userid", "password", "domain")
> ' or - System.Net.CredentialCache.DefaultCredentials()
> Dim jobs As sqlrpts.Job
> Dim intx As Int16 = 0
> For Each jobs In rs.ListJobs
> intx = intx + 1
> Next
> ' If intx is above the threshold we'll set (probably 25-30),
> ' we'll display a 'please wait' message. Otherwise, we'll
> ' redirect to the report URL
> If anyone knows a better way around this, please reply on this thread
> or email me.
> Thanks!
> Tim Shay

Reporting Options

Hello all. I am currently doing some research into options for

setting up reporting. Right now we have a server on EE that's

getting hit a bit too hard by the reports. The budget is

currently a bit low, but we already have a second server

purchased.

For our reporting, we need data that is up to date within the last 15

minutes (less if possible). Because of the potential size of some

of our transactions, I've ruled out log shipping as being too much

downtime of the reporting data while the second server is catching up

to speed. So, I'm trying to figure out what reporting options I

have left open to me.

1) I understand that for reporting purposes, a snapshot must be taken

of the mirrored server. Why are reports not able to run directly

off the mirror live (or am I mistaken?).

2) Is it possible to mirror from EE to SE (remember, low budget for the second server)?

3) How high is the overhead when doing a snapshot every 5-15 minutes (

I would think it's machine specific, but overall is it pretty quick or

prohibitive based on how often the snapshot would be needed)?

4) Is replication perhaps a better option based on how up to date the

data has to be? Are there any other options that may be available

for near-realtime reporting?

Thanks in advance for your time.

1) Mirroring occurs at a physical level so the pages are not necessarily transactionally consistent for scans to occur. Creating a snapshot runs recovery and brings the database to a consistent state.

2) Yes, but you cannot create snapshots on SE.

3) Not very high in most cases. You can make it even less by doing a CHECKPOINT on the principal shortly before creating the snapshot on the mirror as the snapshot will have to recover from the last checkpoint. There are some DDL and long transaction cases that can make snapshot creation somewhat more burdensome.

4) Replication combined with snapshot isolation level scans to do the reads on the reporting server seems like it might also be viable.

|||In general, consider Replication as a Reporting solution and DBM as a High Availability solution. Transactional replication should satisfy all of your requirements.

Reporting on blank fields in Crystal

Hi,
having a bit of trouble trying to get my Crystal report to give me a count of the blank fields in a database field...any ideas?What do you mean by 'blank'? Empty or NULL?|||use a formula

if isnull(field) then
1
else
0|||I suppose the field will be null, I will try the formula to test for this. Thanks.