Reporting Services Quirks?

Hi,
I'm a bit of a newbies to BIDS and SQL Server 2005 and I've noticed a
couple on things about Reporting Services.
- Has anyone noticed that it's almost impossible to get the background
and font settings
to work in the Reporting Services Query Analyzer?
-When I execute any query with a "where" clause, the Query Analyzer
returns the column headings but no returned data is visible. However,
it seems to be getting the results back, because my reports run with
the results set. Also, the SQl analyzer runs it without a
hitch...weird.
- Does Reporting Services ever just stop and hang for you? I usually
have to reboot several times a day. Even though this is the only thing
running on my machine except SQL Query Anayzer. I have only a half
gig of RAM, but I have very little running on the desktop.
So far I have patched, and service packed both SQL and Visual Studio
2005, but still have weird behavior with the tool. Anyway, as misery
loves company, please respond with your stories and any fixes you have
found.
Best,
ScottOn Jul 9, 8:22 pm, dunnsc...@.gmail.com wrote:
> Hi,
> I'm a bit of a newbies to BIDS and SQL Server 2005 and I've noticed a
> couple on things about Reporting Services.
> - Has anyone noticed that it's almost impossible to get the background
> and font settings
> to work in the Reporting Services Query Analyzer?
> -When I execute any query with a "where" clause, the Query Analyzer
> returns the column headings but no returned data is visible. However,
> it seems to be getting the results back, because my reports run with
> the results set. Also, the SQl analyzer runs it without a
> hitch...weird.
> - Does Reporting Services ever just stop and hang for you? I usually
> have to reboot several times a day. Even though this is the only thing
> running on my machine except SQL Query Anayzer. I have only a half
> gig of RAM, but I have very little running on the desktop.
> So far I have patched, and service packed both SQL and Visual Studio
> 2005, but still have weird behavior with the tool. Anyway, as misery
> loves company, please respond with your stories and any fixes you have
> found.
> Best,
> Scott
The issues you are experiencing seem to be related to minimal
available RAM. Check out this article for SQL Server 2005 system/
hardware requirements (http://msdn2.microsoft.com/en-us/library/
ms143506.aspx). I have not personally experienced these types of
performance issues w/SQL Server 2005 or SSRS 2005. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||On Jul 9, 9:22 pm, dunnsc...@.gmail.com wrote:
> Hi,
> I'm a bit of a newbies to BIDS and SQL Server 2005 and I've noticed a
> couple on things about Reporting Services.
> - Has anyone noticed that it's almost impossible to get the background
> and font settings
> to work in the Reporting Services Query Analyzer?
> -When I execute any query with a "where" clause, the Query Analyzer
> returns the column headings but no returned data is visible. However,
> it seems to be getting the results back, because my reports run with
> the results set. Also, the SQl analyzer runs it without a
> hitch...weird.
> - Does Reporting Services ever just stop and hang for you? I usually
> have to reboot several times a day. Even though this is the only thing
> running on my machine except SQL Query Anayzer. I have only a half
> gig of RAM, but I have very little running on the desktop.
> So far I have patched, and service packed both SQL and Visual Studio
> 2005, but still have weird behavior with the tool. Anyway, as misery
> loves company, please respond with your stories and any fixes you have
> found.
> Best,
> Scott
I occasionally have to restart my computer. I usually leave it
running for a week or so without a restart and VS works fine. I got a
GIG of RAM on a Pentium D. I prefer AMD and I believe it's
performance is better (especially dual core) but I have not had too
much of a problem with this work machine. Try optimizing your quires
and your parameters. I changed parameters from looking at a table to
looking to a mapping table for populating... it brought down the
report from minutes to seconds in execution. I am having some weird
problems when trying to run reports from the reporting site but no one
has replied to me with a solution.