Skip to main content

SQL Journey: Blog #16



In this lesson, we will look at stored procedures and how it makes the job of querying to a database more efficient. Imagine that  a person is not that well-versed in creating SQL queries but this person needs information from the database to make informed decisions relating to his job. Well, fret not. For another geeky nerdy expert person could make the query for that person and all he has to do is to write a string of code that is not as lengthy as the stored procedure.

In this case, let's say we want to know the average salary of a salesman from a company database. But we are not that well-versed with SQL. What our database developer or administrator can do is to create a stored procedure that will automate the retrieval of such information.

In the database developer or administrators eyes, this is what he sees:


Next, the developer / administrator will modify the stored procedure.


We do the following modifications to the stored procedure:


Now, the administrator of the database can inform us to use the following code:


And, this will be the result.


Here's the catch of a stored procedure:
Any update to a stored procedure will be updated for all users of that stored procedure. It is more efficient since we no longer have to write long strings of code for something that is commonly being retrieved by a number of non-programming users of the database. How much more if we can couple this stored procedure that will let us input the Jobtitle in a textbox and then press a button to show the resulting table. In this case, we now have a user interface and on that interface, non-programming users can better navigate and retrieve data from the database. That's just my imagination kicking in.

Update on the touch typing journey:

I have done two lessons today and in writing this blog, I painstakingly applied what I have learned so far. I am still quite slow at 27 words per minute. I figured it would be better to apply what I have learned in my daily task so that the habit of using the appropriate finger to a given letter can be developed.


Comments

Popular posts from this blog

Privacy Policy of ShinStats: descriptives calc

Privacy Policy Shin Nix built the ShinStats app as an Ad Supported app. This SERVICE is provided by Shin Nix at no cost and is intended for use as is. This page is used to inform visitors regarding my policies with the collection, use, and disclosure of Personal Information if anyone decided to use my Service. If you choose to use my Service, then you agree to the collection and use of information in relation to this policy. The Personal Information that I collect is used for providing and improving the Service. I will not use or share your information with anyone except as described in this Privacy Policy. The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which are accessible at ShinStats unless otherwise defined in this Privacy Policy. Information Collection and Use For a better experience, while using our Service, I may require you to provide us with certain personally identifiable information. The information that I request will be retaine...

SQL Journey: Blog#10

So far, we are only "reading" from a given database or table using the SELECT command of SQL. In today's lesson, we will now start "writing" into a given database using the UPDATE and DELETE commands. Challenge: Dynamic Documents Given data: CREATE table documents (     id INTEGER PRIMARY KEY AUTOINCREMENT,     title TEXT,     content TEXT,     author TEXT);      INSERT INTO documents (author, title, content)     VALUES ("Puff T.M. Dragon", "Fancy Stuff", "Ceiling wax, dragon wings, etc."); INSERT INTO documents (author, title, content)     VALUES ("Puff T.M. Dragon", "Living Things", "They're located in the left ear, you know."); INSERT INTO documents (author, title, content)     VALUES ("Jackie Paper", "Pirate Recipes", "Cherry pie, apple pie, blueberry pie."); INSERT INTO documents (author, title, content)     VALUES ("Jackie Paper", "Boat Supplies...

SQL Journey: Blog #14

I am now on what Alex the Analyst would call the advanced SQL queries. First off, the Common Table Expression or CTEs. Based on what I understood in the video, CTEs is similar to a function or class in Python which you can call out. It is just how I felt when I first encountered this expression. Now, in this particular case, I tried to replicate what Alex is doing but also not copying the codes that he is using. I am just simply trying to understand what the expression that was used (which starts with WITH) and then observe how he used the said expression. This was my code. Now this code, resulted in the following error. Msg 8156, Level 16, State 1, Line 84 The column 'EmployeeID' was specified multiple times for 'CTE_Employee'. What does someone do in this day and age if we encounter something that bogs us down? We go to the internet especially to AI tools to aid us out. And, apparently, these tools will really come in handy. It stated that the error occurred because I...