Module 1Introduction to Microsoft SQL Server 2014

Module 1: Introduction to Microsoft SQL Server 2014

Página 1 de 26

Module 1: Introduction to Microsoft SQL Server 2014 Contents:

Module Overview Lesson 1:

The Basic Architecture of SQL Server

Lesson 2:

SQL Server Editions and Versions

Lesson 3:

Getting Started with SQL Server Management Studio

Lab:

Working with SQL Server 2014 Tools Module Review and Takeaways

Module Overview

Before beginning to learn how to write queries with Microsoft SQL Server 2014, it is useful to understand the overall SQL Server database platform, including its basic architecture, the various editions available for SQL Server 2014, and the tools a query writer will use. This module will also prepare you to use SQL Server Management Studio, SQL Server's S erver's primary development and administration tool, to connect to SQL Server instances and create, organize, and execute queries.

Objectives After completing this module, you will be able to:

• Des Descri cribe be the the archite architectur cturee of SQL Serv Server er 2014. 2014. • Des Descri cribe be the the editio editions ns of SQL Serv Server er 2014 2014..

Module 1: Introduction to Microsoft SQL Server 2014

Página 2 de 26

• Wor Work k with with SQL SQL Server Server Man Manage agemen mentt Studi Studio. o.

Lesson 1 : The Basic Architecture of SQL Server Se rver In this lesson, you will learn about the basic architecture and concepts of Microsoft SQL Server 2014. You will learn how instances, services, and databases interact, and how databases are structured. This will help prepare you to begin working with SQL Server S erver queries in upcoming modules.

Lesson Objectives After completing this lesson, you will be able to describe:

• Relatio Relational nal databases databases and, and, specifically, specifically, the the role and structur structuree of SQL Server Server databases databases.. • Th Thee sample sample data databas basee used used in thi thiss cours course. e. • Cl Clien ientt serv server er da datab tabas ases es.. • Th Thee structu structure re of Tran Transact sact-SQ -SQL L queri queries. es.

Relation al Da Databases tabases

Module 1: Introduction to Microsoft SQL Server 2014

Página 3 de 26

Typical relational databases comprise of several tables that relate to each other. Each table typically represents a class of entity which might be something tangible, such as an employee, or something intangible, such as a sales order. In this example, a very simple database might have an employee table and an order table, with employees able to place orders.

We find meaningful information by using joins, which are possible when two tables share values.

To continue the example, each order has an employee ID for the person who placed the order.

It is also possible to join several tables. Let’s extend the example and add customers. Now each order also contains a customer ID that can be used to link i t to the new customer table. We can now display an employee and their customers by joining all three tables. It is not necessary to display any order information, we can just use this as a bridge between the other two tables.

Databases in SQL Server are containers for data and objects, including tables, views, stored  procedures, user accounts, and other management objects. An SQL Server database is always a single logical entity, backed by multiple physical files.

SQL Server supports two types of databases—system and user. TS QL, the sample database you will be using to write queries, is a user database. SQL Server's system databases include:

• master, the system configuration database. • msdb, the configuration database for the SQL Server Agent service and other system services. • model, the template for new user databases. • tempdb, used by the database engine to store temporary data such as work tables. This database is dropped and recreated each time SQL Server restarts. Never store anything you need to depend on in it!

Module 1: Introduction to Microsoft SQL Server 2014

Página 4 de 26

• Resource, a hidden system configuration database that provides system objects to other databases.

Database administrators and developers can create user databases to hold data and objects for applications. You connect to a user database to execute your queries. You will need security credentials to log on to SQL Server and a database account with permissions to access data objects in the database.

 About the Course Sample Database

In this course, most of your queries will be written against a sample database named TSQL2014. This is designed as a small, low-complexity database suitable for learning to write T-SQL queries. It contains several types of objects:

• User-defined schemas, which are containers for tables and views. You will learn about schemas later in this course. • Tables, which relate to other tables via foreign key constraints. • Views, which display aggregated information.

The TSQL2014 database is modeled to resemble a sales-tracking application for a small  business. Some of the tables you will use include:

Module 1: Introduction to Microsoft SQL Server 2014

Página 5 de 26

• Sales.Orders, which stores data typically found in the header of an invoice (order ID, customer ID, order date, and so on). • Sales.OrderDetails, which stores transaction details about each order (parent order ID,  product ID, unit price, and so on). • Sales.Customers, which stores information about customers (company name, contact details, and so on). • HR.Employees, which stores information about the company's employees (name, birthdate, hire date, and so on).

