What is the impact of setting SET ANSI_WARNINGS OFF?
Setting ANSI_WARNINGS OFF to avoid NULL value elimination warnings can have an impact on the data quality and system behaviour.
2018-09-11 (first published: 2016-08-23)
29,630 reads
Nakul Vachhrajani
- Twitter: @sqltwins
- Website: https://nakulvachhrajani.com/
- LinkedIn: https://www.linkedin.com/in/nakulvachhrajani/
SSIS: Case sensitivity may expose issues with change deployment
Because SSIS is case sensitive, random VS_NEEDSNEWMETADATA errors on case-insensitive databases may indicate issues in your database change management & deployment process.
2016-02-11
2,454 reads
SQL Server Stored Procedures and SET options
SET options on stored Procedures work a bit different when compared with ad-hoc queries. These differences in behavior are often overlooked when developing the procedures and generating deployment scripts. This mistake can lead to undesired behavior in the application.
2015-10-02 (first published: 2013-08-29)
20,274 reads
Leveraging Constraint Evaluation Sequence in SQL Server
Constraints on a table in SQL Server are evaluated in a specific sequence. Knowing this sequence can help us leverage them to realize various business requirements.
2014-01-27
2,939 reads
HASHBYTES: Is CHECKSUM really required?
When compared with HASHBYTES, CHECKSUM, has a number of drawbacks. Hence, a question that comes up is: Is Checksum really required? In this article, I attempt to answer that question.
2013-03-27
8,227 reads
Deleting large number of rows from a table in a VLDB
For enterprise systems, purging data is a reality. Today, we will see some strategies that I recently implemented to make this process work efficiently.
2013-03-08 (first published: 2011-03-24)
24,396 reads
An in-depth look at change detection in SQL Server - Part 02
Auditing, conflict resolution, tamper & concurrency protection are some of the most common requirements for any enterprise system – this 2-part series presents an in-depth look at the various change detection mechanisms available within SQL Server.
2013-02-19
8,371 reads
An in-depth look at change detection in SQL Server - Part 01
Auditing, conflict resolution, tamper & concurrency protection are some of the most common requirements for any enterprise system – this 2-part series presents an in-depth look at the various change detection mechanisms available within SQL Server.
2013-02-12
5,370 reads
Never update systems tables directly - a study in Agent job scheduling
It is often recommended that system tables should not be updated directly. Presenting a case in point built around nightly job configuration in order to demonstrate the possible issues with updating system tables directly.
2012-09-17
5,671 reads
2012-06-13
2,419 reads
Blogs
Advice I Like: Art
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
Why Optimize CPU for RDS SQL Server is a game changer
One feature that I have been waiting for years! The new announcement around optimize...
Performance tuning KubeVirt for SQL Server
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
Forums
The AI Bubble and the Weak Foundation Beam
Comments posted to this topic are about the item The AI Bubble and the...
data type gets lost in data flow
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my...
i noticed the sqlhealth extende event is on by default , so can i reduce
hi, i noticed the sqlhealth extended event is on by default , and it...
Question of the Day
The Read Committed Snapshot Isolation behaviour
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers