Posted by Erland Sommarskog on 10/20/05 00:58

(wxbuff@aol.com) writes:
> The next level of breakdown is by product. That is where I used my
> phrase 'parsing' - I have a cursor that reads the products for which
> incidents were opened during the specified period and a table is
> created summarizing the work done for each product.
>
> As I sit here, I realize that there are efficiencies to be gained
> (maybe? - I am still a novice) by using 'group by' etc... but I was
> specfically asked to create a report that showed discrete tables for
> each product. Hence the cursor.

So that's tables in the report, not database tables?

Well, a good reporting tool should be able to produce several tables
from one result set.


--
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

• Next in forum: Re: Problem with simple cursor
• Prev in forum: Re: Using "SELECT * " is a bad practice even when using a VIEW instead of a table?
• Thread view: Re: Identifying results sets when stored procedure called multiple times

[Reply to this message]