I searched in google..! and found this try it may help..!
Installation folder may be different from MSSQL.1, can be MSSQL.2 or MSSQL.3 (search for rsreportserver.config under Program Files\Microsoft SQL Server if not found)
Here are the more detailed steps for Disabling Excel Export Option in Reporting Services -
1. Go to Database server where reporting services is installed, open the rsreportserver.config file located at -<Drive Letter>:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer2. Go to <Configuration> <Render> section.
3. Change this entry <Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering"/>to<Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering" Visible="false" />i.e. add Visible="false" for Excel rendering extension, or you can comment this line too.
Why Do Some People Forget To Mark as Answer .If It Helps.
I have created a page that stores a DataSet in a session variable and remove the session variable once the user navigates away from it. There are about 5 grids each with about 4 columns and 3-4 rows and two Developer Express comboboxes which I could see from the view source writing a lot of scripts. I have them all put inside an update panel. The problem is the page is taking too much time b/w postbacks(async).
The yslow shows the following in F grade:
-Make Fewer HTTP requests
-Use a content Delivery Network
-Add Expires headers
-Configure entity tags.
These two D grades:
-Configure entity tags.
This one in E grade:
-Reduce the number of DOM elements.
My browser is IE 7. To my surprise the page is pretty faster in the latest version of FireFox.
I have created a page that stores a DataSet in a session variable and remove the session variable once the user navigates away from it.
Sounds dumb to me.
To my surprise the page is pretty faster in the latest version of FireFox.
No surprises there.
I would check to see how long your database calls take, I would check to see how the update panel performs ( fast AJAX means writing your own code, the ASP.NET library is far from efficient ), and I'd check to see what I was databinding if I don't need to. I'd also check viewstate size to see if I'm posting a massive page every time. You could have the data from your dataset in viewstate, and have it stored in the session as well.
Driven to the arms of OSX by Vista.
Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Thank you Christian
I am actually updating the dataset to the Data base before removing (trying to reduce the Database hits). Updates are done directly on this dataset and then used for adaptor.update(). The dataset is kept in a session variable b/w postbacks. Do you find anything wrong with this approach?
Yes there are lots of things that improves performance of your page. Writing Dataset to Session variable is really not good. Remove viewState by using EnableViewState ="false" if you are not using it. this would reduce the page size by a lot.
Reduce the number of DOM elements means reducing large no of hiddenfield, Tables, Divs, etc. Just reduce them and apply CSS to position it perfectly.