You might think that it would be easy to find a well documented solution for programmatically genereating an Excel Workbook that could be sent as an e-mail attachement from an ASP.NET website. Surprisingly, a reasonable and simple solution to this request proved to be elusive. Recently, a client requested to have ASP.NET 2.0 GridView data exported to an Excel spreadsheet format and then sent as an e-mail attachment from their website. This will mark the object for recompilation which will generate a new query plan the next time that the stored procedure is executed. In many cases, you can merely mark the stored procedure for recompilation by doing running 'sp_recompile'. If it runs considerably faster than when you try the same call from your web app, try adding the following line before you execute the stored proc:īy doing this, you will now be executing your stored procedure using the same query plan as your external code (so if it was running slow from ADO.NET, it should be running slow here as well now).

To see if you are experiencing this, open up an instance of SSMS and try executing the stored procedure in question. Unfortunately, under those conditions, the SQL Server query plan compiled when the stored proc was created can grow sluggish in a changing environment. The system has been in use for years and has experienced its fair share of code evolution. Have you ever encountered slow execution time when calling a SQL Server stored procedure from your web application only to find that it zips right along if you execute it from within SQL Server Management Studio? I ran into this problem recently when working on one of my client's web applications that I had developed using ADO.NET.

Flash actionscript 3.0 tryparse