Abstract

It is important for any organization to handle increase in data; normally this is the job of the DBA in organization to take care of this data growth, along with its protection and its availability. High availability of data is also most important for organizations, for that purpose, shared storage is usually the solution, for example, SAN or NAS storage as Microsoft Cluster Database instances. Mostly Organization does not have shared storage in their infrastructure, which was required for Microsoft cluster SQL database instance; due to that they used other native methods to implement like log shipping or database mirroring, which was not efficient method for high-availability and disaster-recovery solution. After that, Microsoft introduced native method called SQL AlwaysOn method that could be implemented without using SAN and NAS storage method to implement high availability and disaster recovery without using shared storage. SQL AlwaysOn option is using only Microsoft cluster service and shared folder between the nodes. This paper written for DBA and System Administrators; and is implementation of Microsoft SQL Database tier step by step.

Highlights

  • AlwaysOn is native method of Microsoft SQL Server which are giving availability of the SQL database instance and remote running SQL database instance in case of any disaster recovery (Hayat & Soomro, 2016; Nawaz & Soomro, 2013; Weiner, Mishra, & He, 2011)

  • Microsoft SQL AlwaysOn is providing following features and capabilities (Ozar, 2010; Otey, 2011): yy Allowing backups on a secondary replica yy Creating up to 4 secondary replicas yy Employing Built-in Compression and Encryption yy Performing DBCC statements in contrast to a secondary replica yy Providing both Synchronous and Asynchronous mirroring yy Providing a logical grouping of similar databases using Availability Groups yy Using database mirroring over TCP/IP yy Using window cluster services required to make failover or failback without shared storage

  • On the initial step, setting up the basic configuration of cluster services is needed, for example, adding the Windows Failover Cluster Feature and adding cluster group to all the machines running the SQL Server instances that needed to be configured as replicas

Read more

Summary

INTRODUCTION

AlwaysOn is native method of Microsoft SQL Server which are giving availability of the SQL database instance and remote running SQL database instance in case of any disaster recovery (Hayat & Soomro, 2016; Nawaz & Soomro, 2013; Weiner, Mishra, & He, 2011). Using native SQL Server feature failover clustering, which provided as availability group and administrative GUI interface to monitor the availability group status . Microsoft SQL AlwaysOn is providing following features and capabilities (Ozar, 2010; Otey, 2011): yy Allowing backups on a secondary replica yy Creating up to 4 secondary replicas yy Employing Built-in Compression and Encryption yy Performing DBCC statements in contrast to a secondary replica yy Providing both Synchronous and Asynchronous mirroring yy Providing a logical grouping of similar databases using Availability Groups yy Using database mirroring over TCP/IP yy Using window cluster services required to make failover or failback without shared storage. This paper is organized as follows; section 2 material and methods will explore virtual lab environment, software requirements, hardware requirements and step by step installation and configurations; section 3 will discuss findings of this paper; and section 4 will conclude with discussions and future work

MATERIAL AND METHODS
It will ask to reboot the SQL service
RESULTS & FINDINGS
Discussion & Future
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.