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,744 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,459 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,287 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,941 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,232 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,404 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,378 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,376 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,677 reads
Connection Strings 101
This article introduces connection strings and suggests using MDAC to easily write efficient connection strings for those new to SQL Integration.
2010-12-24
5,580 reads
Blogs
T-SQL Tuesday #192: What career risks have you taken?
This T-SQL Tuesday is hosted by the one and only James Serra – literally...
T-SQL Tuesday #196: Taking Risks
By Steve Jones
This month we have a new host, James Serra. I’ve been trying to find...
The First Steps: Understanding the Basics of FinOps
By HeyMo0sh
As a DevOps professional, I’ve seen firsthand how cloud costs can quickly spiral out...
Forums
would it be so terrible to install ssms on a few user desktops?
Hi, ssms is free here. I can think of other reasons to do this...
I'm thinking about submitting some articles
I've written some documentation on using different Markdown types of files on GitHub. It's...
Not Just an Upgrade
Comments posted to this topic are about the item Not Just an Upgrade
Question of the Day
Restoring On Top I
I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?
USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO USE DNRTest GO CREATE TABLE MyTest(myid INT) GO USE master RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACESee possible answers