New RS server TimeProcessing very large

We just installed a new server dedicated to Reporting Services. I uploaded
our report definitions and ran a test. The TimeProcessing value is huge
compared to our old server.
Old server: RS 2005 as part of database cluster on an instances that also
hosts data, 32-bit OS and SQL (SP2), 2.79GHz, 16GB RAM with 7.5GB dedicated
to SQL, Xeon 2.80GHz, PAE
New server: Dedicated to Reporting Services 2005, 64-bit OS and SQL (SP2),
2.66GHz, 16GB RAM, min server memory and max server memory configuration
values are still the defaults, Xeon X5355@.2.66 GHz
Do you have any suggestions on where I can look to begin troubleshooting
this performance issue?
StephanieStephanie, I am also facing the same issue in the same kind of 64-bit OS,
RS2005.
Have you got any solution to this issue?
Kavitha
url:http://www.ureader.com/msg/115713370.aspx|||The volume of data being brought back in our case was too large (we were
trying to bring back data files, not reports) and we were using Excel, which
consumes a tremendous amount of memory. Microsoft's answer was that we
should not be using RS to deliver files, only reports of a printable size,
i.e. not 300 page reports.
"Kavitha" wrote:
> Stephanie, I am also facing the same issue in the same kind of 64-bit OS,
> RS2005.
> Have you got any solution to this issue?
> Kavitha
> url:http://www.ureader.com/msg/115713370.aspx
>|||Keep in mind that if you want to bring over data try CSV ASCII instead of
Excel for large data amounts of data.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
news:FB4109A9-B5DA-4509-8020-1747C3A2179A@.microsoft.com...
> The volume of data being brought back in our case was too large (we were
> trying to bring back data files, not reports) and we were using Excel,
> which
> consumes a tremendous amount of memory. Microsoft's answer was that we
> should not be using RS to deliver files, only reports of a printable size,
> i.e. not 300 page reports.
>
> "Kavitha" wrote:
>> Stephanie, I am also facing the same issue in the same kind of 64-bit OS,
>> RS2005.
>> Have you got any solution to this issue?
>> Kavitha
>> url:http://www.ureader.com/msg/115713370.aspx|||Thanks, Bruce. I think that is exactly the direction that we are going in.
Stephanie
"Bruce L-C [MVP]" wrote:
> Keep in mind that if you want to bring over data try CSV ASCII instead of
> Excel for large data amounts of data.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
> news:FB4109A9-B5DA-4509-8020-1747C3A2179A@.microsoft.com...
> > The volume of data being brought back in our case was too large (we were
> > trying to bring back data files, not reports) and we were using Excel,
> > which
> > consumes a tremendous amount of memory. Microsoft's answer was that we
> > should not be using RS to deliver files, only reports of a printable size,
> > i.e. not 300 page reports.
> >
> >
> > "Kavitha" wrote:
> >
> >> Stephanie, I am also facing the same issue in the same kind of 64-bit OS,
> >> RS2005.
> >>
> >> Have you got any solution to this issue?
> >>
> >> Kavitha
> >>
> >> url:http://www.ureader.com/msg/115713370.aspx
> >>
>
>|||One other point then (that is obscure) there is a server setting that will
default CSV to ascii so that Excel brings up the data properly split between
cells. Otherwise the default is unicode that Excel doesn't know what to do
with so it puts it all into one column that the user then has to split
(there is a menu in Excel to do this).
Let me know if you need the config setting for this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
news:C7FD6C07-7965-4D15-AA73-F2DBC217559C@.microsoft.com...
> Thanks, Bruce. I think that is exactly the direction that we are going
> in.
> Stephanie
>
> "Bruce L-C [MVP]" wrote:
>> Keep in mind that if you want to bring over data try CSV ASCII instead of
>> Excel for large data amounts of data.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
>> news:FB4109A9-B5DA-4509-8020-1747C3A2179A@.microsoft.com...
>> > The volume of data being brought back in our case was too large (we
>> > were
>> > trying to bring back data files, not reports) and we were using Excel,
>> > which
>> > consumes a tremendous amount of memory. Microsoft's answer was that
>> > we
>> > should not be using RS to deliver files, only reports of a printable
>> > size,
>> > i.e. not 300 page reports.
>> >
>> >
>> > "Kavitha" wrote:
>> >
>> >> Stephanie, I am also facing the same issue in the same kind of 64-bit
>> >> OS,
>> >> RS2005.
>> >>
>> >> Have you got any solution to this issue?
>> >>
>> >> Kavitha
>> >>
>> >> url:http://www.ureader.com/msg/115713370.aspx
>> >>
>>|||Really? That would be GREAT! I'm always having to break it up into the
multiple columns manually. I didn't know that you could have this done
automatically. This is a RS configuration setting? Or RS server setting?
How do I update that setting?
Stephanie
"Bruce L-C [MVP]" wrote:
> One other point then (that is obscure) there is a server setting that will
> default CSV to ascii so that Excel brings up the data properly split between
> cells. Otherwise the default is unicode that Excel doesn't know what to do
> with so it puts it all into one column that the user then has to split
> (there is a menu in Excel to do this).
> Let me know if you need the config setting for this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
> news:C7FD6C07-7965-4D15-AA73-F2DBC217559C@.microsoft.com...
> > Thanks, Bruce. I think that is exactly the direction that we are going
> > in.
> >
> > Stephanie
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Keep in mind that if you want to bring over data try CSV ASCII instead of
> >> Excel for large data amounts of data.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
> >> news:FB4109A9-B5DA-4509-8020-1747C3A2179A@.microsoft.com...
> >> > The volume of data being brought back in our case was too large (we
> >> > were
> >> > trying to bring back data files, not reports) and we were using Excel,
> >> > which
> >> > consumes a tremendous amount of memory. Microsoft's answer was that
> >> > we
> >> > should not be using RS to deliver files, only reports of a printable
> >> > size,
> >> > i.e. not 300 page reports.
> >> >
> >> >
> >> > "Kavitha" wrote:
> >> >
> >> >> Stephanie, I am also facing the same issue in the same kind of 64-bit
> >> >> OS,
> >> >> RS2005.
> >> >>
> >> >> Have you got any solution to this issue?
> >> >>
> >> >> Kavitha
> >> >>
> >> >> url:http://www.ureader.com/msg/115713370.aspx
> >> >>
> >>
> >>
> >>
>
>|||You only need to change in one place, rsreportserver.config. Reboot after
the change. The below shows commenting out the existing entry and putting in
the needed change to have CSV export as ASCII. I can understand this being a
default for MS because they are so international oriented but seeing as how
Excel doesn't understand Unicode CSV (at least through Excel 2003) , I don't
know about the most recent version. Anyway, this works great.
<!--
<Extension Name="CSV"
Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering"/>
-->
<Extension Name="CSV"
Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering">
<Configuration>
<DeviceInfo>
<Encoding>ASCII</Encoding>
</DeviceInfo>
</Configuration>
</Extension>
The other option is to use Jump to URL. Here is an example of a Jump to URL
link I use. This causes Excel to come up with the data in a separate window:
="javascript:void(window.open('" & Globals!ReportServerUrl &
"?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
"&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
If you don't want to have it appear in a new window then do this in jump to
URL:
=Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
I configure my server to export CSV in ASCII. Much handier.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
news:F3F00888-F052-4EFD-9079-29E829EB63F3@.microsoft.com...
> Really? That would be GREAT! I'm always having to break it up into the
> multiple columns manually. I didn't know that you could have this done
> automatically. This is a RS configuration setting? Or RS server setting?
> How do I update that setting?
> Stephanie
>
> "Bruce L-C [MVP]" wrote:
>> One other point then (that is obscure) there is a server setting that
>> will
>> default CSV to ascii so that Excel brings up the data properly split
>> between
>> cells. Otherwise the default is unicode that Excel doesn't know what to
>> do
>> with so it puts it all into one column that the user then has to split
>> (there is a menu in Excel to do this).
>> Let me know if you need the config setting for this.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
>> news:C7FD6C07-7965-4D15-AA73-F2DBC217559C@.microsoft.com...
>> > Thanks, Bruce. I think that is exactly the direction that we are going
>> > in.
>> >
>> > Stephanie
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Keep in mind that if you want to bring over data try CSV ASCII instead
>> >> of
>> >> Excel for large data amounts of data.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
>> >> news:FB4109A9-B5DA-4509-8020-1747C3A2179A@.microsoft.com...
>> >> > The volume of data being brought back in our case was too large (we
>> >> > were
>> >> > trying to bring back data files, not reports) and we were using
>> >> > Excel,
>> >> > which
>> >> > consumes a tremendous amount of memory. Microsoft's answer was
>> >> > that
>> >> > we
>> >> > should not be using RS to deliver files, only reports of a printable
>> >> > size,
>> >> > i.e. not 300 page reports.
>> >> >
>> >> >
>> >> > "Kavitha" wrote:
>> >> >
>> >> >> Stephanie, I am also facing the same issue in the same kind of
>> >> >> 64-bit
>> >> >> OS,
>> >> >> RS2005.
>> >> >>
>> >> >> Have you got any solution to this issue?
>> >> >>
>> >> >> Kavitha
>> >> >>
>> >> >> url:http://www.ureader.com/msg/115713370.aspx
>> >> >>
>> >>
>> >>
>> >>
>>|||Bruce,
Great. I'll try the config change. I'm going to do some testing in my
development environment. Do I have to reboot the RS server or can I just
restart RS?
Stephanie
"Bruce L-C [MVP]" wrote:
> You only need to change in one place, rsreportserver.config. Reboot after
> the change. The below shows commenting out the existing entry and putting in
> the needed change to have CSV export as ASCII. I can understand this being a
> default for MS because they are so international oriented but seeing as how
> Excel doesn't understand Unicode CSV (at least through Excel 2003) , I don't
> know about the most recent version. Anyway, this works great.
> <!--
> <Extension Name="CSV"
> Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering"/>
> -->
> <Extension Name="CSV"
> Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering">
> <Configuration>
> <DeviceInfo>
> <Encoding>ASCII</Encoding>
> </DeviceInfo>
> </Configuration>
> </Extension>
> The other option is to use Jump to URL. Here is an example of a Jump to URL
> link I use. This causes Excel to come up with the data in a separate window:
> ="javascript:void(window.open('" & Globals!ReportServerUrl &
> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
> If you don't want to have it appear in a new window then do this in jump to
> URL:
> =Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
> Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
> I configure my server to export CSV in ASCII. Much handier.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
> news:F3F00888-F052-4EFD-9079-29E829EB63F3@.microsoft.com...
> > Really? That would be GREAT! I'm always having to break it up into the
> > multiple columns manually. I didn't know that you could have this done
> > automatically. This is a RS configuration setting? Or RS server setting?
> >
> > How do I update that setting?
> >
> > Stephanie
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> One other point then (that is obscure) there is a server setting that
> >> will
> >> default CSV to ascii so that Excel brings up the data properly split
> >> between
> >> cells. Otherwise the default is unicode that Excel doesn't know what to
> >> do
> >> with so it puts it all into one column that the user then has to split
> >> (there is a menu in Excel to do this).
> >>
> >> Let me know if you need the config setting for this.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
> >> news:C7FD6C07-7965-4D15-AA73-F2DBC217559C@.microsoft.com...
> >> > Thanks, Bruce. I think that is exactly the direction that we are going
> >> > in.
> >> >
> >> > Stephanie
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Keep in mind that if you want to bring over data try CSV ASCII instead
> >> >> of
> >> >> Excel for large data amounts of data.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
> >> >> news:FB4109A9-B5DA-4509-8020-1747C3A2179A@.microsoft.com...
> >> >> > The volume of data being brought back in our case was too large (we
> >> >> > were
> >> >> > trying to bring back data files, not reports) and we were using
> >> >> > Excel,
> >> >> > which
> >> >> > consumes a tremendous amount of memory. Microsoft's answer was
> >> >> > that
> >> >> > we
> >> >> > should not be using RS to deliver files, only reports of a printable
> >> >> > size,
> >> >> > i.e. not 300 page reports.
> >> >> >
> >> >> >
> >> >> > "Kavitha" wrote:
> >> >> >
> >> >> >> Stephanie, I am also facing the same issue in the same kind of
> >> >> >> 64-bit
> >> >> >> OS,
> >> >> >> RS2005.
> >> >> >>
> >> >> >> Have you got any solution to this issue?
> >> >> >>
> >> >> >> Kavitha
> >> >> >>
> >> >> >> url:http://www.ureader.com/msg/115713370.aspx
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||I would assume restart will do it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
news:8A028412-E210-4A2D-8CC5-E395E5BD3474@.microsoft.com...
> Bruce,
> Great. I'll try the config change. I'm going to do some testing in my
> development environment. Do I have to reboot the RS server or can I just
> restart RS?
> Stephanie
>
> "Bruce L-C [MVP]" wrote:
>> You only need to change in one place, rsreportserver.config. Reboot after
>> the change. The below shows commenting out the existing entry and putting
>> in
>> the needed change to have CSV export as ASCII. I can understand this
>> being a
>> default for MS because they are so international oriented but seeing as
>> how
>> Excel doesn't understand Unicode CSV (at least through Excel 2003) , I
>> don't
>> know about the most recent version. Anyway, this works great.
>> <!--
>> <Extension Name="CSV"
>> Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering"/>
>> -->
>> <Extension Name="CSV"
>> Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering">
>> <Configuration>
>> <DeviceInfo>
>> <Encoding>ASCII</Encoding>
>> </DeviceInfo>
>> </Configuration>
>> </Extension>
>> The other option is to use Jump to URL. Here is an example of a Jump to
>> URL
>> link I use. This causes Excel to come up with the data in a separate
>> window:
>> ="javascript:void(window.open('" & Globals!ReportServerUrl &
>> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
>> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
>> If you don't want to have it appear in a new window then do this in jump
>> to
>> URL:
>> =Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
>> Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
>> I configure my server to export CSV in ASCII. Much handier.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
>> news:F3F00888-F052-4EFD-9079-29E829EB63F3@.microsoft.com...
>> > Really? That would be GREAT! I'm always having to break it up into
>> > the
>> > multiple columns manually. I didn't know that you could have this done
>> > automatically. This is a RS configuration setting? Or RS server
>> > setting?
>> >
>> > How do I update that setting?
>> >
>> > Stephanie
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> One other point then (that is obscure) there is a server setting that
>> >> will
>> >> default CSV to ascii so that Excel brings up the data properly split
>> >> between
>> >> cells. Otherwise the default is unicode that Excel doesn't know what
>> >> to
>> >> do
>> >> with so it puts it all into one column that the user then has to split
>> >> (there is a menu in Excel to do this).
>> >>
>> >> Let me know if you need the config setting for this.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
>> >> news:C7FD6C07-7965-4D15-AA73-F2DBC217559C@.microsoft.com...
>> >> > Thanks, Bruce. I think that is exactly the direction that we are
>> >> > going
>> >> > in.
>> >> >
>> >> > Stephanie
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Keep in mind that if you want to bring over data try CSV ASCII
>> >> >> instead
>> >> >> of
>> >> >> Excel for large data amounts of data.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
>> >> >> news:FB4109A9-B5DA-4509-8020-1747C3A2179A@.microsoft.com...
>> >> >> > The volume of data being brought back in our case was too large
>> >> >> > (we
>> >> >> > were
>> >> >> > trying to bring back data files, not reports) and we were using
>> >> >> > Excel,
>> >> >> > which
>> >> >> > consumes a tremendous amount of memory. Microsoft's answer was
>> >> >> > that
>> >> >> > we
>> >> >> > should not be using RS to deliver files, only reports of a
>> >> >> > printable
>> >> >> > size,
>> >> >> > i.e. not 300 page reports.
>> >> >> >
>> >> >> >
>> >> >> > "Kavitha" wrote:
>> >> >> >
>> >> >> >> Stephanie, I am also facing the same issue in the same kind of
>> >> >> >> 64-bit
>> >> >> >> OS,
>> >> >> >> RS2005.
>> >> >> >>
>> >> >> >> Have you got any solution to this issue?
>> >> >> >>
>> >> >> >> Kavitha
>> >> >> >>
>> >> >> >> url:http://www.ureader.com/msg/115713370.aspx
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>