|
|
Posted by bubbles on 04/03/07 00:56
Thank you for your reply.
The tables are in fact seperated by products, as each set of product-
specific data are handled by
different engineers. These sets of data need to be sliced and diced
into various analyses, and the
engineers would also need to dive into raw data for some of their
work.
Because these product-specific data sets are large (several million
records each), I thought that
perprocessing and seperating them into their respective tables would
help the engineers access
their analyses and data faster.
In any case, I have already done the needful and have had the required
tables generated.
Thanks!
Bubbles
On Mar 31, 5:33 am, Erland Sommarskog <esq...@sommarskog.se> wrote:
>
> If the table indeed have different layout depending on product, you
> would indeed have to loop, for instance using a cursor as you discovered.
> But if all sets of tables have the same layout, you should probably have
> one single set of tables instead, and in this case there would not be any
> need for loops.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|