SQL Server 2014 Developer Edition is Free From Now

As a DBA or Developers it is important to have a SQL Server instance to be able to install and use it to understand the working and usage for the applications. So far, DBAs mostly rely on the free Evaluation edition of SQL Server provided by the Microsoft team. This Evaluation edition expires after 180 days, after which we need to purchase a license and upgrade the Evaluation edition to licensed edition depending on our requirement. Microsoft offers different editions for different purposes, like Enterprise edition for important and critical production applications, Standard edition for less critical applications to reduce the cost of the licensing, Developer edition specifically for developers for development and unit testing the applications before moving to production environment. Previously, most developers preferred buying developer edition as the cost is less and is is specifically released for the purpose and it consists of all features available in enterprise edition and also it could be easily upgraded to enterprise edition if required.

Starting with SQL Server 2014, Microsoft has made a decision to make the SQL Server developer edition free of cost for the developers through Visual Studio Dev Essentials members. Once you login as Visual Studio Dev Essentials members, you will be able to download the SQL Server Developer edition and use it for free of cost. This decision was taken inorder for developers to leverage the capabilities that SQL Server 2014 and higher has to offer for their applications and also this is considered as another step for making SQL Server more accessible to the users which helps in spreading the SQL Server in more companies. However, it is important to keep in mind that SQL Server Developer Edition is still specifically for development and testing purposes only, and not to be used in production environments or not to be used with any production data.

Few important things to keep in mind are below.
– This only includes SQL Server Developer Edition and does not include Operating System license or license for any other products.
– SQL Server 2016 developer edition is also will be made available free under same program and this will mostly be continued with the future releases of SQL Server.

In case you are not part of Visual Studio Dev Essentials members, then you may either buy SQL Server developer edition or can try other options available in the market like SQL Server Evaluation edition. If the application is small and not so critical, you may even choose trying SQL Server Express edition. Hope you will get your free developer edition and explore the new features available like InMemory OLTP and other features.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2014
SQL Server 2016

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

 

SQL Server Cumulative Updates are More Stable to Install

Microsoft releases various service packs, cumulative updates, hotfixes for SQL Server to fix any bugs or known issues. Each of these serves different purposes. For example hotfixes address specific bug or issue and released when a customer opens a case with Microsoft and issue identified as bug, then hoxfix will be released to rectify the specific issue. So, DBAs are required to only apply the hotfix if they are facing that issue. Cumulative updates contain more number of fixes which include multiple hotfixes and additional bug fixes raised by customers. Service Packs are more higher level and contain all service packs, cumulative updates released so for for that version of SQL Server.

With each release of SQL Server version, Microsoft has been making various improvements to the product and the process based on the feedback received from the customers. For example, since SQL Server 2008, Microsoft has allowed possibility of uninstalling service packs, thus providing a better and easier way of rollback in case something goes wrong after applying the patch. Now in year 2016, Microsoft has come up with approach of recommending to install latest available service pack or cumulative update and stated that both of these will be stable as the level of testing done will be same. Previously, in DBA community, there has been assumption that service packs are more stable compared to cumulative updates, as service packs contain more fixes and tested thoroughly and thought that CUs are not tested as thoroughly as SPs.

Now with the article, Microsoft has made it clear that even service packs going forward from year 2016 are stable and recommends to install them as soon as they are available, similar to how DBAs react to release of service packs. This is due to change in the way the service packs and cumulative updates are created and tested. Microsoft has made effort to update the KB articles to reflect the same. Previously, the KB articles used to have message that “This cumulative package is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems.”, which made many customer back down from applying the cumulative updates, but now they are updating the message with “we now recommend ongoing, proactive installation of CU’s as they become available.”

This change was welcomed by the DBA community where it makes it easier to convince the management to go ahead with applying the latest updates available from Microsoft whether it is a service pack or a cumulative update. Hope, with coming years there will be many more changes which not only improves the product, but also improves the processes.

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
SQL Server 2016

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 CU4 – Part 5

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) 4 for Microsoft SQL Server 2014.

MSDN Support KB Article 2993483
FIX: SSAS processing fails when you perform a Process Full operation on many partitions in a transaction
MSDN Support KB Article 2993529
FIX: Business rule validation fails with collation mismatch error in SQL Server 2012 or SQL Server 2014 MDS
MSDN Support KB Article 2996629
FIX: “String data, right truncation” error when you do bulk copy on DBCS by using ODBC Driver 11 in SQL Server 2014
MSDN Support KB Article 2998301
FIX: Error 8654 when you run “INSERT INTO … SELECT” on a table with clustered columnstore index in SQL Server 2014
MSDN Support KB Article 2999308
Add detailed information to the “Call to Excel Services returned an error” error message in SQL Server 2014 PowerPivot