Other tables are supplied to add context, such as additional product information, to these tables.

Client Server Databases

SQL Server is a client server system. This means that the client software, which includes SQL Server Management Studio and Visual Studio, is separate from the SQL Server database engine.

When client applications send requests to the database engine as T-SQL statements, SQL Server performs all file, memory, and processor utilization on the client's behalf. Clients never directly access database files, unlike in desktop database applications.

Module 1: Introduction to Microsoft SQL Server 2014

Página 6 de 26

In the course, the client and server are running on the same virtual machine, but in most environments the client software is running on a separate machine to the database engine.

Whether the database engine is local, or you are connecting to it over a network, it makes no difference to the T-SQL code that we write. On the logon screen, you just need to specify the server that you are connecting to.

Because you can connect to instances of SQL Server over a network, you can also refer to other databases in a T-SQL script. To do this, you need to refer to a t able, or other object, using its four-part name. This takes the format of Instance.Database.Schema.Object. For example, the orders table in the dbo schema, in the sales database on the MIA-SQL server’s default instance, would be referred to as MIA-SQL.sales.dbo.orders. To connect to a remote server in a T-SQL script, you should set up the remote instance as a linked server. In T-SQL you can add a linked server using the sp_addlinkedserver stored procedure. Although there are many arguments that can be supplied, in its most straightforward, default, use you could connect to the server in the previous example using the statement exec sp_addlinkedserver n’MIA-SQL’.

Queries

T-SQL is a set-based language. This means that it does not go through records row-by-row,  but instead pulls data from the server one table at a time, or a subset of the table if it is filtered. This makes SQL Server very efficient to deal with large volumes of data, although writing a seemingly straightforward query to add five percent to the preceding row is quite complicated.

Module 1: Introduction to Microsoft SQL Server 2014

Página 7 de 26

SQL Server does not typically consider what row a record is on, it looks at the data within that row.

T-SQL scripts are stored in script files with an .sql extension. These can be further organized into projects.

Inside each file, the script can be ordered into batches, that are marked with the word GO at the end. It is important to realize that each batch is run in its entirety before the next one is started. This is important if things need to happen in a certain order. For example, if you had a script that created a table, and then populated it with data, it would fail without batches. SQL Server would analyze the batch and reject the statement that populated the table bec ause the table does not currently exist. If you write the script to create the table, type GO, and then write the script to populate the table. It will succeed because the table exists when SQL Server assesses the second batch.

Lesson 2: SQL Server Editions and Versions In this lesson, you will learn about the editions and versions of Microsoft SQL Server. You will learn which editions of SQL Server 2014 are available, their distinguishing features, and which editions would be best to use when planning a new deployment.

Lesson Objectives After completing this lesson, you will be able to describe:

• The versions of SQL Server. • The editions of SQL Server 2014. • The choices when deploying SQL Server databases to the cloud.

Module 1: Introduction to Microsoft SQL Server 2014

Página 8 de 26

SQL Serv er Versions

SQL Server 2014 is the latest version in the history of SQL Server development. Originally developed for the OS/2 operating system (versions 1.0 and 1.1 ), SQL Server versions 4.21 and later moved to

the Windows® operating system.

SQL Server's engine received a major rewrite for version 7.0, and subsequent versions have continued to improve and extend SQL Server's capabilities, from the workgroup to the largest enterprises.

Note: Although its name might suggest it, SQL Server 2008 R2 is not a service pack

for SQL Server 2008. It is an independent version (number 10.5) with enhanced multiserver management capabilities, as well as new business intelligence (BI) features.

Question: Have you worked with any versions of SQL Server prior to SQL Server

2012?

SQL Serv er Editio ns

Module 1: Introduction to Microsoft SQL Server 2014

Página 9 de 26

SQL Server offers several editions providing different feature sets that target various business scenarios. In the SQL Server 2012 release, the number of editions was streamlined from  previous versions. The main editions are:

•   Enterprise, which is the flagship edition. It contains all of SQL Server 2014's features, including BI services and support for virtualization. •   Standard, which includes the core database engine, as well as core reporting and analytics capabilities. However, it supports fewer processor cores and does not offer all the availability, security, and data warehousing features found in Enterprise. • Business Intelligence, which is a new edition. It provides the core database engine, full reporting and analytics capabilities, and full BI services. However, like the Standard edition, it supports fewer processor cores and does not offer all the availability, security, and data warehousing features.

