SQL Server: when it's neccessary to use functions/procedures and not queries?

Question

I started to learn functions and stored procedures in Microsoft SQL Server and noticed that everything that they do also can be done with a queries. I'm sure, they exist for a reason, so I'd like to ask:

What can be done using functions / procedures that's impossible to do with a query?
In which cases one should use procedures/functions and not queries?

marc_s · Accepted Answer · 2015-12-05 08:30:16Z

4

There's nothing magic about functions or procedures - there's nothing you cannot do in an ad-hoc query as well.

They can be used to reuse some code - write the function once and use it everywhere, instead of writing the same T-SQL code over and over and over again.

And they can be used to combine code that belongs together (like withdraw amount x from account #1 and deposit it into account #2) into a single, reusable procedure which can also handle transactions internally.

So basically: nothing magic - but using functions and procedures (like in any other programming language) can help reuse and centralize some code, and make your life easier

answered Dec 5, 2015 at 8:30

marc_s

760k186 gold badges1.4k silver badges1.5k bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

SQL Server: when it's neccessary to use functions/procedures and not queries?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related