Milan Negovan has written an article to provide an in-depth perspective on the ViewState mechanism. In his article, he suggested some do’s and dont’s on using ViewState, for example, how by simply disabling the ViewState of the entire page can greatly enhance the performance of the page if you just need to display a DataGrid on the page with no PostBack.
URL: ASP.NET State Management: View State
I have seen multiple times that developers keep EnableViewState true as default even if they simply have to display a single page report for example. As most of the reports are basically rendered using DataGrid, this control generates a huge amount of stuff for ViewState.
Alternatively, you can also think of storing the ViewState of the page on the server. How? Milan has the answer of this question as well in his article.
Firoz Ansari 
Thank you, Firoz. I wrote some more about the pros and cons of storing view state in the database in my yesterday’s post: http://www.aspnetresources.com/blog/page_state_persisters_overview.aspx
LikeLike