SQL Server 2014 also offers other editions, such as Parallel Data Warehouse, Web, Developer, and Express, each targeted for specific use cases.

This course uses core database engine features found in all editions.

SQL Serv er in t he Cloud

Module 1: Introduction to Microsoft SQL Server 2014

Página 10 de 26

SQL Server does not have to run locally, but can also operate as a cloud-based database, taking two forms. SQL Server could be running on a cloud-based server that your organization has provisioned and integrated with your infrastructure. If this is the case, and the infrastructure is properly set up, you should treat it as an instance of SQL Server on your network. In fact, this might be the case and you are completely unaware of it.

The other alternative is the Microsoft Azure™ SQL Database. This allows you to provision databases that use SQL Server technology in the cloud, but without having to provision and configure a whole virtual machine. There are some limitations to T-SQL when using the Microsoft Azure SQL Database, but nothing that will a ffect this course.

Additional Reading: For more information on the use of T-SQL in Microsoft Azure SQL Databases, go to the MSDN article Transact-SQL Support (Microsoft Azure SQL  Database): http://go.microsoft.com/fwlink/?LinkID=394805

Lesson 3: Getting Started with SQL Server Management Studio In this lesson, you will learn how to use SQL Server Management Studio (SSMS) to connect to an instance of SQL Server, explore the databases contained in the instance, an d work with script files containing T-SQL queries.

Module 1: Introduction to Microsoft SQL Server 2014

Página 11 de 26

Lesson Objectives After completing this lesson, you will be able to:

• Start SSMS. • Use SSMS to connect to on-premises SQL Server instances. • Explore a SQL Server instance using Object Explorer. • Create and organize script files. • Execute T-SQL queries. • Use Books Online.

Starting SSMS

SSMS is an integrated management, development, and querying application with many features for exploring and working with your databases. SSMS i s based on the Visual Studio shell. If you have experience with Visual Studio, you will likely feel comfortable with SSMS.

To start SSMS, you may:

• Use its shortcut on the Windows Start screen.

Module 1: Introduction to Microsoft SQL Server 2014

Página 12 de 26

• Enter its filename, SSMS.EXE, in a command prompt window.

By default, SSMS will display a Connect to Server dialog box you can use to specify the server (or instance) name and your security credentials. If you use the Options button to access the Connection Properties tab, you can also supply the database to which you wish to connect. However, you can explore many SSMS features without initially connecting to an SQL Server instance, so you may also cancel the Connect to Server box and link to a server later.

After SSMS is running, you may wish to explore some of its settings, such as those found in the Tools, Options box. SSMS can be customized in many ways, such as setting a d efault font, enabling line numbers for scripts, and controlling the behavior of its many windows.

Additional Reading: For more information on using SQL Server Management Studio, go to Use SQL Server Management Studio in Books Online: http://go.microsoft.com/fwlink/?LinkID=402707

Connecting to SQL Server

To connect to an instance of SQL Server, you need to specify several items, no matter which tool you use:

•

Module 1: Introduction to Microsoft SQL Server 2014

Página 13 de 26

The name of the instance to which you want to connect in t he form: hostname\instancename. For example, MIA-SQL\Proseware would connect to the Proseware instance on the Windows server named MIA-SQL. If you are connecting to the default instance, you may omit the instance name. For Microsoft Azure, the server name is in four parts in the form: .database.windows.net. • The name of the database. If you do not specify this, you will be connected to the database designated as your account's default by the database administrator, or to the master database if no default has been specifically assigned. In Microsoft Azure, it is important to choose the correct database as you may not change connections between user databases. You would need to disconnect and reconnect to the desired database. • The authentication mechanism required by the server. This may be Windows Authentication, in which your Windows network credentials will be passed to SQL Server (no entry required), or SQL Server Authentication, in which a username and password for your account must be created by a database administrator (you enter them at connection time). SQL Server Authentication is the only mechanism supported by Microsoft Azure. Question: Which authentication method do you use to log on to SQL Server in your

organization?

Working with Object Explorer

Module 1: Introduction to Microsoft SQL Server 2014

Página 14 de 26

