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)
30,018 reads
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)
30,018 reads
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,518 reads
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,390 reads
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,999 reads
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,321 reads
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,501 reads
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,476 reads
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,488 reads
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,747 reads
2012-06-13
2,450 reads
By James Serra
(This is the third post in a three-part series on how AI is changing...
Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...
By Steve Jones
Next year the PASS Data Community Summit is in DENVER! and London, but Denver...
Comments posted to this topic are about the item Pay for Performance, which is...
Telp/Wa 628218200233 Jl. Jend. Ahmad Yani No.118, Sidakaya Dua, Sidakaya, Kec. Cilacap Sel., Kabupaten...
Comments posted to this topic are about the item Helping an English Student with...
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, 'true')
GO
See possible answers