Learn more about SQL Server tools

mssqltips logo
 

Tutorials          DBA          Dev          BI          Career          Categories          Webcasts          Whitepapers          Today's Tip          Join

Tutorials      DBA      Dev      BI      Categories      Webcasts

DBA    Dev    BI    Categories

 

What is SQL Server


By:   |   Last Updated: 2010-02-23   |   Comments (10)   |   Related Tips: More > Professional Development Career Planning

Problem

I am new to SQL Server and I have heard the term used in a number of different capacities and in different contexts. So what exactly is it? What are the common components? How does it work? How do people use it? I am brand new to the technology, where do I get started?

Solution

SQL Server originally was a relational database engine. Over time it has grown to include a number of new technologies. SQL Server 2008 is the current version and it consists of the following components:

With this basic set of products outlined, let's try to outline what SQL Server is used for and who uses it, at a high level. SQL Server is a large suite of products, so this tip will try to cover the basic concepts with URL's for additional information. This tip is intended to serve as a stepping stone to learn SQL Server.

Relational Engine

The relational engine is most often referred to as 'SQL Server' in most DBA, Developer, IT and Business circles. At a high level, SQL Server is installed on a Windows Server. SQL Server is managed by a set of services which can be started, stopped, paused or disabled. The two main services are the SQL Server service and SQL Server Agent.

The SQL Server service is the main service and it is responsible high level items like: databases, security, replication, etc. The key item to cover is the concept of the database. In many respects a database is a logical concept. In general you have two types of databases. First, are system databases that are from Microsoft and used to manage SQL Server. Second, are user defined databases that a DBA would build to support an application need by a business.

The database is made up of tables, code, indexes, security, etc. The tables have rows and columns storing the data. The most common coding objects are stored procedures, views, functions, referential integrity, triggers, etc. Indexes are built on tables to improve the access to the data. Security is established to prevent access to data and/or execute particular commands.

On to the physical side of the database. Databases typically have 2 files when they are built. First, is the database file which typically has an extension of MDF. All of the items (i.e. table, view, stored procedure, etc.) associated with the database are stored in database i.e. *.MDF file. Second is the transaction log file which typically has an extension of LDF. At a high level, the transaction log is responsible for storing versions of the data before and after the changes in order to maintain the data integrity.

This explanation is intentionally at a high level because SQL Server is such a large product, but we would be remiss not to include additional key components of the relational engine:

  • Backup and Recovery - Ability to issue backups and restores of the databases
  • Full Text Search - Ability to issue a catalog to improve complex free form querying
  • Service Broker - Queuing based technology internal to the database engine
  • Database mirroring - High availability tool to maintain multiple copies of a complete database
  • Replication - Ability to replicate a portion of a database to multiple SQL Servers
  • Maintenance - Ability to rebuild indexes, statistics, etc. in order to improve data access and performance

SQL Server Agent

SQL Server Agent is the second SQL Server service we will outline relative to the SQL Server engine. It's primary responsibility is scheduling Jobs in order to execute particular operations at specific points in time. SQL Server Agent also has the ability to notify operators based on specific errors, Job failures or business conditions.

SQL Server Relational Engine Programming Languages

The main programming language in SQL Server is called Transact-SQL or T-SQL. SQL is an abbreviation for structure query language. This language can be divided into two broad categories. First is DDL, which is an acronym for data definition language. These commands are to CREATE, ALTER and DROP database objects such as tables, views, functions, indexes, etc. Second is DML, which is an acronym for data manipulation language. These commands are primarily SELECT, INSERT, UPDATE and DELETE. This portion of the language is where programming logic like IF, IF...ELSE, WHILE, etc. would be used.

