List of Bugs Fixed in SQL Server 2014 CU2 – Part 3

SQLServerF1

With every release of SQL Server product or subsequent service packs or Cumulative updates, new bugs are encountered or discovered. Below are some of the bugs which were fixed with the release of Cumulative update package (CU) 2 for Microsoft SQL Server 2014.

KB Article 2960735
SQL Server 2014 bug FIX: Windows Update for SQL Server 2012 or SQL Server 2014 image does not work in Windows Azure Virtual Machine gallery Setup & Install
KB Article 2960989
SQL Server 2014 bug FIX: Error when you use DQS Cleansing component with large batch in an SSIS 2012 or SSIS 2014 package DQS
KB Article 2961254
SQL Server 2014 bug FIX: The execution of an MDX query in SSAS 2012 or SSAS 2014 is much slower than it is in SSAS 2008 R2 Analysis Services

KB Article 2961258
SQL Server 2014 bug FIX: Cannot access the data in FileTable after you upgrade from SQL Server 2012 SP1 to SQL Server 2014 SQL service
KB Article 2962650
SQL Server 2014 bug FIX: Access violation occurs when running a Process Recalc on a tabular table in SSAS 2012 or SSAS 2014 Analysis Services
KB Article 2963408
SQL Server 2014 bug FIX: Error 5180 occurs when you query BLOB column data in SQL Server SQL service
KB Article 2966096
SQL Server 2014 bug FIX: Access violation when you insert data into a table that has a clustered columnstore index in SQL Server 2014 SQL service
KB Article 2967198
SQL Server 2014 bug FIX: DBCC SHRINKDATABASE or DBCC SHRINKFILE cannot move pages that belong to the nonclustered columnstore index SQL service
KB Article 2967240
SQL Server 2014 bug FIX: Cannot reclaim unused space by using shrink operation in the table that contains a LOB column in SQL Server SQL service
KB Article 2967634
SQL Server 2014 bug FIX: SSIS 2012 or SSIS 2014 XML validator only outputs “TRUE” or “FALSE” when you perform XML validation Integration Services

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2014

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

 

List of Bugs Fixed in SQL Server 2014 CU2 – Part 2

SQLServerF1

With every release of SQL Server product or subsequent service packs or Cumulative updates, new bugs are encountered or discovered. Below are some of the bugs which were fixed with the release of Cumulative update package (CU) 2 for Microsoft SQL Server 2014.

KB Article 2939277
SQL Server 2014 bug FIX: Incorrect results when you run queries that contain UNION operator by using parallel query plan in SQL Server SQL performance
KB Article 2950189
SQL Server 2014 bug FIX: An access violation occurs when you execute update query on a table that has a DML trigger in SQL Server SQL performance
KB Article 2950209
SQL Server 2014 bug FIX: Access violation when the start offset is larger than the string length in Substring function in SQL Server SQL service
KB Article 2952101
SQL Server 2014 bug FIX: Poor cardinality estimation when the ascending key column is branded as stationary in SQL Server SQL performance
KB Article 2953354

SQL Server 2014 bug FIX: Log Reader Agent fails when you have Oracle Publishing configured in SQL Server SQL service
KB Article 2954480
SQL Server 2014 bug FIX: SSAS instance crashes when you perform writeback action by using the role with cell security defined Analysis Services
KB Article 2956619
SQL Server 2014 bug FIX: The execution of an SSIS package that is stored in MSDB is slower than it is stored on the file system Integration Services
KB Article 2958062
SQL Server 2014 bug FIX: Error 515 when you add a subscription and then delete it in SQL Server 2012 or SQL Server 2014 SQL service
KB Article 2960237
SQL Server 2014 bug FIX: Error when you execute DQS stored procedure [internal_core].[RestoreDQDatabases] in SQL Server Data Quality Services (DQS)
KB Article 2960310
SQL Server 2014 bug FIX: Access violation when you maintain RBS with the .NET Framework 4.0 in related configuration file in SQL Server

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2014

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

 

Enhancements in SQL Server 2014 for Availability and Disaster Recovery

SQLServerF1

There has been few new versions of SQL Server released of recent which include SQL Server 2012 and the latest being SQL Server 2014. There are many new features introduced with SQL Server 2014 and there has been many enhancements to the existing features of database engine, SSRS, SSIS and SSAS. Below are list of some of the important Enhancements in SQL Server 2014 for Availability and Disaster Recovery.

