SQLSweet16!, Episode 10: "I can eat glass …", but can I load it into a database?
First published on MSDN on Oct 19, 2016 Authored by Sanjay MishraSanjay MishraReviewed By: Dimitri Furman, Murshed Zaman, Kun Cheng If you have tried to use BULK INSERT or bcp utilities to load UTF-8 data into a table in SQL Server 2014 or in an earlier release (SQL Server 2008 or later), you have likely received the following error message:Msg 2775, Level 16, State 13, Line 14The code page 65001 is not supported by the server.SQLSweet16!, Episode 9: Scripting Always Encrypted operations
First published on MSDN on Oct 07, 2016 Authored by Sanjay MishraAuthors: Arvind Shyamsundar, Sanjay Mishra, Subodh Patil (iCertis), Mukesh Singh (iCertis), Ravi Kumar (iCertis)Reviewers: Dimitri Furman, Benjin Dubishar, Raghav Kaushik, Jakub SzymaszekAlways Encrypted is one of the highly acclaimed features in SQL Server 2016.SQLSweet16!, Episode 8: How SQL Server 2016 Cumulative Update 2 (CU2) can improve performance of highly concurrent workloads
First published on MSDN on Sep 29, 2016 Sanjay Mishra, Arvind ShyamsundarReviewed by: Dimitri Furman, Denzil Ribeiro, Mike Ruthruff, Mike Weiner, Ryan Stonecipher, Nitish Upreti, Panagiotis Antonopoulos, Mirek SztajnoLast year, in the SQLCAT lab we were working with an early adopter customer running pre-release SQL Server 2016 on Windows Server 2016 Tech Preview 4.SQLSweet16!, Episode 2: Availability Groups Automatic Seeding
First published on MSDN on Jun 28, 2016 Authored by Sanjay MishraReviewed by: Denzil Ribeiro, Murshed Zaman, Mike Weiner, Kun Cheng, Luis Vargas, Girish Mittur V, Arvind Shyamsundar, Mike RuthruffIf you have been using Availability Groups (or Database Mirroring prior to that), you are probably used to backing up the primary and restoring (with norecovery) the secondary (first a full database backup, followed by transaction log backups) for creating an Availability Group (AG).
