University:
Boston University
Course:
CAS CS 501 | Computer Science Practicum
Academic year:

2020
Views:

353

Pages:

15
Author:

Orvonin2y6

Download SQL Server Management Studio (SSMS) You will be brought to a web page to download the latest release of SQL Server Management Studio. Click on the link to download the latest release, and save the file to a location you can remember Install SQL Server Management Studio (SSMS) Once downloaded, run the SSMS installer from your browser, or directly by double clicking it in Windows Explorer. The first screen that appear is shown below. Click the “Install” button to begin. A progress screen will appear similar to the following. Let it progress through until completion, then you will see a screen indicating successful setup, click close. Congratulations! SSMS is now installed. SQL Server Data Tools SQL Server Data Tools: Formerly Business Intelligence Development studio - a component of Visual Studio with some DBMS components for Analysis services, and development tools, etc. You can find the link to the install instructions in the Tools Section of the SQL Server Installation Center: a. (CS669) Not required b. (CS779) This component may be needed for most advanced topics. Working with and connecting to SQL Server You have installed both SQL Server and SSMS. There are just a few more steps you need in order to start using your database to complete assignments -- connecting to your database and creating a database for assignments. Starting & Stopping SQL Server (optional) If during setup you selected for SQL Server to start manually then you will need to go to the Windows Control Panel->Administrative Tools->Services  Services for SQL Server Developer.  Start the following service: SQL Server (Instance Name)  If using SQL Server Analysis Services check that this is using the local account. 1. Double click on SQL Server Analysis Services. 2. Go to the Log On Tab and choose Local System Account. Click Ok, service will restart if needed.    Note that when you are no longer using SQL Server you can shut the service down to save on system resources. You can also change the startup type to be automatic while the course is running to save you the step of turning this on and off. You may want to put the services shortcut to your desktop for quick access Logging into SQL Server using SQL Server Management Studio    To work with SQL Server you will use the SQL Server Management Studio. You will find it under Microsoft SQL Server 2016 program group. You may want to put the SQL Server Management Studio shortcut to your desktop or pin it to the Windows Task bar for quicker access. In the Connect to Server dialog box: o Server Type: Database Engine (default) o Server Name: This is your system name (default). o Authentication: Use  Windows Authentication (default) and your account OR  The SQL Server Authentication with Login: SA and password which you created during the install and click Connect. Tip: If you forget your system name Click the down arrow icon, , then select “ to browse for your server name, as illustrated below. Under “Local Servers”, expand “Database Engine” and select the SQL Server instance you just installed and click Ok. You have just connected to your database through SQL Server Management Studio! Using SQL Server Management Studio Overview of SQL Server Management Studio Once you connect to SQL Server Instance you can begin to create a database, write quires, or explore the database. Below is a very quick overview of the SQL Server Management Studio Interface to get you started. Saves your SQL commands as .SQL files. Creates a new query window for you to type your SQL commands. Runs your SQL commands. Dropdown to select the database you are working with. Make sure not to work in the master database. Object Explorer allows you to browse databases, tables, columns and other objects within the database. Query window where you can type in your SQL query commands. SQL Query results. Note how the execution time and number of rows are at the bottom. Creating a Database You are almost ready to begin working on assignments, but one more step is needed: creating a database. Now to be sure, there is already a default database called “master”, but it is perilous to use that database for anything of substance. Master is a system database which contains information about the server’s configuration; that database is critical to the operation of SQL Server itself, and if it gets corrupted, or runs out of space, the entire SQL Server instance is at risk. System databases are often located on drives with limited space, and if we need to fail over our instance to another instance, we cannot usually restore the master itself since each instance has its own configuration. Suffice it to say, for assignments it is prudent to create another database. To get started, first right-click on “Databases” in the Object Explorer, and click “New Database…” from the context menu, as illustrated below. When the New Database window appears, enter a database name, and leave everything else defaulted. In the screenshot below, we use “CS669” as the database name, though you can use something different if you’d like. Then click the OK button to create the database. The window will process for a moment, then disappear. Next, in the Object Explorer, expand “Databases” and locate your new database. This is illustrated below. Right-click on CS669 and select “New Query”, as illustrated. A new query window appears, where commands can be typed, saved, and executed. The window is illustrated next. All of your assignment’s commands can be typed and executed in this type of query window! Let’s execute a single SQL command to verify that the database is running. In the buffer, type SELECT DB_NAME() as DatabaseName and then click the “Execute” button just above. You may alternatively hit the F5 key to execute the command. You should see the results something like this: Notice that the results listed out our database name, CS669. There are of course many more commands that you will use in your course, but this gets us started. When you complete your assignments, you will use a buffer just like this, type in your commands, and execute them to get your results. Congratulations! You have installed SQL Server and its client, connected to your database, and executed a command. You are now ready to complete assignments for your course! Uninstall SQL Server or Change Features If you no longer need to use SQL Server, or would like to re-install it or change feature, you can use these steps to uninstall SQL Server from your system. Uninstalling SQL Server 1. Go to Windows Control Panel->Programs and Features 2. Sort program list by name. 3. Look for Microsoft SQL Server 2016 (64-bit) and double click on it. 4. Choose Remove 5. SQL Server will gather information that it needs to perform the uninstall. This will take some time. 6. When prompted to Select Features, Select All and click Next. 7. Removal Rules will process, click Next. 8. Ready to Remove will give you a summary, click Remove. 9. Once finished SQL Server is removed. You may want to review Windows Control Panel>Programs and Features to make sure no components have been left behind, but be careful not to remove any Windows SQL Server components such as Windows Compact Edition. If you are not sure, you can leave these as is. Change SQL Server Features and Components 1. 2. 3. 4. 5. Go to Windows Control Panel->Programs and Features Sort program list by name. Look for Microsoft SQL Server 20146 (64-bit) and double click on it. Choose Add. You may be prompted to select the SQL Server media location. (i.e. your DVD drive) 6. SQL Server will gather information that it needs to modify components and check Install Setup files. This will take some time. Click Ok or Next when prompted. 7. When prompted to Select Installation Type, choose Add features to an existing instance of SQL Server 2016 and click Next 8. When prompted for Feature Selection, review and update features, review Feature list in the installation instructions in previous sections, and click Next. 9. You will be prompted to verify Installation Rules, Disk Space Requirements, Error Reporting, and Installation Configuration Rules, click Next. 10. Ready to Install will give you a summary, click Install. Appendix: How to Install SQL Server on a Mac SQL Server can be installed and used on a Mac, but this requires some setup work. Many consider Mac computers to be the most user friendly computers available, and there are many devoted Mac users today. Although Mac computers may be user friendly, the Mac platform is not supported by the major, modern DBMS vendors, including Oracle and SQL Server. If you find yourself in the situation where your home computer is a Mac, and you do not have a readily available Windows machine available for DBMS installation, there are two ways to run Windows on your Mac – dual booting and using a virtual machine. Dual Booting The first solution, dual booting, is available to you if you have a modern Mac that runs on an Intel‐based processor. All new Macs run on Intel‐based processors, but older ones do not. Dual booting is a fairly simple concept. Normally when you power on your computer, your operating system starts booting immediately, and this happens seamlessly so that it appears your operating system is just a natural part of the computer. In actuality, when your computer is first powered on, it first loads a boot loader program, and that boot loader tells the operating system to start. If there is only one operating system, you may not even notice the work of the boot loader, because it always starts the same operating system. However, there is no reason why one cannot install two operating systems on their computer. In such a case, each time your computer is powered on, the boot loader asks you which operating system you would like to start, and also usually defaults to the first one if you do not select an option, after a timeout period. All new Macs come with what Apple terms “Boot Camp”, which is a built‐in utility that supports dual booting Mac OS X and Windows. To install Oracle in Windows on your Mac, you will need to: 1. Review the prerequisites needed to run Boot Camp and to install Windows as a second operating system on your Mac computer. The prerequisites are listed at http://support.apple.com/kb/HT1461. Ensure that your computer meets the requirements before continuing. 2. Obtain a licensed copy of Windows. If you do not have a licensed copy of Windows, you will need to download one from the MSDNAA site. BU students are entitled to free, licensed copies of the latest versions of Windows through the MSDNAA site, and details on how to access this site are available in your course’s syllabus. 3. Burn the copy of Windows onto a CD, or copy the ISO image onto a USB stick. Boot Camp supports installing Windows from either a CD or a USB stick. 4. Follow the steps recommended by Apple to install Windows using Boot Camp. 5. After Windows is installed, reboot your computer then boot into Windows. Proceed with the SQL Server install instructions, starting from the beginning of this install guide. When you need to run SQL Server, boot into Windows. When you need to use your Mac applications, boot into OS X. Using a Virtual Machine A virtual machine mostly behaves as any other application, but has some differences. The virtual machine has an application window that can be minimized and closed, the same as any other application. What makes a virtual machine different from an ordinary application is that an entire operating system is installed and executes inside of the virtual machine. The operating system running inside of the virtual machine, termed a “guest” operating system, runs as if it were to be on its own physical machine. This means we can install and use applications native to the guest operating system. Thus, once we are running a virtual machine, we are effectively running two operating systems at the same time – our machine’s operating system (termed the “host” operating system), and the guest operating system – and are using applications native to both operating systems at the same time. In our case, we are interested in running Windows as a guest operating system on our Mac. There are many virtual machines available for Macs; however, perhaps the two most popular are VirtualBox and Parallels. VirtualBox, available at http://virtualbox.org, is free to download and use. Parallels, available at http://parallels.com, costs money, but offers more features. Students have successfully used both to run both Windows and SQL Server on a Mac in our BU program. Follow the steps below to install and use SQL Server on your Mac: 1. Download and install your virtual machine of choice. 2. If you do not have a licensed copy of Windows, you will need to download one from the MSDNAA site. BU students are entitled to free, licensed copies of the latest versions of Windows through the MSDNAA site, and details on how to access this site are available in your course’s syllabus. 3. Install Windows inside of the virtual machine. 4. Proceed with the SQL Server install instructions, starting from the beginning of this install guide, installing SQL Server into the guest operating system. Dual Booting Versus Using a Virtual Machine An obvious question is, which of these two options should you use? The answer depends upon your computer hardware, and your personal preferences. The following table summarizes the advantages of both options. Dual Booting Advantages Disadvantages Because both operating systems run natively on the computer’s hardware, there is no performance overhead. You can only run one operating system and its applications at a time. Because both operating systems directly access the computer’s hardware, there are not hardware compatibility issues. The setup is conceptually simpler. Simply boot the operating system you need upon startup. Virtual Machine The guest operating system and its applications run at the same time as the host operating system and its applications. There is clipboard sharing between applications in both operating systems. Text can be copied from an application in one operating system, and pasted into an application in the second operating system. To start the second operating system, you must reboot. There is no clipboard sharing between applications in both operating systems. If text is to be shared across applications, it must be saved in a file then loaded by applications in the other operating system. Because the guest operating system is running under the control of virtual machine software, the guest operating system and its applications will execute noticeably slower than if they were running natively on the computer. Because both operating systems run concurrently, the performance of the host operating system may degrade. If your hardware is powerful enough to support running two operating systems simultaneously, and still perform reasonably well, you may want to use a virtual machine, so that you can run both your Mac applications and your Windows applications at the same time. If you are concerned about obtaining the best performance for both operating systems, you may want to dual boot. A third advanced option, supported by the Parallels virtual machine, is to run the same Windows installation under a dual boot configuration and a virtual machine configuration. This is an advanced setup, and will require two Windows license registrations, as running the same installation both ways is the equivalent of running Windows on two different physical machines.

Microsoft SQL Server Installation Guide Pt 2

Related Documents

Recommended Documents

Description

Related Documents

Free up your schedule!

Take 5 seconds to unlock