SQL Server 2016
20 TopicsChanges in SQL Server 2016 Checkpoint Behavior
First published on MSDN on Aug 03, 2016 Authored by Mike RuthruffReviewed by: Denzil Ribeiro, Mike Weiner, Arvind Shyamsundar, Sanjay Mishra, Murshed Zaman, Peter Byrne, Purvi ShahSQL Server 2016 introduces changes to the default behavior of checkpoint.4.5KViews0likes1CommentBulk Insert causing duplicates in target table
We use ETL tool(C# based) which uses Bulkcopy method to do bulk insert to target table. Recently we are facing 2 Issues in our daily loads 1. Target table with no primary key - the load returns success but it inserts 5x times of the same record. It loads same records 5 times. 2. Target table with Primary Key - The load returns failure with primary key constraint but it inserts the rows into target table. DBA Team is unable to find anything in there logs ,So I am confused why this error occurs. This occurs daily in 10% of the jobs and once you rerun after 2-3 hrs the same job finishes successfully without above mentioned issues. Please suggest how can I debug this issue.5.9KViews0likes3CommentsImprove query performance on memory optimized tables with Temporal using new index creation enhancement in SP1
First published on MSDN on Dec 08, 2016 Reviewed by: Dimitri Furman,Sanjay Mishra, Mike WeinerWith the introduction of the Temporal feature in SQL 2016 and Azure SQL Database, there is an ability to time travel through the state of data as it was at any given point of time.2.2KViews0likes0CommentsReal World Parallel INSERT...SELECT: What else you need to know!
First published on MSDN on Jul 21, 2016 Arvind ShyamsundarReviewed by: Gjorgji Gjeorgjievski, Sunil Agarwal, Vassilis Papadimos, Denzil Ribeiro, Mike Weiner, Mike Ruthruff, Murshed Zaman, Joe SackIn a previous post we have introduced you to the parallel INSERT operator in SQL Server 2016.15KViews0likes0CommentsCheckpoint process for memory-optimized tables in SQL 2016 and implications on the log
First published on MSDN on May 20, 2016 Reviewed by: Alejandro Saenz, Jos de Bruijn; Joe Sack, Mike Weiner,Kun Cheng, Raghavendra TK A durable memory-optimized table (created as SCHEMA_AND_DATA) will have it’s transactions recorded into the transaction log so that on failure, recovery is possible.5.1KViews0likes0CommentsConsiderations around validation errors 41305 and 41325 on memory optimized tables with foreign keys
First published on MSDN on Mar 24, 2016 Reviewed by: Jos de Bruijn; Joe Sack, Mike Weiner, Mike Ruthruff, Kun ChengTransactions on memory optimized tables in SQL Server 2014, SQL Server 2016 and Azure SQL Database are implemented with an optimistic concurrency model with multi-version concurrency control.2.1KViews0likes0CommentsSQL Server 2016 SSIS Data Flow Buffer Auto Sizing capability benefits data loading on Clustered Columnstore tables
First published on MSDN on Feb 29, 2016 Reviewers: Joe Sack, Arvind Shyamsundar, Murshed Zaman, Sanjay MishraThe focus of this blog is to introduce SSIS changes in the Data Flow task in SQL Server 2016 that help data loading into Columnstore tables.11KViews2likes0CommentsDatabase Restoring Status
Hi All, We are usingMicrosoft SQL Server 2016 (SP2) (KB4052908) - 13.0.5026.0 (X64) in our environment DB01 as a Primary and DB02 as a restoring mode RecentlyIhave checkedboth DB mdf files and these mdf files are different from each other DB01 mdf file size is 121GB and DB02 is 116 GB my query is how to check restoring mode is on working state or not what is the steps to check the status of Database restoring is it restoring successfully or not. Kindly response regarding this subject. Thanks in Advance. Best Regards Zahid1.3KViews0likes1CommentSQL Server 2016 crashes
Hey Guys, I am facing really weird issue with MS SQL 2016 crashes. Every so often there is a crash dump generated: SqlDumpExceptionHandler: Process 105 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. This information is very vague so you cannot really determine what is the cause of it. I was playing with the dump file a bit An I got into the module that is causing the crash: ntdll!NtWaitForSingleObject+0x14: 00007ffb`d5255ac4 c3 ret SQL is working the cluster with 4 nodes. Two nodes are in one site and two other nodes are in the second site. Network is working fine. There are no error logs inside the system event viewer or Failover Cluster operational logs. I have noticed that we are running on older version of ODBC drivers which is 17.3.1.1 and the newest one is 17.4.2.1. Do you think this might be related? Regards, Wojciech1.6KViews0likes0Comments