In general T-SQL is the most widely used language for DBAs\Developers and probably the best place to start learning SQL Server. However, SQL Server does support other programming languages internal to the database engine and in some cases, these languages are preferred. Here is a brief explanation:

  • CLR is the acronym for Common Language Runtime which extends executing compiled .NET code directly from the database engine.
  • "LINQ is a set of extensions to the .NET Framework that encompasses language-integrated query, set and transform operations. It extends C# and VB with native language syntax for queries and provides class libraries to take advantage of these capabilities, available only in .NET Framework 3.5." (Source - Introduction to Language Integrated Query (LINQ))
  • SMO is an acronym for SQL Server Management Objects which has an object hierarchy built on the .NET Framework. Check out this tip - Getting started with SQL Server Management Objects (SMO).
  • PowerShell has gained a great deal of popularity recently with Network, System and Database Administrators since it's introduction in 2006. It is also built on the .NET Framework and leverages SMO when working with SQL Server objects directly.

SQL Server Integration Services

Integration Services was introduced in SQL Server 2005. It replaced Data Transformation Services (DTS) which was introduced in SQL Server 7.0. In a nutshell, Integration Services is a engine to perform data extraction, transformation and loading (ETL). This is a complicated way of saying moving data from one location to another. The locations can be SQL Server databases, flat files or other database platforms such as Oracle, DB2, Access, Sybase. The SQL Server Integration Services development is conducted inside of the Business Intelligence Development Studio.

The Business Intelligence Development Studio offers a feature rich development tool to efficiently manage the code, change management, error handling, etc. The Integration Services Package can be executed directly or scheduled with SQL Server Agent. Although Integration Services offers a very feature rich solution, you may encounter other T-SQL commands that also meet the ETL needs of many organizations to include BCP, BULK INSERT, OPENROWSET, etc. Keep in mind Integration Services is a separate installation option (Tip 1, Tip 2 and Tip 3) when you install SQL Server.

Check out the SQL Server Integration Services Tutorial as a stepping stone to learn the technology. Once you have worked through the tutorial, check out the SQL Server Integration Services tips.

SQL Server Reporting Services

Reporting Services was originally released after the introduction of SQL Server 2000. Reporting Services provides report authoring (development), rendering and management features. In many environments, Reporting Services is installed on a separate SQL Server just to handle reporting needs. Keep in mind Integration Services is a separate installation option (Tip 1, Tip 2 and Tip 3) when you install SQL Server. Here is another valuable tip for SQL Server 2005 - Adding Reporting Services to an existing SQL Server installation. During the installation process new SQL Server programs are installed in addition to two databases to support the report meta data and temporary objects. After the installation, configurations are needed to access the report meta data and to setup features to email, encrypt the data, etc.

Check out the SQL Server Reporting Services Tutorial as a stepping stone to learn the technology. Once you have worked through the tutorial, check out the SQL Server Reporting Services tips.

SQL Server Analysis Services

Analysis Services is the primary business intelligence tool in SQL Server. Analysis Services provides the means to build and query multi-dimensional data. Analysis Services and the relational engine have a number of parallel concepts. Both have databases, programming languages, security, backup and recovery features, etc. The key concept with Analysis Services are cubes. If you are a visual person you can think of cubes as a very large "Rubix Cube" with a number of different ways to access the data to determine trends, opportunities, etc.

Analysis Services is a separate installation option (Tip 1, Tip 2 and Tip 3) just like Integration Services and Reporting Services.

Here are some tips to begin learning about Analysis Services:

SQL Server Tools

SQL Server has a variety of tools to meet particular administrative and development needs. These tools include:

At MSSQLTips, we have organized the industry leading tools in one place. Check them out now.

Who works with SQL Server?

In reality more people work with SQL Server in their day to day tasks than anyone probably realizes. Many web sites and core business applications are supported by SQL Server. Typically SQL Server based applications are design, built, maintained and enhanced by DBAs, Developers, Data Modelers, Network Admins, System Admins, Storage Admins, etc. In a business setting, users interact with SQL Server in the following ways:

  • Core Business applications
    • Web and desktop
  • SharePoint applications
  • Reporting applications
  • Decision support applications
  • Dashboards and score cards
