Chapter 1 : Microsoft SQL Server Step by Step - PDF Free Download - Fox ebook Your hands-on, step-by-step guide to building applications with Microsoft SQL Server Teach yourself the programming fundamentals of SQL Server â one step at a time. Installation of SQL Server is fairly easy. The installation wizard provides easy interface to install components of SQL server. Before you start to install the SQL server, install the NetFx3 feature, otherwise you will get error while the installation is in progress. To install the NEtFx3, type the following command in command prompt as shown in the snapshot below. Make sure you have inserted the installation media. Since this is going to be new SQL server installation select the first option. The installation will then check all the pre-requisites that are required to install the SQL server. If everything is fine, you will see green checks as shown below. Enter the product key and click Next. Or choose evaluation edition and click Next. Accept the license terms and click Next. Check to include SQL server product updates and click Next. The installation will now download the setup files as shown below. The installation does the pre-requisite checks once again as you can see below. Select the required SQL features and click Next. After the rules are checked as shown below, click Next. Under Instance Configuration, choose Default instance. You can also define custom instance name. Similarly, you have the option to choose the location where the instance will be stored. I will leave the defaults and click Next button. Under Disk Space Requirements, the installation will show the disk spaces as shown below. Under Database Engine Configuration, choose Windows authentication mode. You also have option to choose both windows authentication and SQL server authentication. Then, add the users who will be managing this SQL server and click Next. Under Error Reporting, review the information and click Next. After the installation is complete, click Close. You can now start creating databases. You may also like -. Page 1
Chapter 2 : How to Restore Database Backup in SQL Server Teach yourself the programming fundamentals of SQL Server â one step at a time. Ideal for beginning SQL Server database administrators and developers, this tutorial provides clear guidance and practical, learn-by-doing exercises for building database solutions that solve real-world business problems. If you are trying to Install Service pack on database which had Mirroring configured on it please refer to This Link. Steps to install SP2 would be same but few precautions needed to be taken care of. I highly recommend readers to please read all the sections before proceeding. Make sure you test all your application functionalities completely. Although service packs or thoroughly tested Microsoft recommends to test it in your UAT environment before proceeding with deployment in production environment. Backup system and user databases. If you use analysis services backup Analysis Service configuration files, databases and repositories. Backup files present at location C: Resource database is utilized during service pack upgrade. In earlier versions of SQL Server, upgrading required dropping and creating system objects. Because the Resource database file contains all system objects, an upgrade is now accomplished simply by copying the single Resource database file to the local server. Service pack upgrade would require a downtime of application. Make sure application does not access database during service pack upgrade. Make sure you stop all jobs and activities on database before proceeding. Make sure you are administrator on the system and always run the service pack executable with administrator privileges. Steps to Install SP2 Click on download mark on the link and download 64 bit or 32 bit of installable as per your machine architecture. After extraction is complete below message will appear. You can click on show details you check what all checks are performed by SQL server before starting installation of SP2. Sometimes is OS on which SQL Server is installed has restart pending it will show here as error saying restart pending. In that case you have to cancel the setup restart the OS and then again run the setup as administrator After you click next you would reach to License term page. You need to select the I accept check box and click on next After that Select Features page will appear on which you can select features of SQL Server you want to upgrade to SP2 and click next. Next we would move to page Check files In use. If you see SQL Server management studio is open with one other file. Or else you can close the applications and click on refresh check if you do not want to restart SQL Server service. After you are done with the choice click next. This will take you to ready to upgrade screen where you can cross check what are features being updated. Click on update to install SP2. This will take you to Install progress screen Allow installation to complete and if it completes successfully you would get below screen If Service Pack install fails please take help of Log files present at location C: Uninstall Service Pack If after service pack upgrade you face issue in you environment there is an option to remove service pack. You can go to add remove program and remove the service pack. Go to Run and type appwiz. Lots of new user gets confused thinking Service pack is not installed correctly. But you need to click on View Installed Updates to see service pack. After clicking on view installed updates below window will pop up. Page 2
Chapter 3 : Download Test Lab Guide: Install SQL Server Enterprise from Official Microsoft Download Cen This step-by-step has been created to help you get started in creating a SQL Server AlwaysOn Availability Group for your mission-critical databases. Prerequisites Windows Server Failover Cluster (WSFC). The procedure described is for a non-clustered server, and can be applied either to a default instance or a named instance. It is intended to be read by Database Administrators and anybody interested in the technical aspects of carrying out this task. Before beginning, you should check that minimum hardware and software requirements to install and run SQL Server have been met. For operating system and hardware requirements, visit: Identify drive that will be used for data or log files. Decide which folder will be the primary location for data files: If you are installing Analysis Services, identify drives that will host the data and log files for the cube s. Create dedicated service account for each of the service to be installed. Ensure that these accounts are not member of Local Administrator because it will give unnecessary rights to these accounts. Assign Deny logon locally right to these service accounts. Therefore it is recommended to change default ports associated with the SQL Server installation. From the root folder, double-click Setup. To install from a network share, locate the root folder on the share, and then double-click Setup. To create a new installation of SQL Server, select the Installation option on the left side, and then click New SQL Server stand-alone installation or add features to an existing installation: Setup is now preparing to launch Setup Support Rules window: In the License Terms window, tick the box I accept the license terms and then click Next to continue: You must accept the license agreement before you can continue the installation of SQL Server Send feature usage data to Microsoft option is optional. These files are necessary to perform the actual installation. Following the installation of the setup support files, you will be presented with another compatibility check. Following dialog appears once you successfully pass these checks. You can click the Show Details button under the green progress bar if you want to see the individual checks listed: Click Next to continue to the Setup Role page: You can also specify the shared feature directory where share features components will be installed. Click Next to continue to the Installation Rules page, Setup verifies the system state of your computer before Setup continues: Click Next to continue to the Instance Configuration page. This screen also report on other instances installed on this machine. Click Next to proceed to the Disk Space Requirements page: This is just a information page that does not require you to make any choices. Click Next to go to Server Configuration page: Here you specify service startup and authentication. Microsoft recommends that each service account have separate user accounts as a security best practice as shown in the following figure: Run SQL Server services with the lowest possible privileges. For the purposes of this article, we will authenticate all services using LocalSystem account. You may have noticed the Collation tab here in this page. Click Collation tab and then click Customize button to specify the collation for your Database Engine and Analysis Services instance that best matches your application need: Click Next to continue to Database Engine Configuration page. You will also need to specify the SQL Server administrators to be used; in this example I will use the current logged in user by clicking Add Current User button: Click Data Dictionary tab and specify default database, log, backup, and tempdb locations: Specify users or accounts that will have administrator permissions for Analysis Services in Account Provisioning page and specify non-default installation directories in Data Directories page: Click Next to continue to Reporting Services Configuration page, specify the kind of Reporting Services installation to create. For the purpose of this article, I will use Install and Configure option: Click Next to proceed to Distributed Replay Controller page, specify the users you want to grant administrative permissions to for the Distributed Replay controller service and then click Next to continue: Distributed Replay Client Configuration page appears, here specify setting as shown in next figure: Correct any errors reported in the Installation Rules screen and click on Next to advanced to Ready to Install page. This page shows a tree view of installation options that were specified during Setup. On this page, Setup indicates whether the Product Update feature is enabled or disabled and the final update version: The Setup will first install the required prerequisites for the selected features followed by the feature installation. The Installation Progress page provides status so that you can monitor installation progress as Setup continues: Page 3
When the installation is complete, click on Next to Complete page: Click on the link to review the installation log if appropriate, then click on Close. This finalizes the installation process for SQL Server He has more than a decade of IT experience in development, technical training and database administration on Microsoft SQL Server platforms. Basit has authored numerous SQL Server technical articles, and developed and implemented many successful database infrastructure, data warehouse and business intelligence projects. Page 4
Chapter 4 : How to: Configure SQL Server AlwaysOn - Part 1 of 7 - SQL Hammer SQL Hammer Installing SQL Server Step by Step If you have done an installation of a complex software product before, you probably recognize that feeling of uncertainty that accompanies starting the installation for the first time. In our previous article we learned how to install SQL Server on machine. Click on the first link and the installation process begin. Setup Support Rules Before proceeding with the installation steps, SQL Server setup runs a setup to check all the things required for installation. This check is nothing but a kind of verification to ensure you can proceed further or not. Product Updates Here, setup will look for latest product updates to enhance SQL Server performance as my setup found one update of 22 MB for enhancement as shown below. Setup Support Rules After successful completion of previous step, setup will again run a check to ensure everything looks good for the installation. On the Feature Selection page, all features will be selected by default. On Server Configuration page, default accounts will be set. On Database Engine Configuration page, your current logon account will be added as a Server Administrator. Components or Features to Install Select the components you want to install on your machine. The following is the description for above listed components. Allow you to install SQL Server instance. Allow you to install an Analysis Services instance on standalone or on cluster node. Allow you to install the server as report server. Allow you to install Integration Services. Allow you to install SQL Server management configuration tool including command line and power shell tool. If all looks good, click Next. Instance Configuration This step will ask, what type of instance you want to configure, as we all know, either we can install Default or Named instance. Select type of instance you want to install. As shown in above screenshot, I already installed 2 instances on my machine. After doing instance configuration, click Next. You can set startup type as Manual or Automatic. The collation type you select here will be set as default collation for your instance. After performing above steps, click Next. Page 5
Chapter 5 : SQL Failover Cluster Build (Step by Step) â Part 1: Installing SQL â MEA SI Blog Accept the license by clicking on "I accept license terms." Click Next. Step 6: Product Updates Here, setup will look for latest product updates to enhance SQL Server performance as my setup found one update of 22 MB for enhancement as shown below. Windows Server failover cluster used in the demo Please note that this is for demo purposes and built in my local environment Windows, Hyper The pre-requisites for Windows and SQL failover clustering storages, network configurations, user accounts, etc. You logged in Node 1 with cluster admin account. Provide product key for your media. Accept License Agreement and the other check if you would like. Setup Support Rules Wait for Rules check. Once done make sure no failed task. Evaluate warnings for your environment remember the VM is not connected to Internet. Then click Next 8. Select Features then Next Make sure feature Rule check complete with no Failed status. Provide Network and Instance names. MS recommends use of named instances. Select Disk needed for the resource group RG. MS recommends to use unique service accounts per each data services. Then click on Data Directories tab menu item. Please consider having different disks for data, log and temp data. Check the sharing error reports with MS if you would like. Make sure no clusters rules failed. Confirm the selection last chance to edit before installation. Enjoy your waiting with a coffee. Click Close to complete the process. You should see it is reflected on Cluster roles. In my next posts, I will demonstrate how to add a second node and how to install a new named database instance to the SQL cluster. Hope you like it and stay tuned! Page 6
Chapter 6 : Installing SQL Server Step by Step I installed SQL Server but when I open my SQL Server Configuration Manager. It shows that "The remote procedure call failed" when i click on SQL Server Services. I see that all the folders looks correct in SSMS in the object explorer. It brings SQL Server high availability and disaster recovery to a whole new level by allowing multiple copies of the database be highly available and potentially using them for read-only workloads and offloading management tasks such as backups. AlwaysOn Availability Groups allow you to fail over a group of databases as a single entity, unlike database mirroring where you can only do so one database at a time. This step-by-step has been created to help you get started in creating a SQL Server AlwaysOn Availability Group for your mission-critical databases. In previous versions of Windows Server, you need shared storage to create a failover cluster for the quorum disk. Windows Server and higher provided the option to use a file share witness as a quorum configuration. For this step-by-step, we will only be working with standalone SQL Server default instances. Before deciding to implement this feature, take stock of your SQL Server licenses to make sure you have enough to get you covered. If you intend to use the other replicas for read-only workloads or offloading your backups, you would need licenses for those SQL Server instances as well. This is also another one of those items that customers get confused with because in previous versions of SQL Server, database mirroring can be configured with Standard Edition. Same SQL Server collation for all replicas. This is one of the reasons for keeping the database collation the same for a single instance SharePoint also requires a specific collation for the content databases. If you want to configure AlwaysOn Availability Groups for your databases, they should all be running the same collation on all of the SQL Server instances acting as replicas. Unlike database mirroring where you can only have one extra copy of the database, AlwaysOn Availability Groups allow you to have up to five copies of the database running on five replicas â three of which can be configured for synchronous-commit mode and two in asynchronous-commit mode. For the operating system, we will be using Windows Server To add the Failover Clustering feature: When prompted with the Add features that are required for Failover Clustering dialog box, click Add Features. Click Install to install the Failover Clustering feature. Configuring Accounts in Active Directory. In the Validate a Configuration Wizard dialog box, click Next. In the Testing Options dialog box, make sure that the option Run all tests recommended is selected. In the Confirmation dialog box, click Next. The Failover Cluster Validation Wizard is expected to return several Warning messages, especially if you will not be using shared storage. As we mentioned earlier, there is no need to use shared storage to create the Windows Server Failover Cluster that we will use for our Availability Group. Just be aware of these Warning messages as we will configure a file share witness for our cluster quorum configuration. However, if you see any Error messages, you need to fix those first prior to creating the Windows Server Failover Cluster. This will create the Windows Failover Cluster using the servers as nodes of the cluster, add DNS and Active Directory entries for the cluster hostname. In the Summary dialog box, verify that the configuration is successful. To configure the cluster quorum configuration to use a file share, right-click on the cluster name, select More Actions and click Configure Cluster Quorum Settingsâ We will be configuring a file share witness for our cluster quorum setting. By default, the wizard will configure the cluster to use Node Majority. In the Select Quorum Witness page, select the Configure a file share witness recommended for special configuration option. In the Confirmation page, click Next. In the Summary page, click Finish. This needs to be done on all of the SQL Server instances that you will configure as replicas in your Availability Group. This will prompt you to restart the SQL Server service. Restart the SQL Server service. If you intend to create an Availability Group for a new SharePoint farm, you will need to create a temporary database. This is so that the SharePoint farm will use the AlwaysOn Availability Group when creating the farm configuration and the admin content databases. After the SharePoint farm has been created, this database can be removed from the Availability Group configuration and deleted from the instance. This will launch the New Availability Group Wizard. In the Introduction page, click Next. In the Select Databases page, select the checkbox beside the database that you want to include in your Availability Group. The databases have to be in Full recovery model prior to joining them in the Page 7
Availability group. Configure the following options Automatic Failover Up to 2: Checked Synchronous Commit Up to 3: No In the Endpoints tab, verify that the port number value is In the Listener tab, select the Create an availability group listener option. Enter the following details. Name that you will use in your application connection string Port: Provide a shared folder that is accessible the replicas and that the SQL Server service account used by both replicas has Write permissions to. This is just a temporary file share to store the database backups that will be used to initialize the databases in an Availability group. If you are dealing with large databases, it is recommended that you manually initialize the databases prior to configuring them as your network bandwidth may not be able to accommodate the size of the database backups. In the Validation page, verify that all validation checks return successful results. In the Summary page, verify all configuration settings and click Finish. This will create and configure the AlwaysOn Availability Group and join the databases. In the Results page, verify that all tasks have been completed successfully. You can now use the Availability Groups listener name in your application connection string. Keep in mind that you need to manually add new databases in the Availability Group even though your application has already been using the listener name. So, be sure to monitor the replicas in your Availability Groups to be alerted when new databases are created. Page 8
Chapter 7 : SQL Server Installation Guide - SQLServerCentral Contents at a Glance. Introduction xix. PRTA I GETTING STARTED WITH MICROSOFT SQL SERVER ChaPter 1. Overview of Microsoft SQL Server 3. This feeling comes from the complexity of the product to be installed and the diversity of questions to be answered during the installation process. Because you may not completely understand the product, you or the person who installs the software may be less than confident that you can give accurate answers for all the questions that the Setup program asks to complete its tasks. This section will help you to find your way through the installation by giving you answers to most of the questions that you are likely to encounter. As its name suggests, besides planning, Installation Center supports the installation of the software, too. Installation Center shows you several options related to the installation of the database system and its components. Again, it is the same tool that is launched when you click System Configuration Checker during the planning phase. Failures must be corrected before Setup can continue. If no problems are reported, click Next. After you have chosen an option, click Next. On the next page of the wizard, Product Key, enter the character key from the product packaging. Click Next to continue. On the Feature Selection page see Figure, select the components to install by checking the corresponding check boxes. Also, toward the bottom of the page, you can specify the directory in which to store the shared components. After that, click Next to continue. Figure â Feature Selection page Note â All the shared features in Figure are grayed out, which means that these features are not selected. For your own installation, you should decide which of these features should be installed and check their corresponding check boxes. Note â Components of SQL Server that are selected will be installed one after the other in the order in which they are listed on the Feature Selection page. The installation process starts with the installation of the Database Engine, followed by the installation of Analysis Services, and so on. Only the selected components will be installed. On the next page, Installation Rules, the setup runs rules to determine if the installation process will be blocked. On the Instance Configuration page see Figure, you can choose between the installation of a default or named instance. To install the default instance, click Default Instance. If a default instance is already installed and you select Default Instance, the Setup program upgrades it and gives you the option to install additional components. Therefore, you have another opportunity to install components that you skipped in the previous installation processes. Figure â Instance Configuration page To install a new named instance, click Named Instance and type a new name in the given text box. In the lower part of the page, you can see the list of instances already installed on your system. As you can see from Figure, the computer on which I installed the instance already contains an installed instance. The Disk Space Requirements page shows whether the space available on your disk is sufficient for the installation of the database system. If so, click Next to continue. The next page, Server Configuration see Figure, allows you to specify usernames and corresponding passwords for services of all components that will be installed during the installation process. You can apply one account for all services, but this is not recommended, for security reasons. Figure â Server Configuration Service Accounts tab To choose the collation of your instance, click the Collation tab of the same page. Collation defines the sorting behavior for your instance. You can either choose the default collations for the components that will be installed, or click Customize to select some other collations that are supported by the system. On the Database Engine Configuration page see Figure, you choose the authentication mode for your Database Engine system. As you already know, the Database Engine supports Windows authentication mode and Mixed mode. If you select the Windows Authentication Mode radio button, the Setup process creates the sa system administrator login, which is disabled by default. If you choose the Mixed Mode radio button, you must enter and confirm the system administrator login. Click Add Current User if you want to add one or more users that will have unrestricted access to the instance of the Database Engine. Figure â Database Engine Configuration Account Provisioning tab Note â You can change the information concerning account provisioning after installation. The other tab of the Database Engine Configuration page, Data Directories see Figure, allows you to specify the locations for all the directories in which Database Engineâ related files are stored. Figure â Database Engine Configuration Page 9
Data Directories tab What appears for the next step depends on whether or not you chose to install Analysis Services. If you did choose to install it, a page similar to Figure will appear for Analysis Services. Specify users that will have access to Analysis Services and click Next to continue. Similarly, what appears for the next step depends on whether or not you decided to install Reporting Services. If you indicated that Reporting Services should be installed, the Reporting Services Configuration page see Figure appears. On this page, you can decide just to install the report server without its configuration or to install and configure it. The third alternative is to integrate the report server with Microsoft Office SharePoint Server a server program that can be used to facilitate collaboration, provide content management features, and implement business processes. Figure â Reporting Services Configuration page On the Error Reporting page, specify the information, if any, that you would like to send to Microsoft automatically. Clear the check box if you do not want to take part in this automatic reporting. The next page, Installation Configuration Rules, is similar to the earlier page called Installation Rules. At the end of this step, the summary of all configuration rules will be displayed. The last page, before the installation process actually starts, is the Ready to Install page. This page allows you to review the summary of all SQL Server components that will be installed. To start the installation process, click Install. Setup shows you the progress of your installation process. If the installation process succeeds, click Next. At the end, the Complete page see Figure appears, with the location of the file in which the summary log is stored. Click Close to complete the installation process. After that, you can use all components that you installed during the installation process. Figure â Complete page. Chapter 8 : Step-By-Step: Creating a SQL Server AlwaysOn Availability Group â CANITPRO In this blog post I will be sharing step by step installation detail for SQL Server with Best Practice for SharePoint.. SQL Software requirements. bit edition of Microsoft SQL Server R2 or SQL Server /16 Standard (Enterprise required for Always On). Chapter 9 : Install SQL Server in Windows Server R2 The next step is the Install Setup Files step, where SQL Server Management Studio (SSMS) setup will download, extract and install all necessary setup files to your server. Step 6: Once SQL Server Management Studio (SSMS) setup is done with the install setup files, it verifies the setup support rules in order to proceed. Page 10