Sql Server Failover Clustering

Front 1

Full-Text Queries - failover clustering requirements

Back 1

1. SQL server must run on same system account on all failover cluster nodes. (general requirement for all failover clustering)
2. To change the startup account for sql server in the failover cluster, you must use sql server configuration manager. Using the control panel or services will break the full-text configuration

Front 2

SQL server configuration manager - failover clustering reqs

Back 2

1. To change the startup account for SQL Server in the failover cluster, you must use SQL Server Configuration Manager. If you use Control Panel or the Services Application in Windows, you might break your server configuration.
2. When creating or altering databases, you can only view the cluster disks for the local failover cluster instance.
3. you must manually restart full - text an sql server agent after resetting the the SQL service account restart.

Front 3

Management Studio - fail over clustering reqs

Back 3

1. If you are browsing a table using SQL Server Management Studio and lose the connection to SQL Server during a failover, you see the error message, "Communication Link Failure." You must press the ESC key to undo the changes and exit out of the SQL Server Management Studio window.
You cannot run a query, save any changes, or edit the grid.

Front 4

SQL server profiler - fail over clustering reqs

Back 4

1. You can use SQL Server Profiler with failover clustering. However, if a failover occurs when you are running a SQL Server Profiler trace, you must restart the trace after the server comes back online.

Front 5

Service Control Manager - fail over clustering reqs

Back 5

1. Use Service Control Manager to start or stop a clustered instance of SQL Server. You cannot pause a clustered instance of SQL Server.

Front 6

SQL Mail - fail over clustering reqs

Back 6

1. SQL mail can be configured remotely by Configuration Manager.