Object Explorer is a graphical tool for managing SQL Server instances and databases. It is one of several SSMS window panes available from the View menu. Object Explorer provides direct interaction with most SQL Server data objects, such as tables, views, and procedures. Right-clicking an object, such as a table, will display context-sensitive commands, including query and script generators for object definitions.

Any operation performed in SSMS requires appropriate permissions granted by a database administrator. Being able to see an object or command does not necessarily imply permission to use the object or issue the command. Note:

SQL Server query writers most commonly use Object Explorer to l earn about the structure and definition of the data objects they want to use in their queries. For example, to le arn the names of columns in a table, you follow these steps:

1.

Connect to the SQL Server, if necessary.

2.

Expand the Databases folder to expose the list of databases.

3.

Expand the relevant database to expose the Tables folder.

4.

Expand the Tables folder to view the list of tables in the database.

5.

Locate the table you are interested in and expand it to find the Columns folder. The Columns folder will display the names, data types, and other information about the columns that make up the table. You can even drag the name of a database, table, or column into the query window to have it entered and avoid typing it yourself.

Selecting objects in the Object Explorer pane does not change any connections made in other windows. Note:

Module 1: Introduction to Microsoft SQL Server 2014

Página 15 de 26

Working with Script Files and Projects

SSMS allows you to create and save T-SQL code in text files, typically given an .sql file extension. Like other Windows applications that open, edit, and save files, SSMS provides access to file management through the File menu, as well as st andard toolbar buttons.

In addition to directly manipulating individual script files, SSMS provides a mechanism for initially saving groups of files together and for opening, saving, and closing them together. This mechanism uses several conceptual layers to work with T-SQL script files and related documents, using the Solution Explorer pane to display a nd control them:

Object

Parent

Description

Solution

None

Top-level container for projects. Stored as a text file with an .ssmssln extension, which references components contained within it. May contain multiple  projects. Displayed at the top of the object hierarchy in Solution Explorer.

Project

Solution

Container for T-SQL scripts (called queries), stored database connection metadata, and miscellaneous files. Stored as a text file with an . ssmssqlproj extension, which references component scripts and other files.

Script

Project

T-SQL script file with an .sql extension. The core item of work in SSMS.

The benefits of using scripts organized in projects and solutions include the ability to immediately open multiple script files in SSMS. You can open the solution or project file from within SSMS or Windows Explorer.

Module 1: Introduction to Microsoft SQL Server 2014

Página 16 de 26

To create a new solution, click the File menu and click New Project. (There is no “New Solution” command.) Specify a name for the initial project, its parent solution, and whether you want the project to be stored in a subfolder below the solution file in the location you indicate. Click OK to create the parent objects.

To interact with Solution Explorer, open the pane (if necessary) from the View menu. To create a new script that will be stored as part of the project, right-click the Queries folder in the project and click New Query.

Using the New Query toolbar button or the new query commands on the File menu will create a new script temporarily stored with the solution in the Miscellaneous Files folder. If you wish to move an existing open query document into a solution currently open in Solution Explorer, you will need to save the file. You can then drag the query into the project tree to save it in the Queries folder. This will make a copy of the script file and place it in the solution. Note:

It is important to remember to save the solution when exiting SSMS or opening another solution to preserve changes to the file inventory. Saving a script using the Save toolbar button or the Save .sql command on the File menu will only save changes to the current script file contents. To save the entire solution and all its files, use the Save All command on the File menu or when prompted to save the .ssmssln and .ssmssqlproj files on exit.

Executin g Queries

Module 1: Introduction to Microsoft SQL Server 2014

Página 17 de 26

To execute T-SQL code in SSMS, you first need to open the .sql file that c ontains the queries, or type your query into a new query window. Then decide how much of the code in the script is to be executed as follows:

• Select the code you wish to execute. • If nothing is selected, SSMS will execute the entire script, which is the default behavior.

When you have decided what you wish to execute, you can run the code by doing one of the following:

• Clicking the Execute button on the SSMS toolbar. • Clicking the Query menu, then clicking Execute. • Pressing the F5 key, the Alt+X keyboard shortcut, or the Ctrl+E keyboard shortcut.

By default, SSMS will display your results in a new pane of the query window. The location and appearance of the results can be changed in the Options box, accessible from the Tools menu. To toggle the results display and return to a full-screen T-SQL editor, use the Ctrl+R keyboard shortcut.

SSMS provides several formats for the display of query results:

•

  Grid,

