How The SQL Basics Equal Performance

by Ermie C
This article is very informative of how to improve performance on how to use SQL server. The main thing that is presented is poorly coded SQL statements is how databases are slowed down and efficiency is not maximized. Although, it is impossible to create the perfect statements there are many ways to create an easier database structure. With all elements of doing a skill, the things people forget that are the most critical part of a skill are the basics. When people have the basics down, then implementation of new ideas and skills for databases can be easily created. The main types of code that is used in the basics of SQL are “WHERE”, “SELECT”, and “FROM”. These create the foundation of how certain types of information is organized and selected within a database. However, following the rules is the main purpose of why this article was written. To improved the performance of a database, is to start thinking in a relational manner. This means that when implementing a database, it must been seen as comparing tables of data as if they were files. To be able to filter and choose the types of data that must be extracted for use in the business world. There are also mistakes made in the SQL world. The author states that SQL statementes shouldn’t be “asking for what you already know” (Mullins). I believe this means that finding data shouldn’t be hard coded at tailored for a specific piece of data, but to create a SQL statement that could be used for any part of the data. Finally, the author encourages continuous updates on the database. We can all agree that databases are only good for the content they hold and its integrity. Following the rules and simplifying SQL statements will make the life expectancy of a database longer and more efficient, but if these rules are not met, then what is the purpose of having an efficient database without performance.

I found this article to be very interesting because it really states that understanding the basics of SQL or anything is the first step of understanding and applying a new skill. Without the basics, how is it possible to achieve the highest output of a product. SQL seems to be more effective than meets the eye and that it should be used in a certain way. I think this has a lot to do with the class because this is mostly an introduction to many of the students. If we do shortcuts and not understand how to make an effective database and create effective SQL statements the right way, then being hired for a job that deals with SQL will become very difficult for all of us.

My experience with SQL has only been a little bit, because I’ve only seen it coded. I’ve wanted to go to an internship and find out how it is implemented, but all I have heard are stories of how it is heavily implemented with businesses that have many accounts with different types of information. This is because I have looked at some of the opportunities that have been presented from broncoconnection at Cal Poly Pomona. Many job offers require SQL and I have not really dabbled in it. So, hopefully after this quarter, I could widen the spectrum of my job search and knowledge.

Note:

There are actually many videos and websites that can get a person started in SQL. Here is website of how to get an introduction to SQL.

http://sqlserver2008tutorial.com/sql-tutorials.html

Reference:

Mullins, C. (2010). Sql performance basics. Database Trends and Applications V. 24 No. 4 (December 2010) P. 29, 24(4), 29.

Kash Data Consulting, LLC. (2011). SQL Server 2008 Tutorial.com. Retrieved from http://http://sqlserver2008tutorial.com/sql-tutorials.html

2 thoughts on “How The SQL Basics Equal Performance”

  1. I like how this article stresses about fundamentals and the importance of the basics. I’m a firm believer of learning the fundamentals of everything. I’m hoping that I will learn the fundamentals and basics of SQL in this class so that in the future and can build upon them.

  2. I agree that it is important for us to know the basics the right way and build the corrrect skills in the first place rather than trying to take shortcuts and end up coding poorly in the long run. It will save us tons of headaches in the future and this applies to most things in life as well. Great article.

Comments are closed.