Can I Loop Through A Table Variable In T-SQL?


Answer :

Add an identity to your table variable, and do an easy loop from 1 to the @@ROWCOUNT of the INSERT-SELECT.

Try this:

DECLARE @RowsToProcess  int DECLARE @CurrentRow     int DECLARE @SelectCol1     int  DECLARE @table1 TABLE (RowID int not null primary key identity(1,1), col1 int )   INSERT into @table1 (col1) SELECT col1 FROM table2 SET @RowsToProcess=@@ROWCOUNT  SET @CurrentRow=0 WHILE @CurrentRow<@RowsToProcess BEGIN     SET @CurrentRow=@CurrentRow+1     SELECT          @SelectCol1=col1         FROM @table1         WHERE RowID=@CurrentRow      --do your thing here--  END 

DECLARE @table1 TABLE (     idx int identity(1,1),     col1 int )  DECLARE @counter int  SET @counter = 1  WHILE(@counter < SELECT MAX(idx) FROM @table1) BEGIN     DECLARE @colVar INT      SELECT @colVar = col1 FROM @table1 WHERE idx = @counter      -- Do your work here      SET @counter = @counter + 1 END

Believe it or not, this is actually more efficient and performant than using a cursor.


My two cents.. From KM.'s answer, if you want to drop one variable, you can do a countdown on @RowsToProcess instead of counting up.

DECLARE @RowsToProcess  int;  DECLARE @table1 TABLE (RowID int not null primary key identity(1,1), col1 int )   INSERT into @table1 (col1) SELECT col1 FROM table2 SET @RowsToProcess = @@ROWCOUNT   WHILE @RowsToProcess > 0 -- Countdown BEGIN     SELECT *         FROM @table1         WHERE RowID=@RowsToProcess      --do your thing here--      SET @RowsToProcess = @RowsToProcess - 1; -- Countdown END

Comments

Post a Comment

Popular posts from this blog

Are Regular VACUUM ANALYZE Still Recommended Under 9.1?

Answer : VACUUM is only needed on updated or deleted rows in non-temporary tables. Obviously you're doing lots of INSERTs but it's not obvious from the description that you're also doing lots of UPDATEs or DELETEs. These operations can be tracked with the pg_stat_all_tables view, specifically the n_tup_upd and n_tup_del columns. Also, even more to the point, there is a n_dead_tup column that tells, per table, how much rows need to be vacuumed. (see Monitoring statistics in the doc for functions and views related to statistics gathering). A possible strategy in your case would be to suppress the scheduled VACUUM, keeping an eye on this view and checking on which tables the n_dead_tup is going up significantly. Then apply the aggressive VACUUM to these tables only. This will be a win if there are large tables whose rows never get deleted nor updated and the aggressive VACUUM is really necessary only on smaller tables. But keep running the ANALYZE for the optimiz
Read more

Can Feynman Diagrams Be Used To Represent Any Perturbation Theory?

Answer : Diagram machinery works also for perturbation theory in classical statistical mechanics and classical field theories. Generally, various kinds of diagrams constitute a pictorial way of talking about tensor products and their contractions while hiding the multi-linear algebra from the layman. In the simplest case, vertices (or blobs) represent vectors, matrices, tensors; vertices have ingoing and/or outgoing ports; ingoing ports denote (contravariant) ro indices; outgoing ports denote (covariant) co indices; directed arcs between blobs give a pair of equal indices summed over; different base spaces ⇔ \Leftrightarrow ⇔ different arc types; symmetric tensors ⇔ \Leftrightarrow ⇔ undirected diagrams; no labels are needed for internal lines. In many cases, the directed arcs are decorated (as thin, thick, broken,wavy, curly lines), each decoration indicating the presence of a so-called propagator, a function of its label to use as a weight in the sum, which may beco
Read more