which is a spreadsheet-like view of the results, with row numbers and columns you

can resize. You can use Ctrl+D to select this before executing a query. •

  Text,

which is a Windows Notepad-like display that pads column widths. You can use

Ctrl+T to select this before executing a query. •

  File,

which allows you to directly save query results to a text file with an .rpt extension.

Executing the query will prompt a results file location. The file may then be opened by any

Module 1: Introduction to Microsoft SQL Server 2014

Página 18 de 26

application that can read text files, such as Windows Notepad and SSMS. You can use Ctrl+Shift+F to select this before executing a query.

Using Books Online

Books Online (often abbreviated BOL) is the product documentation for SQL Server. BOL includes helpful information on SQL Server's architecture and concepts, a s well as syntax reference for T-SQL. BOL can be accessed from the Help menu in SSMS. In a script window, context-sensitive help for T-SQL keywords is available by selecting the keyword and pressing Shift+F1.

Books Online can be browsed directly on Microsoft's website:

Books Online for SQL Server 2014 http://go.microsoft.com/fwlink/?LinkID=402708

Note: Before SQL Server 2014, SQL Server provided the option to install Books Online locally during SQL Server setup. In SQL Server 2014, Books Online does not ship with the product installation media, so must be downloaded and installed separately.

Module 1: Introduction to Microsoft SQL Server 2014

Página 19 de 26

The first time Help is invoked, you will be prompted to specify whether you wish to view Books Online content online or locally.

For detailed instructions on how to download, install, and configure Books Online for local offline use, go to the topic Get Started with Product Documentation for SQL Server:

Get Started with Product Documentation for SQL Server http://go.microsoft.com/fwlink/?LinkID=402709

Demonstr ation: Intr oducing Microsoft SQL Server 2014 In this demonstration, you will see how to:

• Use SSMS to connect to an on-premises instance of SQL Server. • Explore databases and other objects. • Work with T-SQL scripts.

Demonstr ation Steps Use SSMS to connect to an on-premises instance of SQL Server 2014

1.

Ensure that the 20461C-MIA-DC and 20461C-MIA-SQL virtual machines are both running, and then log on to 20461C-MIA-SQL as ADVENTUREWORKS\Student with the password Pa$$w0rd.

2.

Run D:\Demofiles\Mod01\Setup.cmd as an administrator.

3.

Start SQL Server Management Studio and connect to the MIA-SQL database engine instance using Windows authentication.

Module 1: Introduction to Microsoft SQL Server 2014

Página 20 de 26

Explore databases and other objects

1.

If the Object Explorer pane is not visible, click View and click Object Explorer.

2.

Expand the Databases folder to see the list of databases.

3.

Expand the AdventureWorks database.

4.

Expand the Tables folder.

5.

Expand the Sales.Customer table.

6.

Expand the Columns folder.

7.

Show the list of columns, and point out the data type information for the ModifiedDate column.

Work with T-SQL scripts

1.

If the Solution Explorer pane is not visible, click View and click Solution Explorer. Initially, it will be empty.

2.

Click the File menu, click New, click Project.

3.

In the New Project box, under Installed Templates, click SQL Server Management Studio Projects.

4.

In the middle pane, click SQL Server Scripts.

5.

In the Name box, type Module 1 Demonstration.

6.

In the Location box, type or browse to D:\Demofiles\Mod01.

7.

Point out the solution name, then click OK.

8.

In the Solution Explorer pane, right-click Queries, then click New Query.

9.

Type the following T-SQL code:

Module 1: Introduction to Microsoft SQL Server 2014

Página 21 de 26

USE AdventureWorks; GO SELECT CustomerID, AccountNumber FROM Sales.Customer;

10.

Select the code and click Execute on the toolbar.

11.

Point out the results pane.

12.

Click File, and then click Save All.

13.

Click File, and then click Close Solution.

14.

Click File, click Recent Projects and Solutions, and then click Module 1 Demonstration.ssmssln.

15.

Point out the Solution Explorer pane.

16.

Close SQL Server Management Studio without saving any files.

Lab: Working with SQL Server 2014 Tools Scenario The Adventure Works Cycles Bicycle Manufacturing Company has adopted SQL Se rver 2014 as its relational database management system of choice. You are an information worker who will be required to find and retrieve business data from several SQL Server databases. In this lab, you will begin to explore the new environment and become acquainted with the tools for querying SQL Server.

