I would like to know if it is possible to export a report created with reporting
service
in Microsoft Word or RTF format.
Thank's in advance
Giorgio ParmeggianiNot out of the box. I don't know if there are 3rd party renderers or not.
You can do Excel and PDF which might fit your needs. And, of course, HTML.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Giorgio Parmeggiani" <gipasoft@.newsgroups.nospam> wrote in message
news:ddf4e4a662b78c7c7182df905e2@.msnews.microsoft.com...
> I would like to know if it is possible to export a report created with
> reporting service in Microsoft Word or RTF format.
> Thank's in advance
> Giorgio Parmeggiani
>|||Hi Giorgio,
Welcome to use MSDN Managed Newsgroup!
We do not support render Word (RTF) format in the SQL Server Reporting
Services 2000/2005. You may try third party solution in the link below
Design Reports Using Microsoft Word
http://officewriter.softartisans.com/officewriter-296.aspx
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label service. Show all posts
Showing posts with label service. Show all posts
Sunday, March 11, 2012
Friday, March 9, 2012
Export to PDF in a new window using web service render method
We have an order screen which we would like to be visible at all times, and a
report based off some of the information on that screen. Is there any way to
keep this window open and open the report in a new window? Right now the
button used to launch the report is a server control button. This is what I
use now to open in the same window:
'setup parameters here...
result = rs.Render(reportPath, format, historyID, devInfo, parameters,
credentials, showHideToggle, encoding, mimeType, reportHistoryParameters,
warnings, streamIDs)
sh.SessionId = rs.SessionHeaderValue.SessionId
With Response
.ClearContent()
.AppendHeader("content-length", result.Length.ToString())
.ContentType = "application/pdf"
.BinaryWrite(result)
.Flush()
.Close()
End With
I did some reading and tried using window.open but to no avail. Any
suggestions?Does this help?
For the following you need SP1 or greater installed.
= "javascript:void(window.open('http://www.google.com','_blank'))"
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Treviathon" <Treviathon@.discussions.microsoft.com> wrote in message
news:454A2439-8071-48A2-9476-DA631E985D6C@.microsoft.com...
> We have an order screen which we would like to be visible at all times,
and a
> report based off some of the information on that screen. Is there any way
to
> keep this window open and open the report in a new window? Right now the
> button used to launch the report is a server control button. This is what
I
> use now to open in the same window:
> 'setup parameters here...
> result = rs.Render(reportPath, format, historyID, devInfo, parameters,
> credentials, showHideToggle, encoding, mimeType, reportHistoryParameters,
> warnings, streamIDs)
> sh.SessionId = rs.SessionHeaderValue.SessionId
> With Response
> .ClearContent()
> .AppendHeader("content-length", result.Length.ToString())
> .ContentType = "application/pdf"
> .BinaryWrite(result)
> .Flush()
> .Close()
> End With
> I did some reading and tried using window.open but to no avail. Any
> suggestions?|||I'm trying the same thing.
I've tried your solution, and it doesn't work for me. Maybe I'm
misunderstanding?
I've put the snippet of javascript on the OnClickevent of my asp.net
pushbutton, and I can't compile the project. Can you give me a fuller
sample?
Thx
report based off some of the information on that screen. Is there any way to
keep this window open and open the report in a new window? Right now the
button used to launch the report is a server control button. This is what I
use now to open in the same window:
'setup parameters here...
result = rs.Render(reportPath, format, historyID, devInfo, parameters,
credentials, showHideToggle, encoding, mimeType, reportHistoryParameters,
warnings, streamIDs)
sh.SessionId = rs.SessionHeaderValue.SessionId
With Response
.ClearContent()
.AppendHeader("content-length", result.Length.ToString())
.ContentType = "application/pdf"
.BinaryWrite(result)
.Flush()
.Close()
End With
I did some reading and tried using window.open but to no avail. Any
suggestions?Does this help?
For the following you need SP1 or greater installed.
= "javascript:void(window.open('http://www.google.com','_blank'))"
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Treviathon" <Treviathon@.discussions.microsoft.com> wrote in message
news:454A2439-8071-48A2-9476-DA631E985D6C@.microsoft.com...
> We have an order screen which we would like to be visible at all times,
and a
> report based off some of the information on that screen. Is there any way
to
> keep this window open and open the report in a new window? Right now the
> button used to launch the report is a server control button. This is what
I
> use now to open in the same window:
> 'setup parameters here...
> result = rs.Render(reportPath, format, historyID, devInfo, parameters,
> credentials, showHideToggle, encoding, mimeType, reportHistoryParameters,
> warnings, streamIDs)
> sh.SessionId = rs.SessionHeaderValue.SessionId
> With Response
> .ClearContent()
> .AppendHeader("content-length", result.Length.ToString())
> .ContentType = "application/pdf"
> .BinaryWrite(result)
> .Flush()
> .Close()
> End With
> I did some reading and tried using window.open but to no avail. Any
> suggestions?|||I'm trying the same thing.
I've tried your solution, and it doesn't work for me. Maybe I'm
misunderstanding?
I've put the snippet of javascript on the OnClickevent of my asp.net
pushbutton, and I can't compile the project. Can you give me a fuller
sample?
Thx
Sunday, February 26, 2012
Export to Excel 2000 format with Reporting services 2000 SP1
Hi,
I am clueless on how to generate the report in Excel 2000 format. i have
installed reporting services 2000 with service pack 2 in this machine. the
resultant Excel file format is in version 2003. i cant view that in Excel
2000. your feedback is highly appreciated.
Following is my code,
string report = m_ReportNameEXCEL;
string path = m_TargetReportLocation + report;
Byte[] bytes;
string format = "EXCEL";
string historyid = null;
string deviceInfo = null;
ReportServer.ParameterValue[] parameters;
DataSourceCredentials[] credentials = null;
string showhide = null;
string encoding = null;
string mimetype = null;
ParameterValue[] parameterused = null;
Warning[] warnings = null;
string[] streamIDs = null;
-
-
-
bytes = reportService.Render(
path,
format,
historyid,
deviceInfo,
parameters,
credentials,
showhide,
out encoding,
out mimetype,
out parameterused,
out warnings,
out streamIDs);
FileStream fs = File.Create(m_OutputPath + iYear.ToString()+ @."\" +
fileName);
fs.Write(bytes,0,bytes.Length);
fs.Close();
}
Thanks,
PradeepI have just looked it up in a Book. Only Excel 2002 or 2003 is supported. The
Data is rendered into MTHML with Mime Type ms-excel internally and brought to
Excel after that.
BUT: I am also using EXCEL 2000 on my machine and the exported Reports can
be opened without problems... (I have to say that I had Office 2003 on it
before, uninstalled it and installed OIffice 2000, God knows if there are any
DLLs left...?)
Maybe you are using anything inside your Report that needs a newer version?
Did you try a very simple Report?
There is the possibility to create your ow new Export formats. To do this
you have to program a File Rendering Extension. This is quite complex to
realize. You should get a good book to realize that.
Markus Poehler
netpoint-edv gmbh
"msnews.microsoft.com" wrote:
> Hi,
> I am clueless on how to generate the report in Excel 2000 format. i have
> installed reporting services 2000 with service pack 2 in this machine. the
> resultant Excel file format is in version 2003. i cant view that in Excel
> 2000. your feedback is highly appreciated.
> Following is my code,
> string report = m_ReportNameEXCEL;
> string path = m_TargetReportLocation + report;
> Byte[] bytes;
> string format = "EXCEL";
> string historyid = null;
> string deviceInfo = null;
> ReportServer.ParameterValue[] parameters;
> DataSourceCredentials[] credentials = null;
> string showhide = null;
> string encoding = null;
> string mimetype = null;
> ParameterValue[] parameterused = null;
> Warning[] warnings = null;
> string[] streamIDs = null;
> -
> -
> -
>
> bytes = reportService.Render(
> path,
> format,
> historyid,
> deviceInfo,
> parameters,
> credentials,
> showhide,
> out encoding,
> out mimetype,
> out parameterused,
> out warnings,
> out streamIDs);
>
> FileStream fs = File.Create(m_OutputPath + iYear.ToString()+ @."\" +
> fileName);
> fs.Write(bytes,0,bytes.Length);
> fs.Close();
> }
>
> Thanks,
> Pradeep
>
>|||SP1 and greater definitely creates native Excel format (that can be opened
in Excel 2000). To make sure the problem isn't your code, open up a report
in report manager and export it to Excel and see if you can open in Excel
2000. Note that when you upgrade to SP1 or SP2 it is both a report designer
upgrade and a RS server upgrade.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"MarkusPoehler" <MarkusPoehler@.discussions.microsoft.com> wrote in message
news:BB9415C5-7400-4C88-9001-5964112E55EC@.microsoft.com...
>I have just looked it up in a Book. Only Excel 2002 or 2003 is supported.
>The
> Data is rendered into MTHML with Mime Type ms-excel internally and brought
> to
> Excel after that.
> BUT: I am also using EXCEL 2000 on my machine and the exported Reports can
> be opened without problems... (I have to say that I had Office 2003 on it
> before, uninstalled it and installed OIffice 2000, God knows if there are
> any
> DLLs left...?)
> Maybe you are using anything inside your Report that needs a newer
> version?
> Did you try a very simple Report?
> There is the possibility to create your ow new Export formats. To do this
> you have to program a File Rendering Extension. This is quite complex to
> realize. You should get a good book to realize that.
> Markus Poehler
> netpoint-edv gmbh
> "msnews.microsoft.com" wrote:
>> Hi,
>> I am clueless on how to generate the report in Excel 2000 format. i have
>> installed reporting services 2000 with service pack 2 in this machine.
>> the
>> resultant Excel file format is in version 2003. i cant view that in Excel
>> 2000. your feedback is highly appreciated.
>> Following is my code,
>> string report = m_ReportNameEXCEL;
>> string path = m_TargetReportLocation + report;
>> Byte[] bytes;
>> string format = "EXCEL";
>> string historyid = null;
>> string deviceInfo = null;
>> ReportServer.ParameterValue[] parameters;
>> DataSourceCredentials[] credentials = null;
>> string showhide = null;
>> string encoding = null;
>> string mimetype = null;
>> ParameterValue[] parameterused = null;
>> Warning[] warnings = null;
>> string[] streamIDs = null;
>> -
>> -
>> -
>>
>> bytes = reportService.Render(
>> path,
>> format,
>> historyid,
>> deviceInfo,
>> parameters,
>> credentials,
>> showhide,
>> out encoding,
>> out mimetype,
>> out parameterused,
>> out warnings,
>> out streamIDs);
>>
>> FileStream fs = File.Create(m_OutputPath + iYear.ToString()+ @."\" +
>> fileName);
>> fs.Write(bytes,0,bytes.Length);
>> fs.Close();
>> }
>>
>> Thanks,
>> Pradeep
>>
I am clueless on how to generate the report in Excel 2000 format. i have
installed reporting services 2000 with service pack 2 in this machine. the
resultant Excel file format is in version 2003. i cant view that in Excel
2000. your feedback is highly appreciated.
Following is my code,
string report = m_ReportNameEXCEL;
string path = m_TargetReportLocation + report;
Byte[] bytes;
string format = "EXCEL";
string historyid = null;
string deviceInfo = null;
ReportServer.ParameterValue[] parameters;
DataSourceCredentials[] credentials = null;
string showhide = null;
string encoding = null;
string mimetype = null;
ParameterValue[] parameterused = null;
Warning[] warnings = null;
string[] streamIDs = null;
-
-
-
bytes = reportService.Render(
path,
format,
historyid,
deviceInfo,
parameters,
credentials,
showhide,
out encoding,
out mimetype,
out parameterused,
out warnings,
out streamIDs);
FileStream fs = File.Create(m_OutputPath + iYear.ToString()+ @."\" +
fileName);
fs.Write(bytes,0,bytes.Length);
fs.Close();
}
Thanks,
PradeepI have just looked it up in a Book. Only Excel 2002 or 2003 is supported. The
Data is rendered into MTHML with Mime Type ms-excel internally and brought to
Excel after that.
BUT: I am also using EXCEL 2000 on my machine and the exported Reports can
be opened without problems... (I have to say that I had Office 2003 on it
before, uninstalled it and installed OIffice 2000, God knows if there are any
DLLs left...?)
Maybe you are using anything inside your Report that needs a newer version?
Did you try a very simple Report?
There is the possibility to create your ow new Export formats. To do this
you have to program a File Rendering Extension. This is quite complex to
realize. You should get a good book to realize that.
Markus Poehler
netpoint-edv gmbh
"msnews.microsoft.com" wrote:
> Hi,
> I am clueless on how to generate the report in Excel 2000 format. i have
> installed reporting services 2000 with service pack 2 in this machine. the
> resultant Excel file format is in version 2003. i cant view that in Excel
> 2000. your feedback is highly appreciated.
> Following is my code,
> string report = m_ReportNameEXCEL;
> string path = m_TargetReportLocation + report;
> Byte[] bytes;
> string format = "EXCEL";
> string historyid = null;
> string deviceInfo = null;
> ReportServer.ParameterValue[] parameters;
> DataSourceCredentials[] credentials = null;
> string showhide = null;
> string encoding = null;
> string mimetype = null;
> ParameterValue[] parameterused = null;
> Warning[] warnings = null;
> string[] streamIDs = null;
> -
> -
> -
>
> bytes = reportService.Render(
> path,
> format,
> historyid,
> deviceInfo,
> parameters,
> credentials,
> showhide,
> out encoding,
> out mimetype,
> out parameterused,
> out warnings,
> out streamIDs);
>
> FileStream fs = File.Create(m_OutputPath + iYear.ToString()+ @."\" +
> fileName);
> fs.Write(bytes,0,bytes.Length);
> fs.Close();
> }
>
> Thanks,
> Pradeep
>
>|||SP1 and greater definitely creates native Excel format (that can be opened
in Excel 2000). To make sure the problem isn't your code, open up a report
in report manager and export it to Excel and see if you can open in Excel
2000. Note that when you upgrade to SP1 or SP2 it is both a report designer
upgrade and a RS server upgrade.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"MarkusPoehler" <MarkusPoehler@.discussions.microsoft.com> wrote in message
news:BB9415C5-7400-4C88-9001-5964112E55EC@.microsoft.com...
>I have just looked it up in a Book. Only Excel 2002 or 2003 is supported.
>The
> Data is rendered into MTHML with Mime Type ms-excel internally and brought
> to
> Excel after that.
> BUT: I am also using EXCEL 2000 on my machine and the exported Reports can
> be opened without problems... (I have to say that I had Office 2003 on it
> before, uninstalled it and installed OIffice 2000, God knows if there are
> any
> DLLs left...?)
> Maybe you are using anything inside your Report that needs a newer
> version?
> Did you try a very simple Report?
> There is the possibility to create your ow new Export formats. To do this
> you have to program a File Rendering Extension. This is quite complex to
> realize. You should get a good book to realize that.
> Markus Poehler
> netpoint-edv gmbh
> "msnews.microsoft.com" wrote:
>> Hi,
>> I am clueless on how to generate the report in Excel 2000 format. i have
>> installed reporting services 2000 with service pack 2 in this machine.
>> the
>> resultant Excel file format is in version 2003. i cant view that in Excel
>> 2000. your feedback is highly appreciated.
>> Following is my code,
>> string report = m_ReportNameEXCEL;
>> string path = m_TargetReportLocation + report;
>> Byte[] bytes;
>> string format = "EXCEL";
>> string historyid = null;
>> string deviceInfo = null;
>> ReportServer.ParameterValue[] parameters;
>> DataSourceCredentials[] credentials = null;
>> string showhide = null;
>> string encoding = null;
>> string mimetype = null;
>> ParameterValue[] parameterused = null;
>> Warning[] warnings = null;
>> string[] streamIDs = null;
>> -
>> -
>> -
>>
>> bytes = reportService.Render(
>> path,
>> format,
>> historyid,
>> deviceInfo,
>> parameters,
>> credentials,
>> showhide,
>> out encoding,
>> out mimetype,
>> out parameterused,
>> out warnings,
>> out streamIDs);
>>
>> FileStream fs = File.Create(m_OutputPath + iYear.ToString()+ @."\" +
>> fileName);
>> fs.Write(bytes,0,bytes.Length);
>> fs.Close();
>> }
>>
>> Thanks,
>> Pradeep
>>
Friday, February 24, 2012
Export To Excel
Hi Friends,
I am generating a report using sql server reporting service and
rendering it in my .aspx page in a report viewer control. Now i need
to export it to excel so that the excel file can be stored in client
pc.How do i show an save as dialoge box,so that user can either
save,open or cancel.
Please help me out.
Thanks,
RanjanOn Feb 27, 12:26 am, "Ranj" <ranjan.raghaven...@.gmail.com> wrote:
> Hi Friends,
> I am generating a report using sql server reporting service and
> rendering it in my .aspx page in a report viewer control. Now i need
> to export it to excel so that the excel file can be stored in client
> pc.How do i show an save as dialoge box,so that user can either
> save,open or cancel.
> Please help me out.
> Thanks,
> Ranjan
You should be able to use something like the following (basically,
call a header):
------
Response.Clear();
Response.AddHeader("content-disposition", "attachment;filename=" +
Session["SpecialName"].ToString() + "NameOfExcelSpreadsheet.xls");
Response.ContentType = "application/vnd.xls";
System.IO.StringWriter sw = new System.IO.StringWriter();
HtmlTextWriter htw = new HtmlTextWriter(sw);
this.ObjectName.RenderControl(htw);
Response.Write(sw.ToString());
Response.End();
------
I'm not certain this will work in the Report Viewer itself though. You
might need to add a button/etc to accomplish this outside the report
viewer. Hope this helps.
Regards,
Enrique Martinez
Sr. ASP.NET/SQL Server Developer
I am generating a report using sql server reporting service and
rendering it in my .aspx page in a report viewer control. Now i need
to export it to excel so that the excel file can be stored in client
pc.How do i show an save as dialoge box,so that user can either
save,open or cancel.
Please help me out.
Thanks,
RanjanOn Feb 27, 12:26 am, "Ranj" <ranjan.raghaven...@.gmail.com> wrote:
> Hi Friends,
> I am generating a report using sql server reporting service and
> rendering it in my .aspx page in a report viewer control. Now i need
> to export it to excel so that the excel file can be stored in client
> pc.How do i show an save as dialoge box,so that user can either
> save,open or cancel.
> Please help me out.
> Thanks,
> Ranjan
You should be able to use something like the following (basically,
call a header):
------
Response.Clear();
Response.AddHeader("content-disposition", "attachment;filename=" +
Session["SpecialName"].ToString() + "NameOfExcelSpreadsheet.xls");
Response.ContentType = "application/vnd.xls";
System.IO.StringWriter sw = new System.IO.StringWriter();
HtmlTextWriter htw = new HtmlTextWriter(sw);
this.ObjectName.RenderControl(htw);
Response.Write(sw.ToString());
Response.End();
------
I'm not certain this will work in the Report Viewer itself though. You
might need to add a button/etc to accomplish this outside the report
viewer. Hope this helps.
Regards,
Enrique Martinez
Sr. ASP.NET/SQL Server Developer
Export to Excel
Hi all,
I cannot open the Excel report exported from Reporting Service by Excel2000.
How to make the exported format (Excel) can be read by Excel2000?
Thx
CharlesMost of the Excel related problems are solved by Service Pack 1
Did you install it?
Some versions were not supported by RS before SP1. I guess your version is
one of them.
Eralper
http://www.kodyaz.com/ShowForum.aspx?ForumID=4
"Pro" wrote:
> Hi all,
> I cannot open the Excel report exported from Reporting Service by Excel2000.
> How to make the exported format (Excel) can be read by Excel2000?
> Thx
> Charles
>
>|||How to check which the version of the reporting service installed?
Thank you
Charles
"eralper" <eralper@.discussions.microsoft.com> wrote in message
news:A460D6D1-ACE8-4DE4-AA22-C5A44C243505@.microsoft.com...
> Most of the Excel related problems are solved by Service Pack 1
> Did you install it?
> Some versions were not supported by RS before SP1. I guess your version is
> one of them.
> Eralper
> http://www.kodyaz.com/ShowForum.aspx?ForumID=4
> "Pro" wrote:
>> Hi all,
>> I cannot open the Excel report exported from Reporting Service by
>> Excel2000.
>> How to make the exported format (Excel) can be read by Excel2000?
>> Thx
>> Charles
>>|||Hi,
You can check the thread at http://www.kodyaz.com/ShowPost.aspx?PostID=26
All you have to do is browsing the http://machine/reportserver url and
check the version number at the bottom of the page.
8.00.743.00 is the Retail version and 8.00.878.00 is SP1
Eralper
http://www.kodyaz.com/ShowForum.aspx?ForumID=4
"Pro" wrote:
> How to check which the version of the reporting service installed?
> Thank you
> Charles
> "eralper" <eralper@.discussions.microsoft.com> wrote in message
> news:A460D6D1-ACE8-4DE4-AA22-C5A44C243505@.microsoft.com...
> > Most of the Excel related problems are solved by Service Pack 1
> >
> > Did you install it?
> >
> > Some versions were not supported by RS before SP1. I guess your version is
> > one of them.
> >
> > Eralper
> > http://www.kodyaz.com/ShowForum.aspx?ForumID=4
> >
> > "Pro" wrote:
> >
> >> Hi all,
> >>
> >> I cannot open the Excel report exported from Reporting Service by
> >> Excel2000.
> >> How to make the exported format (Excel) can be read by Excel2000?
> >>
> >> Thx
> >> Charles
> >>
> >>
> >>
>
>|||Hi,
You can check the thread at http://www.kodyaz.com/ShowPost.aspx?PostID=26
All you have to do is browsing the http://machine/reportserver url and
check the version number at the bottom of the page.
8.00.743.00 is the Retail version and 8.00.878.00 is SP1
Eralper
http://www.kodyaz.com/ShowForum.aspx?ForumID=4
"Pro" wrote:
> How to check which the version of the reporting service installed?
> Thank you
> Charles
> "eralper" <eralper@.discussions.microsoft.com> wrote in message
> news:A460D6D1-ACE8-4DE4-AA22-C5A44C243505@.microsoft.com...
> > Most of the Excel related problems are solved by Service Pack 1
> >
> > Did you install it?
> >
> > Some versions were not supported by RS before SP1. I guess your version is
> > one of them.
> >
> > Eralper
> > http://www.kodyaz.com/ShowForum.aspx?ForumID=4
> >
> > "Pro" wrote:
> >
> >> Hi all,
> >>
> >> I cannot open the Excel report exported from Reporting Service by
> >> Excel2000.
> >> How to make the exported format (Excel) can be read by Excel2000?
> >>
> >> Thx
> >> Charles
> >>
> >>
> >>
>
>
I cannot open the Excel report exported from Reporting Service by Excel2000.
How to make the exported format (Excel) can be read by Excel2000?
Thx
CharlesMost of the Excel related problems are solved by Service Pack 1
Did you install it?
Some versions were not supported by RS before SP1. I guess your version is
one of them.
Eralper
http://www.kodyaz.com/ShowForum.aspx?ForumID=4
"Pro" wrote:
> Hi all,
> I cannot open the Excel report exported from Reporting Service by Excel2000.
> How to make the exported format (Excel) can be read by Excel2000?
> Thx
> Charles
>
>|||How to check which the version of the reporting service installed?
Thank you
Charles
"eralper" <eralper@.discussions.microsoft.com> wrote in message
news:A460D6D1-ACE8-4DE4-AA22-C5A44C243505@.microsoft.com...
> Most of the Excel related problems are solved by Service Pack 1
> Did you install it?
> Some versions were not supported by RS before SP1. I guess your version is
> one of them.
> Eralper
> http://www.kodyaz.com/ShowForum.aspx?ForumID=4
> "Pro" wrote:
>> Hi all,
>> I cannot open the Excel report exported from Reporting Service by
>> Excel2000.
>> How to make the exported format (Excel) can be read by Excel2000?
>> Thx
>> Charles
>>|||Hi,
You can check the thread at http://www.kodyaz.com/ShowPost.aspx?PostID=26
All you have to do is browsing the http://machine/reportserver url and
check the version number at the bottom of the page.
8.00.743.00 is the Retail version and 8.00.878.00 is SP1
Eralper
http://www.kodyaz.com/ShowForum.aspx?ForumID=4
"Pro" wrote:
> How to check which the version of the reporting service installed?
> Thank you
> Charles
> "eralper" <eralper@.discussions.microsoft.com> wrote in message
> news:A460D6D1-ACE8-4DE4-AA22-C5A44C243505@.microsoft.com...
> > Most of the Excel related problems are solved by Service Pack 1
> >
> > Did you install it?
> >
> > Some versions were not supported by RS before SP1. I guess your version is
> > one of them.
> >
> > Eralper
> > http://www.kodyaz.com/ShowForum.aspx?ForumID=4
> >
> > "Pro" wrote:
> >
> >> Hi all,
> >>
> >> I cannot open the Excel report exported from Reporting Service by
> >> Excel2000.
> >> How to make the exported format (Excel) can be read by Excel2000?
> >>
> >> Thx
> >> Charles
> >>
> >>
> >>
>
>|||Hi,
You can check the thread at http://www.kodyaz.com/ShowPost.aspx?PostID=26
All you have to do is browsing the http://machine/reportserver url and
check the version number at the bottom of the page.
8.00.743.00 is the Retail version and 8.00.878.00 is SP1
Eralper
http://www.kodyaz.com/ShowForum.aspx?ForumID=4
"Pro" wrote:
> How to check which the version of the reporting service installed?
> Thank you
> Charles
> "eralper" <eralper@.discussions.microsoft.com> wrote in message
> news:A460D6D1-ACE8-4DE4-AA22-C5A44C243505@.microsoft.com...
> > Most of the Excel related problems are solved by Service Pack 1
> >
> > Did you install it?
> >
> > Some versions were not supported by RS before SP1. I guess your version is
> > one of them.
> >
> > Eralper
> > http://www.kodyaz.com/ShowForum.aspx?ForumID=4
> >
> > "Pro" wrote:
> >
> >> Hi all,
> >>
> >> I cannot open the Excel report exported from Reporting Service by
> >> Excel2000.
> >> How to make the exported format (Excel) can be read by Excel2000?
> >>
> >> Thx
> >> Charles
> >>
> >>
> >>
>
>
Wednesday, February 15, 2012
Export Slow from SQL Reporting Service
We have users experiencing very slow to export SQL Reporting Service 2005
rendered data to EXCEL. Is there any way to improve the performance?
BrianOn Mar 9, 8:37 pm, Brian <B...@.discussions.microsoft.com> wrote:
> We have users experiencing very slow to export SQL Reporting Service 2005
> rendered data to EXCEL. Is there any way to improve the performance?
> Brian
Usually this is due to either high activity on the web server that the
reports are on -or- that the query or stored procedure sourcing the
report needs to be revised to improve performance. I would suggest
using the Database Engine Tuning Adviser against the stored procedure
or query to implement indexes, etc to improve the performance. Hope
this helps.
Regards,
Enrique Martinez
Sr. SQL Server Developer|||Hello,
What about exporting to other formats like PDF or MHTML. Is it very slow
too?
How complicated are these reports and how much data do they contain?
Sometimes the reason of slow exporting to Excel is complex structure of
reports (a lot of cells, nested objects, etc.).
If reports contain a lot of hidden rows all of them are saving to Excel file
(even if they are unseen during exporting).
Maybe this is the reason.
Regards,
Radoslaw Lebkowski
U¿ytkownik "Brian" <Brian@.discussions.microsoft.com> napisa³ w wiadomo¶ci
news:632830EF-9C4F-4A1C-B8C9-672E327E95C4@.microsoft.com...
> We have users experiencing very slow to export SQL Reporting Service 2005
> rendered data to EXCEL. Is there any way to improve the performance?
> Brian|||Thank you for the quick response.
The SQL Reporting 2005 report is a simple report which has no complex
structure in it. It is a single line type of report. However, it has the
company logo image on the title of the report. The report rendered within
one minute with 123 pages. When I export to EXCEL, it was ten times slower
then the web page rendered.
Does export require SQL to query the data again or it gathered the rendered
data to EXCEL?
Would increase SQL memory from dynamic to static with 3GB help? How about
caching the report?
Thanks,
Brian
"Radoslaw Lebkowski" wrote:
> Hello,
> What about exporting to other formats like PDF or MHTML. Is it very slow
> too?
> How complicated are these reports and how much data do they contain?
> Sometimes the reason of slow exporting to Excel is complex structure of
> reports (a lot of cells, nested objects, etc.).
> If reports contain a lot of hidden rows all of them are saving to Excel file
> (even if they are unseen during exporting).
> Maybe this is the reason.
>
> Regards,
> Radoslaw Lebkowski
>
> U¿ytkownik "Brian" <Brian@.discussions.microsoft.com> napisa³ w wiadomo¶ci
> news:632830EF-9C4F-4A1C-B8C9-672E327E95C4@.microsoft.com...
> > We have users experiencing very slow to export SQL Reporting Service 2005
> > rendered data to EXCEL. Is there any way to improve the performance?
> >
> > Brian
>
>|||By changing the export from EXCEL to PDF, It does not make any difference.
When I ran the SQL Web Reporting, it rendered very fast. Only when I need to
export the data to EXCEL and it is much slower.
Brian
"EMartinez" wrote:
> On Mar 9, 8:37 pm, Brian <B...@.discussions.microsoft.com> wrote:
> > We have users experiencing very slow to export SQL Reporting Service 2005
> > rendered data to EXCEL. Is there any way to improve the performance?
> >
> > Brian
> Usually this is due to either high activity on the web server that the
> reports are on -or- that the query or stored procedure sourcing the
> report needs to be revised to improve performance. I would suggest
> using the Database Engine Tuning Adviser against the stored procedure
> or query to implement indexes, etc to improve the performance. Hope
> this helps.
> Regards,
> Enrique Martinez
> Sr. SQL Server Developer
>|||On Mar 10, 11:25 am, Brian <B...@.discussions.microsoft.com> wrote:
> By changing the export from EXCEL to PDF, It does not make any difference.
> When I ran the SQL Web Reporting, it rendered very fast. Only when I need to
> export the data to EXCEL and it is much slower.
> Brian
> "EMartinez" wrote:
> > On Mar 9, 8:37 pm, Brian <B...@.discussions.microsoft.com> wrote:
> > > We have users experiencing very slow to export SQL Reporting Service 2005
> > > rendered data to EXCEL. Is there any way to improve the performance?
> > > Brian
> > Usually this is due to either high activity on the web server that the
> > reports are on -or- that the query or stored procedure sourcing the
> > report needs to be revised to improve performance. I would suggest
> > using the Database Engine Tuning Adviser against the stored procedure
> > or query to implement indexes, etc to improve the performance. Hope
> > this helps.
> > Regards,
> > Enrique Martinez
> > Sr. SQL Server Developer
If the image is large or there is a lot of report data to export, this
may be the reason. Have you tried the Database Engine Tuning Advisor
yet? I think that caching the report might improve the performance and
response time.
Regards,
Enrique Martinez
Sr. SQL Server Developer|||If you render previous executed reports to other output format, it doesn't
require regathering data from datasources.
Rendering process uses intermediate format of these reports stored in RS
cache.
Rendering to output format uses SQL Server only for Report Processing
Extensions (not for executing SQL queries from datasources).
Rendering reports to PDF or Excel are the slowest operations whereas
exporting to HTML and CSV are the fastests methods.
I've heard a lot of complaints for slow rendering to PDF and Excel. It's
very common situation.
To improve speed of rendering reports try to find server's bottlenecks.
Maybe it's a CPU or server memory.
Try to use SQL Server Profiler to measure CPU usage during rendering to
different formats.
I hope it will be helpful.
Radoslaw Lebkowski
U¿ytkownik "Brian" <Brian@.discussions.microsoft.com> napisa³ w wiadomo¶ci
news:5C8EF1BB-10C8-4468-B221-C75D18D9434C@.microsoft.com...
> Thank you for the quick response.
> The SQL Reporting 2005 report is a simple report which has no complex
> structure in it. It is a single line type of report. However, it has the
> company logo image on the title of the report. The report rendered within
> one minute with 123 pages. When I export to EXCEL, it was ten times
> slower
> then the web page rendered.
> Does export require SQL to query the data again or it gathered the
> rendered
> data to EXCEL?
> Would increase SQL memory from dynamic to static with 3GB help? How about
> caching the report?
> Thanks,
> Brian
>
> "Radoslaw Lebkowski" wrote:
>> Hello,
>> What about exporting to other formats like PDF or MHTML. Is it very slow
>> too?
>> How complicated are these reports and how much data do they contain?
>> Sometimes the reason of slow exporting to Excel is complex structure of
>> reports (a lot of cells, nested objects, etc.).
>> If reports contain a lot of hidden rows all of them are saving to Excel
>> file
>> (even if they are unseen during exporting).
>> Maybe this is the reason.
>>
>> Regards,
>> Radoslaw Lebkowski
>>
>> U?ytkownik "Brian" <Brian@.discussions.microsoft.com> napisa3 w wiadomo?ci
>> news:632830EF-9C4F-4A1C-B8C9-672E327E95C4@.microsoft.com...
>> > We have users experiencing very slow to export SQL Reporting Service
>> > 2005
>> > rendered data to EXCEL. Is there any way to improve the performance?
>> >
>> > Brian
>>|||If it is much data at all then what you should do is have your users export
via CSV. It will still open it up in Excel. One other point, however. The
default CSV format is Unicode which Excel doesn't know how to handle (at
least Excel 2003 and earlier can't handle, I don't know about 2007). In RS
2005 you can change a configuration setting that causing CSV exports to be
in ASCII. CSV and HTML rendering is about the same performance wise.
As a test just try it. Excel will (I believe) put all the data in a single
column and then you have to use the menu in Excel to split the data out into
multiple columns.
I am gone next week to the MVP Summit in Seattle. All the newsgroups will
see very little MVP involvement for the next week.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:5C8EF1BB-10C8-4468-B221-C75D18D9434C@.microsoft.com...
> Thank you for the quick response.
> The SQL Reporting 2005 report is a simple report which has no complex
> structure in it. It is a single line type of report. However, it has the
> company logo image on the title of the report. The report rendered within
> one minute with 123 pages. When I export to EXCEL, it was ten times
> slower
> then the web page rendered.
> Does export require SQL to query the data again or it gathered the
> rendered
> data to EXCEL?
> Would increase SQL memory from dynamic to static with 3GB help? How about
> caching the report?
> Thanks,
> Brian
>
> "Radoslaw Lebkowski" wrote:
>> Hello,
>> What about exporting to other formats like PDF or MHTML. Is it very slow
>> too?
>> How complicated are these reports and how much data do they contain?
>> Sometimes the reason of slow exporting to Excel is complex structure of
>> reports (a lot of cells, nested objects, etc.).
>> If reports contain a lot of hidden rows all of them are saving to Excel
>> file
>> (even if they are unseen during exporting).
>> Maybe this is the reason.
>>
>> Regards,
>> Radoslaw Lebkowski
>>
>> U¿ytkownik "Brian" <Brian@.discussions.microsoft.com> napisa³ w wiadomo¶ci
>> news:632830EF-9C4F-4A1C-B8C9-672E327E95C4@.microsoft.com...
>> > We have users experiencing very slow to export SQL Reporting Service
>> > 2005
>> > rendered data to EXCEL. Is there any way to improve the performance?
>> >
>> > Brian
>>|||Exporting to CSV helps and improve the export time. Let's hope Microsoft
will improve the export process to EXCEL in the future.
Thanks,
Brian
"Bruce L-C [MVP]" wrote:
> If it is much data at all then what you should do is have your users export
> via CSV. It will still open it up in Excel. One other point, however. The
> default CSV format is Unicode which Excel doesn't know how to handle (at
> least Excel 2003 and earlier can't handle, I don't know about 2007). In RS
> 2005 you can change a configuration setting that causing CSV exports to be
> in ASCII. CSV and HTML rendering is about the same performance wise.
> As a test just try it. Excel will (I believe) put all the data in a single
> column and then you have to use the menu in Excel to split the data out into
> multiple columns.
> I am gone next week to the MVP Summit in Seattle. All the newsgroups will
> see very little MVP involvement for the next week.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Brian" <Brian@.discussions.microsoft.com> wrote in message
> news:5C8EF1BB-10C8-4468-B221-C75D18D9434C@.microsoft.com...
> > Thank you for the quick response.
> >
> > The SQL Reporting 2005 report is a simple report which has no complex
> > structure in it. It is a single line type of report. However, it has the
> > company logo image on the title of the report. The report rendered within
> > one minute with 123 pages. When I export to EXCEL, it was ten times
> > slower
> > then the web page rendered.
> >
> > Does export require SQL to query the data again or it gathered the
> > rendered
> > data to EXCEL?
> >
> > Would increase SQL memory from dynamic to static with 3GB help? How about
> > caching the report?
> >
> > Thanks,
> > Brian
> >
> >
> >
> > "Radoslaw Lebkowski" wrote:
> >
> >> Hello,
> >> What about exporting to other formats like PDF or MHTML. Is it very slow
> >> too?
> >> How complicated are these reports and how much data do they contain?
> >> Sometimes the reason of slow exporting to Excel is complex structure of
> >> reports (a lot of cells, nested objects, etc.).
> >> If reports contain a lot of hidden rows all of them are saving to Excel
> >> file
> >> (even if they are unseen during exporting).
> >> Maybe this is the reason.
> >>
> >>
> >> Regards,
> >> Radoslaw Lebkowski
> >>
> >>
> >>
> >> U¿ytkownik "Brian" <Brian@.discussions.microsoft.com> napisa³ w wiadomo¶ci
> >> news:632830EF-9C4F-4A1C-B8C9-672E327E95C4@.microsoft.com...
> >> > We have users experiencing very slow to export SQL Reporting Service
> >> > 2005
> >> > rendered data to EXCEL. Is there any way to improve the performance?
> >> >
> >> > Brian
> >>
> >>
> >>
>
>
rendered data to EXCEL. Is there any way to improve the performance?
BrianOn Mar 9, 8:37 pm, Brian <B...@.discussions.microsoft.com> wrote:
> We have users experiencing very slow to export SQL Reporting Service 2005
> rendered data to EXCEL. Is there any way to improve the performance?
> Brian
Usually this is due to either high activity on the web server that the
reports are on -or- that the query or stored procedure sourcing the
report needs to be revised to improve performance. I would suggest
using the Database Engine Tuning Adviser against the stored procedure
or query to implement indexes, etc to improve the performance. Hope
this helps.
Regards,
Enrique Martinez
Sr. SQL Server Developer|||Hello,
What about exporting to other formats like PDF or MHTML. Is it very slow
too?
How complicated are these reports and how much data do they contain?
Sometimes the reason of slow exporting to Excel is complex structure of
reports (a lot of cells, nested objects, etc.).
If reports contain a lot of hidden rows all of them are saving to Excel file
(even if they are unseen during exporting).
Maybe this is the reason.
Regards,
Radoslaw Lebkowski
U¿ytkownik "Brian" <Brian@.discussions.microsoft.com> napisa³ w wiadomo¶ci
news:632830EF-9C4F-4A1C-B8C9-672E327E95C4@.microsoft.com...
> We have users experiencing very slow to export SQL Reporting Service 2005
> rendered data to EXCEL. Is there any way to improve the performance?
> Brian|||Thank you for the quick response.
The SQL Reporting 2005 report is a simple report which has no complex
structure in it. It is a single line type of report. However, it has the
company logo image on the title of the report. The report rendered within
one minute with 123 pages. When I export to EXCEL, it was ten times slower
then the web page rendered.
Does export require SQL to query the data again or it gathered the rendered
data to EXCEL?
Would increase SQL memory from dynamic to static with 3GB help? How about
caching the report?
Thanks,
Brian
"Radoslaw Lebkowski" wrote:
> Hello,
> What about exporting to other formats like PDF or MHTML. Is it very slow
> too?
> How complicated are these reports and how much data do they contain?
> Sometimes the reason of slow exporting to Excel is complex structure of
> reports (a lot of cells, nested objects, etc.).
> If reports contain a lot of hidden rows all of them are saving to Excel file
> (even if they are unseen during exporting).
> Maybe this is the reason.
>
> Regards,
> Radoslaw Lebkowski
>
> U¿ytkownik "Brian" <Brian@.discussions.microsoft.com> napisa³ w wiadomo¶ci
> news:632830EF-9C4F-4A1C-B8C9-672E327E95C4@.microsoft.com...
> > We have users experiencing very slow to export SQL Reporting Service 2005
> > rendered data to EXCEL. Is there any way to improve the performance?
> >
> > Brian
>
>|||By changing the export from EXCEL to PDF, It does not make any difference.
When I ran the SQL Web Reporting, it rendered very fast. Only when I need to
export the data to EXCEL and it is much slower.
Brian
"EMartinez" wrote:
> On Mar 9, 8:37 pm, Brian <B...@.discussions.microsoft.com> wrote:
> > We have users experiencing very slow to export SQL Reporting Service 2005
> > rendered data to EXCEL. Is there any way to improve the performance?
> >
> > Brian
> Usually this is due to either high activity on the web server that the
> reports are on -or- that the query or stored procedure sourcing the
> report needs to be revised to improve performance. I would suggest
> using the Database Engine Tuning Adviser against the stored procedure
> or query to implement indexes, etc to improve the performance. Hope
> this helps.
> Regards,
> Enrique Martinez
> Sr. SQL Server Developer
>|||On Mar 10, 11:25 am, Brian <B...@.discussions.microsoft.com> wrote:
> By changing the export from EXCEL to PDF, It does not make any difference.
> When I ran the SQL Web Reporting, it rendered very fast. Only when I need to
> export the data to EXCEL and it is much slower.
> Brian
> "EMartinez" wrote:
> > On Mar 9, 8:37 pm, Brian <B...@.discussions.microsoft.com> wrote:
> > > We have users experiencing very slow to export SQL Reporting Service 2005
> > > rendered data to EXCEL. Is there any way to improve the performance?
> > > Brian
> > Usually this is due to either high activity on the web server that the
> > reports are on -or- that the query or stored procedure sourcing the
> > report needs to be revised to improve performance. I would suggest
> > using the Database Engine Tuning Adviser against the stored procedure
> > or query to implement indexes, etc to improve the performance. Hope
> > this helps.
> > Regards,
> > Enrique Martinez
> > Sr. SQL Server Developer
If the image is large or there is a lot of report data to export, this
may be the reason. Have you tried the Database Engine Tuning Advisor
yet? I think that caching the report might improve the performance and
response time.
Regards,
Enrique Martinez
Sr. SQL Server Developer|||If you render previous executed reports to other output format, it doesn't
require regathering data from datasources.
Rendering process uses intermediate format of these reports stored in RS
cache.
Rendering to output format uses SQL Server only for Report Processing
Extensions (not for executing SQL queries from datasources).
Rendering reports to PDF or Excel are the slowest operations whereas
exporting to HTML and CSV are the fastests methods.
I've heard a lot of complaints for slow rendering to PDF and Excel. It's
very common situation.
To improve speed of rendering reports try to find server's bottlenecks.
Maybe it's a CPU or server memory.
Try to use SQL Server Profiler to measure CPU usage during rendering to
different formats.
I hope it will be helpful.
Radoslaw Lebkowski
U¿ytkownik "Brian" <Brian@.discussions.microsoft.com> napisa³ w wiadomo¶ci
news:5C8EF1BB-10C8-4468-B221-C75D18D9434C@.microsoft.com...
> Thank you for the quick response.
> The SQL Reporting 2005 report is a simple report which has no complex
> structure in it. It is a single line type of report. However, it has the
> company logo image on the title of the report. The report rendered within
> one minute with 123 pages. When I export to EXCEL, it was ten times
> slower
> then the web page rendered.
> Does export require SQL to query the data again or it gathered the
> rendered
> data to EXCEL?
> Would increase SQL memory from dynamic to static with 3GB help? How about
> caching the report?
> Thanks,
> Brian
>
> "Radoslaw Lebkowski" wrote:
>> Hello,
>> What about exporting to other formats like PDF or MHTML. Is it very slow
>> too?
>> How complicated are these reports and how much data do they contain?
>> Sometimes the reason of slow exporting to Excel is complex structure of
>> reports (a lot of cells, nested objects, etc.).
>> If reports contain a lot of hidden rows all of them are saving to Excel
>> file
>> (even if they are unseen during exporting).
>> Maybe this is the reason.
>>
>> Regards,
>> Radoslaw Lebkowski
>>
>> U?ytkownik "Brian" <Brian@.discussions.microsoft.com> napisa3 w wiadomo?ci
>> news:632830EF-9C4F-4A1C-B8C9-672E327E95C4@.microsoft.com...
>> > We have users experiencing very slow to export SQL Reporting Service
>> > 2005
>> > rendered data to EXCEL. Is there any way to improve the performance?
>> >
>> > Brian
>>|||If it is much data at all then what you should do is have your users export
via CSV. It will still open it up in Excel. One other point, however. The
default CSV format is Unicode which Excel doesn't know how to handle (at
least Excel 2003 and earlier can't handle, I don't know about 2007). In RS
2005 you can change a configuration setting that causing CSV exports to be
in ASCII. CSV and HTML rendering is about the same performance wise.
As a test just try it. Excel will (I believe) put all the data in a single
column and then you have to use the menu in Excel to split the data out into
multiple columns.
I am gone next week to the MVP Summit in Seattle. All the newsgroups will
see very little MVP involvement for the next week.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:5C8EF1BB-10C8-4468-B221-C75D18D9434C@.microsoft.com...
> Thank you for the quick response.
> The SQL Reporting 2005 report is a simple report which has no complex
> structure in it. It is a single line type of report. However, it has the
> company logo image on the title of the report. The report rendered within
> one minute with 123 pages. When I export to EXCEL, it was ten times
> slower
> then the web page rendered.
> Does export require SQL to query the data again or it gathered the
> rendered
> data to EXCEL?
> Would increase SQL memory from dynamic to static with 3GB help? How about
> caching the report?
> Thanks,
> Brian
>
> "Radoslaw Lebkowski" wrote:
>> Hello,
>> What about exporting to other formats like PDF or MHTML. Is it very slow
>> too?
>> How complicated are these reports and how much data do they contain?
>> Sometimes the reason of slow exporting to Excel is complex structure of
>> reports (a lot of cells, nested objects, etc.).
>> If reports contain a lot of hidden rows all of them are saving to Excel
>> file
>> (even if they are unseen during exporting).
>> Maybe this is the reason.
>>
>> Regards,
>> Radoslaw Lebkowski
>>
>> U¿ytkownik "Brian" <Brian@.discussions.microsoft.com> napisa³ w wiadomo¶ci
>> news:632830EF-9C4F-4A1C-B8C9-672E327E95C4@.microsoft.com...
>> > We have users experiencing very slow to export SQL Reporting Service
>> > 2005
>> > rendered data to EXCEL. Is there any way to improve the performance?
>> >
>> > Brian
>>|||Exporting to CSV helps and improve the export time. Let's hope Microsoft
will improve the export process to EXCEL in the future.
Thanks,
Brian
"Bruce L-C [MVP]" wrote:
> If it is much data at all then what you should do is have your users export
> via CSV. It will still open it up in Excel. One other point, however. The
> default CSV format is Unicode which Excel doesn't know how to handle (at
> least Excel 2003 and earlier can't handle, I don't know about 2007). In RS
> 2005 you can change a configuration setting that causing CSV exports to be
> in ASCII. CSV and HTML rendering is about the same performance wise.
> As a test just try it. Excel will (I believe) put all the data in a single
> column and then you have to use the menu in Excel to split the data out into
> multiple columns.
> I am gone next week to the MVP Summit in Seattle. All the newsgroups will
> see very little MVP involvement for the next week.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Brian" <Brian@.discussions.microsoft.com> wrote in message
> news:5C8EF1BB-10C8-4468-B221-C75D18D9434C@.microsoft.com...
> > Thank you for the quick response.
> >
> > The SQL Reporting 2005 report is a simple report which has no complex
> > structure in it. It is a single line type of report. However, it has the
> > company logo image on the title of the report. The report rendered within
> > one minute with 123 pages. When I export to EXCEL, it was ten times
> > slower
> > then the web page rendered.
> >
> > Does export require SQL to query the data again or it gathered the
> > rendered
> > data to EXCEL?
> >
> > Would increase SQL memory from dynamic to static with 3GB help? How about
> > caching the report?
> >
> > Thanks,
> > Brian
> >
> >
> >
> > "Radoslaw Lebkowski" wrote:
> >
> >> Hello,
> >> What about exporting to other formats like PDF or MHTML. Is it very slow
> >> too?
> >> How complicated are these reports and how much data do they contain?
> >> Sometimes the reason of slow exporting to Excel is complex structure of
> >> reports (a lot of cells, nested objects, etc.).
> >> If reports contain a lot of hidden rows all of them are saving to Excel
> >> file
> >> (even if they are unseen during exporting).
> >> Maybe this is the reason.
> >>
> >>
> >> Regards,
> >> Radoslaw Lebkowski
> >>
> >>
> >>
> >> U¿ytkownik "Brian" <Brian@.discussions.microsoft.com> napisa³ w wiadomo¶ci
> >> news:632830EF-9C4F-4A1C-B8C9-672E327E95C4@.microsoft.com...
> >> > We have users experiencing very slow to export SQL Reporting Service
> >> > 2005
> >> > rendered data to EXCEL. Is there any way to improve the performance?
> >> >
> >> > Brian
> >>
> >>
> >>
>
>
Subscribe to:
Posts (Atom)