Enhancements to Always On Availability Groups which now support up to 8 replicas instead of 4 as in SQL Server 2012. If primary replica or quorum is unavailable, then the secondary replica will still be available as read-only, instead of the Availability group going offline as in SQL Server 2012. Also, now Availability Groups can use SQL Azure for DR purposes rather than creating a secondary Data Centre just for that. Also, SQL Server 2014 allows the hosting of Availability Group data files in Azure, hosting an entire replica in a Windows Azure VM, and performing backups to a URL to store in Windows Azure Blob Storage. Failover cluster instances (FCIs) can now use Cluster Shared Volumes (CSVs) as cluster shared disks. Many new New DMVs and functions have been introduced with SQL Server 2014.

There are also few security enhancements like Native Backup Encryption which allows DBAs to get rid of the 3-rd party tools with same functionality. Connect Any Database permission allows a login to connect to any database existing or future without having to configure connect privileges on every database Impersonate Any Login allows a login to impersonate any other login, without giving them sysadmin privileges. Also it can use be used to deny impersonation even for logins that inherently have the right to do so. Select All User Securables allows SELECT, but not INSERT/UPDATE/DELETE/MERGE permissions on all user tables in all user databases. Useful for auditors or anyone who needs a read only role across all databases, without having to configure things like db_datareader or individual object-level permissions in every database.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2014

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

 

Performance Enhancements in SQL Server 2014

SQLServerF1

There has been few new versions of SQL Server released of recent which include SQL Server 2012 and the latest being SQL Server 2014. There are many new features introduced with SQL Server 2014 and there has been many enhancements to the existing features of database engine, SSRS, SSIS and SSAS. Below are list of some of the important Performance Enhancements in SQL Server 2014.

The most important and most talked feature in SQL Server 2014 is In-memory OLTP, which is a new lock-free, latch-free, optimistic concurrency approach of storing the user data in memory. In some specific scenarios the improvement in performance and/or throughput can be about 40x. Another important feature is Transactions with Delayed Durability. A delayed durable transaction returns control to the client before the transaction log record is written to disk which may increase the transaction performance significantly. Durability can be controlled at the database level, COMMIT level, or ATOMIC block level.

Other enhancements include support of up to 640 cores and 4 TB of RAM on a physical box, however this limit may be lower in a virtual machine, due to operating system and Hyper-V limitations, not SQL Server itself.
Another enhancement is reduction of eager writes to tempdb. The database engine will try to defer or completely avoid any physical writes of data that it assumes will be transient and short-lived. This means less writes in tempdb. There have been significant Improvements to the SQL Server Query Optimizer which include improvement of the component of the database engine that creates and optimizes query plans.
Another improvement include support of clustered columnstore indexes, also many of the data type limitations have been removed, and the index is now writable. New archival compression algorithm, with a much greater compression rate at a slightly higher CPU cost though.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2014

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

 

Reasons to upgrade to SQL Server 2014

SQLServerF1

There has been quite few new SQL Server versions released frequently since the launch of SQL Server 2008. Currently the most used versions in most of the organizations are SQL Server 2005, SQL Server 2008 R2 and BDAs or organizations have been planning to upgrade from these versions to next higher version SQL Server 2012, however there has been another new release which is SQL Server 2014. Now there could be confusion about upgrading to which version? should we upgrade from SQL Server 2005/2008 R2 to SQL Server 2012 or 2014?

If you are planning to upgrade to higher version, then it is advisable to go with the latest release of SQL Server 2014, by skipping SQL Server 2012, as you can avoid use this version for longer time and there will be no need for another upgrade in few years, instead we can run with SQL Server 2014 for many years. Along with this there are also few other things which will prove to go ahead with SQL Server 2014 instead of SQL Server 2012, which include the license cost, which is almost same for both SQL Server 2012 and SQL Server 2014. Another important thing is that the end of life cycle date is far to ahead, so there is no force to upgrade to higher versions atleast for next 10+ years, unless we want to use any particular latest feature.

By upgrading directly to SQL Server 2014, you can get chance to use new features of SQL Server 2014 like In-Memory-OLTP, etc and also there are many enhancements to features like AlwaysON and also there are many enhancements to BI technology like SSAS, SSRS and SSIS. So, if you are planning to upgrade, it is better to prefer to go ahead with the latest releases always and in this case it is SQL Server 2014.

Hope this was helpful.

This is applicable for below versions of SQL Server

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

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

 
1 2