Objectives

Module 1: Introduction to Microsoft SQL Server 2014

Página 22 de 26

After completing this lab, you will be able to: • Use SQL Server Management Studio. • Create and organize T-SQL scripts. • Use SQL Server Books Online.

Estimated Time: 30 minutes Virtual machine: 20461C-MIA-SQL User name: ADVENTUREWORKS\Student Password: Pa$$w0rd

Exercise 1: Working with SQL Server Management Studio

Scenario

You have been tasked with writing queries for SQL Server. Initially, you would like to  become familiar with the development environment and, therefore you have decided to explore SQL Server Management Studio and configure the editor for your use. The main tasks for this exercise are as follows: 1.

Open Microsoft SQL Server Management Studio

2.

Configure the Editor Settings

Module 1: Introduction to Microsoft SQL Server 2014

Página 23 de 26

Task 1: Open Micros oft SQL Server Management Studi o

1.

Start SSMS, but do not connect to an instance of SQL Server.

2.

Close the Object Explorer and Solution Explorer windows.

3.

Using the View menu, show the Object Explorer and Solution Explorer windows in SSMS.

Task 2: Configur e the Editor Settin gs

1.

On the Tools menu, choose Options to open the Options window in SSMS and change the font size to 14 for the text editor.

2.

Change several additional settings in the Options window: o

Disable IntelliSense.

o

Change the tab size to 6 spaces for T-SQL.

o

Enable the option to include column headers when copying the result from the grid. Look under Query Results, SQL Server, Results to Grid for the check box Include column headers when copying or saving the results.

Results: After this exercise, you should have opened SSMS and configured editor settings.

Exercise 2: Creating and Organizing T-SQL scri pts

Scenario

Usually you will organize your T-SQL code in multiple query files inside one project. You will practice how to create a project and add different query files to it.

Module 1: Introduction to Microsoft SQL Server 2014

Página 24 de 26

The main tasks for this exercise are as follows:

1.

Create a Project

2.

Add an Additional Query File

3.

Reopen the Created Project

Task 1: Create a Proj ect

1.

Create a new project called MyFirstProject and store it in the folder D:\Labfiles\Lab01 \Starter.

2.

Add a new query file to the created project and name it MyFirstQueryFile.sql.

3.

Save the project and the query file by clicking the Save All option.

Task 2: A dd an A dditi onal Query File

1.

Add an additional query file called MySecondQueryFile.sql to the created project and save it.

2.

Open Windows Explorer, navigate to the project folder, and observe the created files in the file system.

3.

Back in SSMS, using Solution Explorer, remove the query file MySecondQueryFile.sql from the created project. (Choose the Remove option, not Delete.)

4.

Again, look in the file system. Is the file MySecondQueryFile.sql still there?

5.

Back in SSMS, remove the file MyFirstQueryFile.sql and choose the Delete option. Observe the files in Windows Explorer. What is different this time?

Module 1: Introduction to Microsoft SQL Server 2014

Página 25 de 26

Task 3: Reopen the Created Proj ect

1.

Save the project, close SSMS, reopen SSMS, and open the project MyFirstProject.

2.

Drag the query file MySecondQueryFile.sql from Windows Explorer to the Queries folder under the project MyFirstProject in Solution Explorer. (Note: If the Solution Explorer window is not visible, enable it as you did in exercise 1).

3.

Save the project.

Results: After this exercise, you should have a basic understanding of how to create a  project in SSMS and add query files to it.

Exercise 3: Using Books Online

Scenario

To be effective in your upcoming training and exercises, you will practice how to use Books Online to efficiently check for T-SQL syntax.

The main tasks for this exercise are as follows:

1.

Launch Books Online

2.

Use Books Online

Task 1: Launch Book s Online

1.

Launch Manage Help Settings from the Windows Start screen.

2.

Configure Books Online to use the online option, not local help.

Module 1: Introduction to Microsoft SQL Server 2014

Página 26 de 26

Task 2: Use Boo ks Onlin e

1.

Use Books Online to find information about SQL Server 2014 tools and add-in components.

Results: After this exercise, you should have a basic understanding of how to find

information in Books Online.

Module Review and Takeaways Review Question(s) Question: Can an SQL Server database be stored across multiple instances?

Question: If no T-SQL code is selected in a script window, which lines will be run when

you click the Execute button?

Question: What does an SQL Server Management Studio solution contain?