Welcome to the New Year everyone! After debating with myself and talking to a few colleagues/peers over the last few weeks, I’ve decided that I have gotten away from my original sense of purpose for this blog. It’s time to fix that!
My original idea was to have this blog be a place where people could come to learn about SQL. Be it learning syntax, or what functionality is available, or even why things exist – it’s always good to know what’s out there. Especially, if you just don’t know. So, that’s what I’m going back to doing.
One idea that really got me to thinking was the idea of what we mean with a stored procedure. According to TechTarget, a stored procedure is “a set of SQL statements with an assigned name, which are stored in a relational database management system as a group so it can be reused and shared by multiple programs.”
Hopefully, you’ve had a chance to read my past blog posts on SQL statements. If not, you can refresh your memory in the following posts:
Now, using the SQL statements learned in those posts, you can make a stored procedure. Just give it a name and Boom! Bob’s your Uncle!
In our next blog post – which I promise will happen way sooner than they have in the past – we’ll go over why you should create stored procedures and what their benefits are. Until then!