AlwaysOn Cluster Setup: Use the same account to run all SQL Server service for all node in the cluster. Account has Administrator permissions on all servers in node. Account has sysadmin SQL permission on all servers in node. Account has log on as service policy on all servers in node. Note: Always use SQL Server... » read more
Database State Definitions The following table defines the database states. State Definition ONLINE Database is available for access. The primary filegroup is online, although the undo phase of recovery may not have been completed. OFFLINE Database is unavailable. A database becomes offline by explicit user action and remains offline until additional user action is taken.... » read more
Example The set state command should be a fast process. If it takes a while, stop the process, restart server and SQL server, and then try again. <db_state_option> Controls the state of the database. OFFLINEThe database is closed, shut down cleanly, and marked offline. The database can’t be modified while it’s offline. ONLINEThe database is... » read more
Error: Cannot bring the Windows server fail over cluster (WSFC) resources online. (Error Code 5942). The WSFC service may not be running or may not be accessible in its currents states, or the WSFC resources may not be in a state that could accept the request. For information about this error code see “system error... » read more
Need the following… Host name of Listener, host name need to be setup first in AD Port, default to 1433 Network Mode, use Static IP IP Address, set to specific IP Address Note: For Network Mode, IP Address/Subnet are automatically detected using DHCP option. If you have a specific IP address, use Static IP option.... » read more
Cause: When your database partition is full, the Microsoft SQL server sets the status of the database that can no longer grow to “Recovery Pending”. This status means that SQL can’t open the database and can’t lock the database files. This status is comparable to a database in offline mode. Another cause is with problem... » read more
Primary reasons when an SQL Server Database is marked in Suspect Mode System Issues Transaction Log File is Missing SQL Server Crash Database Files are inaccessible SQL Server Database Operation Failures Due to Improper shut down of SQL Server System Due to Sudden Power Outage Low Disk Space Issues Hardware Failure Drives missing or not... » read more
Select Databases Select database. Database mush meet criteria. Database mode must be set to Full. Select Data Synchronization Three Options Available Full Join only Skip initial data synchronization Note: Option #1 of Data Synchronization is the easiest but require a backup to be made on the primary and a recovery on the secondary. Backup and... » read more
Setting up AlwaysOn High Availability involves setting up… Windows Failover Cluster via Windows Failover Cluster Manager SQL Server vis SQL Server Management Studio Prerequisite Make sure database has a full backup and recovery mode set to Full. Make sure the SQL Server service on each node has the proper permission on the server. (recommend using... » read more
Using SQL Server Configuration Manager To disable AlwaysOn Connect to the Windows Server Failover Clustering (WSFC) node that hosts the SQL Server instance where you want to disable AlwaysOn Availability Groups. On the Start menu, point to All Programs, point to Microsoft SQL Server 2014, point to Configuration Tools, and click SQL Server Configuration Manager. In SQL Server Configuration Manager, click SQL Server... » read more