Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
OK, I know it can be done, I do it quite often, but why so difficult to do a loop in T-SQL? I can think of a ton of reasons I’d want to parse thru a query result set and do something that simply can’t be done without a loop, yet the code to setup and execute my loop is > 20 lines.
I’m sure others have a similar opinions so why are we still without a simple way to perform a loop?
An aside: we finally got an UPSERT (aka MERGE) in SQL2008 so maybe all hope isn’t lost.
SQL is a set-based, declarative language; not a procedural or imperative language. T-SQL tries to straddle the two, but it’s still built on a fundamentally set-based paradigm.