Cluster Server 8.0 Implementation Guide for Microsoft SQL Server - Windows
- Section I. Introducing Veritas InfoScale solutions for application high availability
- Understanding the InfoScale solutions for application high availability
- About the VCS agents for SQL Server
- How VCS monitors storage components
- How application availability is achieved in a physical environment
- How is application availability achieved in a VMware virtual environment
- Managing storage and installing the VCS agents
- Installing SQL Server
- Understanding the InfoScale solutions for application high availability
- Section II. Configuring SQL Server in a physical environment
- Overview
- Configuring the VCS cluster
- Configuring the SQL Server service group
- Configuring a SQL Server service group using the wizard
- Making SQL Server user-defined databases highly available
- Verifying the service group configuration
- Administering a SQL Server service group
- Configuring an MSDTC service group
- Configuring the standalone SQL Server
- Configuring an Active/Active cluster
- Configuring a disaster recovery setup
- Section III. Configuring SQL Server in a VMware environment
- Configuring application monitoring using the Veritas High Availability solution
- Administering application monitoring
- Administering application monitoring using the Veritas High Availability tab
- Administering application availability using Veritas High Availability dashboard
- Understanding the dashboard work area
- Section IV. Appendixes
- Appendix A. Troubleshooting
- Error and warning messages from VCS agent for SQL Server
- Troubleshooting application monitoring configuration issues
- Troubleshooting Veritas High Availability view issues
- Appendix B. Using the virtual MMC viewer
- Appendix A. Troubleshooting
Assigning privileges to the existing SQL Server databases and logs
Note:
The following steps are required only if you have configured the SQL cluster account while creating the SQL Server service group earlier.
While installing SQL Server, if the user account specified for the SQL Server services is not a member of the local administrators group, then the SQL services and databases may not be accessible after a service group failover. For such a case, you configure the SQL cluster account while creating the SQL Server service group.
The SQL cluster account gets full control privileges to all the new databases and log files that are created after the service group is configured.
However, if databases were created before the service group is configured, you have to manually assign the SQL cluster account with full control privileges to the existing databases and log files associated with the instances in the service group.
To assign privileges to the existing SQL databases and logs
- On the node where the SQL Server service group is online, navigate to the following directory from Windows explorer:
<Datarootdirectory>\<SQLinstancename>\MSSQL\
The directory contains various directories including DATA, FTData, JOBS, Log, repldata.
Here, <Datarootdirectory> is the path that you specified while installing SQL Server.
- Assign the SQL Cluster account with full control privileges to the following directories:
DATA
Log
- Navigate inside the DATA folder and then assign the SQL cluster account with full control privileges to the following files in that directory:
tempdb.mdf
templog.ldf
- Repeat these steps for all the instances that are configured in the SQL Server service group.
This ensures the existing SQL databases are accessible after a service group failover.