WSFC Cluster Quorum Vote Configuration Not Recommended for AG

SQLServerF1

When you create an AlwaysOn availability group by using the New Availability Group Wizard in Microsoft SQL Server 2012, or when you are performing failover of the AlwaysON Availability Group (AG) every time you may receive a warning message as shows below

The current WSFC cluster quorum vote configuration is not recommended for this availability group.

The above error occurs due to various reasons. and one of which is missing windows OS patch KB 2494036 on all cluster nodes part of the AlwaysON Availability Groups. Verify and apply the mentioned patch and reboot the nodes and the issue should be resolved. However if the issue still persists even after this patch is applied on all the cluster nodes then apply latest Service Pack or Cumulative Update available for SQL Server 2012 or SQL Server 2014.

Starting with Windows Server 2008, failover clustering introduced node based voting where Windows Server Failover Clustering (WSFC) uses a majority of votes to establish a quorum for determining cluster membership. Votes are assigned to nodes in the cluster or to a witness that is either a disk or a file share witness. We can use the Configure Cluster Quorum Wizard to configure the clusters quorum model. When you configure a Node Majority, Node and Disk Majority, or Node and File Share Majority quorum model, all nodes in the cluster are each assigned one vote. However there are limitations to the votes for AlwaysON Availability Groups which involve SQL Server Clustered instance. If a  primary or a secondary replica is hosted by a Windows cluster then this replica is configured for an automatic failover without a vote. If this is by design then you may ignore the warning as it still allows the initial setup of AlwaysON Availability Groups and subsequent manual failover of AlwaysON Availability Groups, but the warning will appear each time you try to perform a manual failover.

Also it is possible to configure the votes for each node and customized as per the business requirement. This functionality helps with multi-site clusters where you may want one site to have more number of votes than other sites in a disaster recovery data center. By default all nodes in the cluster have one vote but administrators can change the vote functionality in the quorum model by configuring a particular node to have 0 votes.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Introduction of SQL Server Integration Services (SSIS)

SQLServerF1

Microsoft SQL Server Integration Services (SSIS) is a platform for building enterprise-level data integration and data transformations solutions. Integration Services solve complex business problems by copying or downloading files, sending e-mail messages in response to events, updating data warehouses, cleaning and mining data, and managing SQL Server objects and data. These packages can work alone or together with other packages to address all business needs. Integration Services can be used to perform extract and transform data from a wide variety of sources such as XML data files, flat files, and relational data sources, and then load the data into one or more destinations.

SQL Server Integration Services was introduced starting with SQL Server 2005, prior to that Data Transformation Services (DTS) was available. SQL Server Integration Services (SSIS) is mainly used to perform ETL operations which include Extract, Transform and Load.  ETL processing is commonly used for data warehousing (DW) applications, however it is not just limited to Data Warehouse applications, but can be used to satisfy various business solutions. We can use SQL Server Business Intelligence studio or Visual Studio to build the Sql Server Integration Services package and once developed and build, we can import it to any SQL Server using SQL Server Management Studio (SSMS) and use it through SQL Server jobs to execute regularly.

Integration Services includes a rich set of built-in tasks and transformations; tools for constructing packages; and the Integration Services service for running and managing packages. You can use the graphical Integration Services tools to create solutions without writing a single line of code; or you can program the extensive Integration Services object model to create packages programmatically and code custom tasks and other package objects.

Integration Services can connect to a wide variety of data sources, including multiple sources in a single package. A package can connect to relational databases by using .NET and OLE DB providers, and to many legacy databases by using ODBC drivers. It can also connect to flat files, Excel files, and Analysis Services projects. Integration Services includes source components that perform the work of extracting data from flat files, Excel spreadsheets, XML documents, and tables and views in relational databases from the data source to which the package connects. The data can be then transformed by using the transformations that Integration Services provides. The data can be transformed to compatible formats which can be merged physically into one dataset. After the data is merged successfully and transformations are applied to data, the data is usually loaded into one or more destinations. Integration Services includes destination for loading data into flat files, raw files, and relational databases. The data can also be loaded into an in-memory recordset and accessed by other package elements.

Some of the uses of SQL Server Integration Services include populating data into data warehouses and data marts, cleaning and standardizing the data, Building Business Intelligence into a Data Transformation Process, and Automating Administrative Functions and Data Loading, etc.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

TOP KNOWN ISSUES WITH MICROSOFT SQL SERVER 2014 CU4

SQLServerF1

You may receive below error on a table that contains non-unique indexes and when you run a query to update the table by using the bitmap index that contains a partition key
Msg 2601, Level 14, State 1, Line 1
Cannot insert duplicate key row in object <table name> with unique index <index name>. The duplicate key value is (0, <the value>).
The issue has been fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

You may receive below kind of deadlock error when parallelism is used at server or query level.
(Process ID 85) was deadlocked on thread | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
The issue was fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

Incorrect results may be returned when you use Option(Recompile) for queries inside a procedure and involves join to other tables and the joined table is updated from another transaction in SQL Server 2014
The issue was fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

When using SQL Server 2012 service broker as an initiator to send high number of messages to a remote target, a race condition might occur leading to an access violation and deadlocked schedulers and may cause service broker to stop working.
The issue was fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

When a query is run which contains common language runtime (CLR) functions in the WHERE clause against an indexed view, may cause an fatal exception and that session may get disconnected.
The issue was fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

When manual failover is performed on a mirrored database, you may notice that database takes a long time to recover and to come online on the new Principal server or the database stays in “In Recovery” status for a long time and does not assume the role of the mirror database on the new mirror server and at the same time, the new Principal database may also get into “Principal, Disconnected” state.
The issue was fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

In Merge replication when a custom stored procedure resolver is used to resolve conflicts, there may be additional characters added to the character type data after conflict resolution. Also the merge agent may fail and following error may be logged in the replmerg.log file
ERROR: ErrNo = 0x8004565a, ErrSrc = <null>, ErrType = 8, ErrStr = The Merge Agent failed because the schema of the article at the Publisher does not match the schema of the article at the Subscriber. This can occur when there are pending DDL changes waiting to be applied at the Subscriber. Restart the Merge Agent to apply the DDL changes and synchronize the subscription.
The issue was fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

With release of each new version and new service packs of SQL Server, new issues or bugs will surface and Microsoft will work on fixing high priority bugs. Above are some of the top known issues which were identified and fixed in Microsoft SQL Server 2014 CU4.

This is applicable on below versions of SQL Server

SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.