Posted by Erland Sommarskog on 06/07/05 02:09

SQLJunkie (vsinha73@gmail.com) writes:
> This is an automated report that runs on a monthly basis so there is no
> front end to it. I was hoping to run the SP from a dotnet app and then
> export the data to excel and email results. We may also decide to
> display the results on a webpage too - so fast execution of the SP is
> critical also.

If fast execution is critical, you should definitely take the rowset
without thrills from SQL Server, and then transpose it your .Net client.
C#/VB is much better fitted for such operations than SQL Server.

Or, hey, import the data into Excel as is, and have Excel do the
crosstab. A poster here recently claimed that Excel was the best tool
in town for pivots. (I have done pivots myself in Excel though.) Excel
has an OLE interface, but I would expect standard routines being
available to manipulate Excel books from .Net.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

[Back to original message]