Answer by David 1
One of the motivations of E.F.Codd when he first proposed the Relational Model of data was to devise a system that didn't require the looping, branching and step-at-a-time processing used in imperative...
View ArticleAnswer by Matt Whitfield
The best analogy I have seen comes from Jeff Moden's signature on the main site. And that is that with procedural code you are probably thinking about what you want to do to a row. With set-based code...
View ArticleAnswer by Rob Farley
My preference for explaining this question comes down to the paradigm that database systems employ. When you really get into it, a database system runs on a computer, and eventually works things out...
View ArticleAnswer by Tom Staab
A procedural approach follows the paradigm of traditional languages used for applications. You perform a function then call another function and so on. When this method is used to retrieve data from a...
View ArticleAnswer by sbhollis
I landed here while trying to find something that described when it is not appropriate to use a set based language to solve a problem. Or in other words what types of algorithms don't lend themselves...
View ArticleAnswer by Magnus Ahlkvist
One little addition from me: We have many, many stored procedures which use cursors. Sure - some of them could probably be replaced by a set based approach. Some of them definitely by...
View ArticleAnswer by GPO
Although the discussion here has focussed on cursors to a large extent, my pet hate is scalar functions in SELECT statements, where the scalar functions contain (and very effectively hide) SELECT...
View ArticleAnswer by danlatimer
This isn't a complicated question and does not require a complicated answer: **Short Answer:** Databases are most efficient when you tell them what you want and let them figure out the most efficient...
View ArticleAnswer by David 1
One of the motivations of E.F.Codd when he first proposed the Relational Model of data was to devise a system that didn't require the looping, branching and step-at-a-time processing used in imperative...
View ArticleAnswer by Matt Whitfield
The best analogy I have seen comes from Jeff Moden's signature on the main site. And that is that with procedural code you are probably thinking about what you want to do to a row. With set-based code...
View ArticleAnswer by Rob Farley
My preference for explaining this question comes down to the paradigm that database systems employ.When you really get into it, a database system runs on a computer, and eventually works things out...
View ArticleAnswer by Tom Staab
A procedural approach follows the paradigm of traditional languages used for applications. You perform a function then call another function and so on. When this method is used to retrieve data from a...
View ArticleAnswer by sbhollis
I landed here while trying to find something that described when it is not appropriate to use a set based language to solve a problem. Or in other words what types of algorithms don't lend themselves...
View ArticleAnswer by Magnus Ahlkvist
One little addition from me: We have many, many stored procedures which use cursors. Sure - some of them could probably be replaced by a set based approach. Some of them definitely by...
View ArticleAnswer by GPO
Although the discussion here has focussed on cursors to a large extent, my pet hate is scalar functions in SELECT statements, where the scalar functions contain (and very effectively hide) SELECT...
View ArticleAnswer by danlatimer
This isn't a complicated question and does not require a complicated answer: **Short Answer:** Databases are most efficient when you tell them what you want and let them figure out the most efficient...
View Article