Next Steps
  • This tip is intended as a stepping stone to learn SQL Server. If you are new to SQL Server check out the URLs for the particular section of tips that is most interesting to you.
  • If you still have questions about SQL Server or need to figure out the next steps in your learning process, please add entries to the forum link below or give us some feedback.
  • As you learn SQL Server stop back to MSSQLTips to expand your knowledge and contribute to the community.


Last Updated: 2010-02-23


next webcast button


next tip button



About the author
MSSQLTips author Jeremy Kadlec Since 2002, Jeremy Kadlec has delivered value to the global SQL Server community as an MSSQLTips.com co-founder and Edgewood Solutions SQL Server Consultant.

View all my tips
Related Resources




Post a comment or let the author know this tip helped.

All comments are reviewed, so stay on subject or we may delete your comment. Note: your email address is not published. Required fields are marked with an asterisk (*).

*Name    *Email    Email me updates 


Signup for our newsletter
 I agree by submitting my data to receive communications, account updates and/or special offers about SQL Server from MSSQLTips and/or its Sponsors. I have read the privacy statement and understand I may unsubscribe at any time.



    



Thursday, May 29, 2014 - 8:11:22 AM - K SANTHOSH Back To Top

HELLO

THANKYOU 

THIS IS EXCELLENT INITIAL BACKGROUND FOR STARTER

 

K SANTHOSH


Wednesday, May 08, 2013 - 8:19:48 AM - Shruthi Back To Top

Hello,

Thankyou so much, this is an excellent package especially for the beginners..

Thankyou,

Shruthi


Monday, April 08, 2013 - 10:29:25 AM - Jeremy Kadlec Back To Top

Ritesh,

At this point in time, I think you need to start branching out into new portions of the database engine based on what you enjoy.  I would take some time to think about what you enjoy and then build a plan around that.  If you still feel you have not been exposed to the full SQL Server stack, I would try to get exposure to those portions of the engine and re-assess your situation.

HTH.

Thank you,
Jeremy Kadlec
Community Co-Leader


Monday, April 08, 2013 - 9:42:51 AM - Ritesh Aggarwal Back To Top

 

I am new to SQL Server.I know the SQL DML,DDL queries and i had run that all queris in the database.

My Question is i want to know that after Learning and running all SQL queirs in a database what is the next step that should i do or start to learn more and perform better in SQL server 2008 R2.

Kindly help me..List me the content step by step to Learn it and get a job at intermediate level in SQL Server.

Please do revert back...

 

Thanking You

Ritesh


Friday, October 05, 2012 - 10:43:46 AM - Jeremy Kadlec Back To Top

Tony,

Thank you for the feedback.  Let me get this updated for SQL Server 2012 and include that update.

Thank you,
Jeremy Kadlec 


Thursday, October 04, 2012 - 8:13:41 AM - Tony Sutcliffe Back To Top

Jeremy,

I would also say that I think this is a well structured article and an excellent introduction to SQL server.

You make the comment that "Databases typically have 2 files when they are built"; although this is correct, I feel that it might be worth highlighting that the first file is the "Primary Data File" and that there can be a number of "Secondary Data Files" in addition. It would also be worth then linking that through to articles on why and when people might want to consider using multiple secondary files.


Tuesday, August 21, 2012 - 8:19:00 PM - Jeremy Kadlec Back To Top

Gene,

Thank you for the feedback.  Until we are able to update the tip, I would encourage you to review these tips - http://www.mssqltips.com/sql-server-tip-category/111/express-edition/.

Thank you,
Jeremy Kadlec


Tuesday, August 21, 2012 - 7:05:33 PM - Gene Wirchenko Back To Top

Please revise this tutorial to include what is included in the Express versions and what is not.


Friday, April 27, 2012 - 2:12:17 PM - Jeremy Kadlec Back To Top

Reed,

Thank you for the positive feedback.  If you have any other aspects of SQL Server you could use some clarifications on please let us know here - http://www.mssqltips.com/feedback.asp.

Thank you,
Jeremy Kadlec


Thursday, April 26, 2012 - 6:51:12 PM - Reed Back To Top

This was a great article. Thanks for speaking the lay person's language to get me started.


Learn more about SQL Server tools