MSDN Support KB Article 3003023
FIX: Schema lock occurs on a table with large data when you delete lots of rows from it in SQL Server 2014
MSDN Support KB Article 3003755
FIX: “SQL Server edition is not supported by MDS” error when you use MDS after you apply the CU3 for SQL Server 2014
MSDN Support KB Article 3003760
FIX: Cannot remove the secondary filegroup after you upgrade the database to SQL Server 2014
MSDN Support KB Article 3003804
FIX: Error when you export data cleansing result with the “Data and Cleansing Info” option in SQL Server 2014
MSDN Support KB Article 3004195
FIX: “sp_send_dbmail” stored procedure truncates email attachments to 64 KB in SQL Server 2014
MSDN Support KB Article 3007873
An update to add an “Open in Management Portal” item to the context menu for SQL Azure database nodes in SSMS 2014
MSDN Support KB Article 3007905
An update to the template script for creating SQL Azure database in SSMS 2014
MSDN Support KB Article 3008282
An update to add new service tier and performance level to the “Import Data-tier Application…” wizard
MSDN Support KB Article 2993859
FIX: “Unexpected termination” error in SQL Server Agent job that schedules an SSIS 2014 package running every minute

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 CU4 – Part 4

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) 4 for Microsoft SQL Server 2014.

KB Article 2988166
FIX: Additional semicolons are added to object definition when you run Invoke-Sqlcmd in SQL Server Management Tools
KB Article 2989002
FIX: Tasks shift to upper-left corner when you move or resize them while designing a maintenance plan in SSMS 2014 Integration Services
KB Article 2989043
FIX: Access denied when you try to view report history on a SharePoint site with the View Items permission Reporting Services

KB Article 2989512
FIX: MDX query returns no result when the cache is not cleared after you run a previous query in OLAP or tabular model Analysis Services
KB Article 2989590
FIX: Except function does not return the calculated member that is created at the ALL member level in SSAS Analysis Services
KB Article 2989810
FIX: Error in bcp_init when you do bulk copy with local temp table as input parameter in SQL Server Native Client 11.0 SQL service
KB Article 2990152
FIX: Unexpected Simplified Chinese characters appear in TextData field of Distributed Replay trace in SQL Server Management Tools
KB Article 2991526
FIX: SSIS 2012 or SSIS 2014 XML Source task cannot load data from a URI Integration Services
KB Article 2992414
FIX: Error in SQL task with IsQueryStoredProcedure set to True when you use .NET Data Provider for Teradata in SSIS Integration Services
KB Article 2993262
FIX: Some rows are missing in the result when you run query to select data from Oracle linked server by using merge join

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 CU4 – 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) 4 for Microsoft SQL Server 2014.

KB Article 2976861
FIX: The time is longer and longer to perform process full on an SSAS 2012 or SSAS 2014 tabular model database Analysis Services
KB Article 2976953
FIX: The DAX query with filter returns incorrect result after you run a DAX query without any filters in SSAS 2012 or in SSAS 2014 Analysis Services
KB Article 2979304
FIX: Error when you run RBS Maintainer in SQL Server 2012 or SQL Server 2014 SQL service

KB Article 2980208
FIX: Permissions cannot be propagated to Subscriber in transaction replication when the Distributor is SQL Server SQL service
KB Article 2980395
FIX: A severe error occurs when you run a query that uses CTEs against the partitioned tables in SQL Server SQL performance
KB Article 2982544
FIX: Slow to access “Explorer” or “System Administration” on MDM home page Data Quality Services (DQS)
KB Article 2986627
FIX: UPDATE STATISTICS performs incorrect sampling and processing for a table with columnstore index in SQL Server SQL performance
KB Article 2986722
FIX: Error 7105 when you execute UPDATE on sparse column set while ONLINE INDEX REBUILD is running on the same table in SQL Server SQL performance
KB Article 2987809
FIX: Report format is misaligned when you view the report that has certain report items in Internet Explorer 11 Reporting Services
KB Article 2987935
FIX: Long wait on CLR_CRST when you execute spatial query that is under heavy load 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

 

List of Bugs Fixed in SQL Server 2014 CU4 – Part 1

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) 4 for Microsoft SQL Server 2014.

KB Article 2924996
FIX: Issues when you export a report to PDF that has Unicode fonts in SQL Server Reporting Services
KB Article 2962767
FIX: “Cannot insert duplicate key” error occurs when you update a table by using a bitmap index that contains a partition key in SQL Server SQL performance
KB Article 2963137
FIX: Incorrect result is returned when you query multiple dimension members in MDX and DAX in SSAS 2012 or SSAS 2014 Analysis Services

KB Article 2963138
FIX: Parallel deadlock or self-deadlock occurs when you run a query that results in parallelism in SQL Server SQL service
KB Article 2965069
FIX: Incorrect result when you execute a query that uses WITH RECOMPILE option in SQL Server 2012 or SQL Server 2014 SQL performance
KB Article 2965654
FIX: SSRS 2012 or SSRS 2014 report is cut horizontally after you apply Update MS13-088 on a computer Reporting Services
KB Article 2965922
FIX: Issue when you configure scheduled data refresh for the PowerPivot workbook in SharePoint 2013 BI Azure
KB Article 2967103
FIX: Service broker stops working when you unregister and remove a session in SQL Server SQL service
KB Article 2967594
FIX: Fatal exception when you run a query that contains CLR functions against an indexed view in SQL Server SQL service
KB Article 2970421
FIX: The database sticks in role configuration phase when you perform a manual failover of a mirrored 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

 

List of Bugs Fixed in SQL Server 2014 CU3 – 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) 3 for Microsoft SQL Server 2014.

KB Article 2978472
FIX: UPDATE or INSERT statement on CCI makes sys.partitions not match actual row count in SQL Server 2014 SQL service
KB Article 2979121
FIX: Log Reader Agent fails when you upgrade from SQL Server 2008 to SQL Server 2012 or SQL Server 2014 SQL service
KB Article 2979587
FIX: Image completion setup fails when you use SysPrep to install localized version of SQL Server Setup & Install
KB Article 2981764
FIX: Cannot create indexed view on a clustered columnstore index and BCP on the table fails in SQL Server 2014 SQL service

KB Article 2984628
FIX: Auto-statistics creation increases the compilation time for natively compiled stored procedure in SQL Server 2014 In-Memory OLTP
KB Article 2984629
FIX: LCK_M_SCH_M occurs when you access memory-optimized table variables outside natively compiled stored procedures In-Memory OLTP
KB Article 2984907
FIX: “The current SQL Server edition is not supported by MDS” error when you browse to the MDS website DQS
KB Article 2986081
FIX: An access violation occurs when you use UPDATE STATISTICS on a computed column in SQL Server 2014 SQL performance
KB Article 2988552
Update enables SQLDOM to support “service_objective” in the Microsoft Azure SQL Database SQL service
KB Article 2989704
FIX: Some columns in sys.column_store_segments view show NULL value when the table has non-dbo schema in SQL Server 2014

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 CU3 – 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) 3 for Microsoft SQL Server 2014.

KB Article 2963668
FIX: w3wp.exe process crashes during merge replication with SQL Server Compact subscribers and precomputed partitions
KB Article 2963836
FIX: “Parameter missing value” error when you use a drillthrough report in SharePoint in SSRS 2012 or SSRS 2014
KB Article 2967635
FIX: Incorrect DBA reference of business rules after you upgrade SQL Server 2008 R2 MDS to SQL Server 2012 MDS or SQL Server 2014 MDS
KB Article 2968418
FIX: “Non-yielding scheduler” error when you insert or update many rows in one transaction in SQL Server 2014

KB Article 2968909
FIX: Access violation when you query sys.extended_properties table in SQL Server 2012 or SQL Server 2014
KB Article 2973561
FIX: Error when you insert a record into a FileTable or FILESTREAM in SQL Server 2012 or SQL Server 2014
KB Article 2975322
FIX: Blank value is set to NULL value in a business rule in MDS of SQL Server 2012 or SQL Server 2014
KB Article 2975402
FIX: Log Reader Agent crashes during initialization when you use transactional replication in SQL Server
KB Article 2975434
FIX: Error when you complete an SSAS 2014 image after specifying a non-default root directory
KB Article 2977312
FIX: Incorrect result when you use LIKE pattern to match the Japanese repeat character (Cho-On) 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

 

List of Bugs Fixed in SQL Server 2014 CU3 – Part 1

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) 3 for Microsoft SQL Server 2014.

KB Article 2936984
FIX: “Failed to generate dynamic snapshot” when you call sp_MScreatemergedynamicsnapshot in SQL Server
KB Article 2952444
FIX: Poor performance when you use table variables in SQL Server 2012 or SQL Server 2014
KB Article 2954861
FIX: “Query Timeout Expired” when you preview a command of an SSIS package in SSDT
KB Article 2957768
FIX: Excel rendering extension produces corrupted files when rendering a NaN or Infinity value in SSRS 2012 or SSRS 2014

KB Article 2957957
FIX: Attributes sort incorrectly after you use the Attribute Properties function in SQL Server MDS Add-in for Excel
KB Article 2959342
FIX: Data-driven subscription can’t be created when the driving query takes longer than 30 seconds to execute in SQL Server
KB Article 2960924
FIX: Cannot open the memory-optimized table template remotely in SQL Server 2014
KB Article 2961559
FIX: Incorrect folder when deploying SQL Server 2012 or SQL Server 2014 PowerPivot solutions by using SharePoint 2013 Central Admin
KB Article 2963372
FIX: Sub-total of calculated measure is incorrect (non-filtered) when you execute MDX query in SSAS 2012 or SSAS 2014
KB Article 2963386
FIX: SSRS 2012 or SSRS 2014 fails with IsolatedStorageException when subscriptions exported to Excel worksheets are larger than 10 MB

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

 
1 2 3 4