Execute Dynamic SQL commands in SQL Server

-
In some applications having hard-coded SQL statements is not appealing, because of the dynamic nature of the queries being issued against the database server. Because of this sometimes there is a need to dynamically create a SQL statement on the fly and then run that command. This can be done quite simply from the application perspective where the statement is built on the fly whether you are using ASP.NET , ColdFusion or any other programming language. But how do you do this from within a SQL Server stored procedure? SQL Server offers a few ways of running a dynamically built SQL statement. These ways are: Writing a query with parameters Using EXEC Using sp_executesql Writing a query with parameters This first approach is pretty straightforward if you only need to pass parameters into the WHERE clause of your SQL statement. Let’s say we need to find all records from the Customers table where City = ‘London’. This can be done easily as the following example shows. ...
Post a Comment

Functional difference between “NOT IN” vs “NOT EXISTS” clauses

-

“NOT IN” and “NOT EXISTS” clauses are not the same functionally or performance wise and, therefore, should be used appropriately. This blog post outlines how these commands are executed and discusses when it is appropriate to use them.

Sample data:
/*******************************************************************************************
Create a dummy EMP_MASTER table populate it with some records for illustration. This is Oracle Syntax. There are ten employees that have been created and 9 out of those 10 report to their manager: Dennis who is at the head of the chain and does not have a manager to report to.
********************************************************************************************/
CREATE TABLE EMP_MASTER
(
EMP_NBR NUMBER(10) NOT NULL PRIMARY KEY,
EMP_NAME VARCHAR2(20 CHAR),
MGR_NBR NUMBER(10) NULL
)
/

INSERT INTO EMP_MASTER VALUES (1, ‘DON’, 5);
INSERT INTO EMP_MASTER VALUES (2, ‘HARI’, 5);
INSERT INTO EMP_MASTER VALUES (3, ‘RAMESH’, 5);
INSERT INTO EMP_MASTER VALUES (4, ‘JOE’, 5);
INSERT INTO EMP_MASTER VALUES (5, ‘DENNIS’, NULL);
INSERT INTO EMP_MASTER VALUES (6, ‘NIMISH’, 5);
INSERT INTO EMP_MASTER VALUES (7, ‘JESSIE’, 5);
INSERT INTO EMP_MASTER VALUES (8, ‘KEN’, 5);
INSERT INTO EMP_MASTER VALUES (9, ‘AMBER’, 5);
INSERT INTO EMP_MASTER VALUES (10, ‘JIM’, 5);
COMMIT
/

Resulting in:

EMP_NBR

 EMP_NAME MGR_NBR
1 DON 5
2 HARI 5
3 RAMESH 5
4 JOE 5
5 DENNIS NULL
6 NIMISH 5
7 JESSIE 5
8 KEN 5
9 AMBER 5
10 JIM 5

Now, the aim is to find all those employees who are not managers. Let’s see how we can achieve that by using the “NOT IN” vs the “NOT EXISTS” clause.

NOT IN

SQL> select count(*) from emp_master where emp_nbr not in ( select mgr_nbr from emp_master );
COUNT(*)
———-
0

This means that everyone is a manager…hmmm, I wonder whether anything ever gets done in that case :-)

NOT EXISTS

SQL> select count(*) from emp_master T1 where not exists ( select 1 from emp_master T2 where t2.mgr_nbr = t1.emp_nbr );

COUNT(*)
———-
9

Now there are 9 people who are not managers. So, you can clearly see the difference that NULL values make and since NULL != NULL in SQL, the NOT IN clause does not return any records back. (in MS SQL Server, depending upon the ANSI NULLS setting, the behavior can be altered but this post only talks about the behavior that is same in Oracle, DB2 LUW and MS SQL Server).

Performance implications:

When using “NOT IN”, the query performs nested full table scans, whereas for “NOT EXISTS”, query can use an index within the sub-query.

Another Optional Method

Another way of doing this is to use an outer join and check for NULL values in the other table:

SELECT COUNT(*)
FROM EMP_MASTER T1
LEFT OUTER JOIN EMP_MASTER T2
ON T1.EMP_NBR = T2.MGR_NBR
WHERE T2.MGR_NBR IS NULL
/

Of course, there should be other selection criteria as well (possibly a range search criteria, an equality SARG (searchable argument) criteria etc.) to help improve the selectivity besides just the NOT EXISTS clause.

Comments

Post a Comment

Popular posts from this blog

Check If Temporary Table Exists

-
When working with temporary tables in SQL Server, the common conundrum is often determining whether a temp table exists before performing operations on it. In this blog post, we’ll delve into the nuances of checking the existence of temp tables and explore the potential pitfalls and solutions. The Basics: Local Temp Tables To check if a local temp table exists, one commonly used approach is: IF OBJECT_ID ( 'tempdb..#temp' ) IS NOT NULL BEGIN PRINT '#temp exists!' END ELSE BEGIN PRINT '#temp does not exist!' END This method utilizes the OBJECT_ID function to verify the existence of the temp table in the tempdb database. The Undocumented Second Parameter An alternative way involves an undocumented optional second parameter: IF OBJECT_ID ( 'tempdb..#temp' , 'u' ) IS NOT NULL BEGIN PRINT '#temp exists!' END ELSE BEGIN PRINT '#temp does not exist!' END However, it’s important to no...
Read more

Multiple NULL values in a Unique index in SQL

-
this project needed to support having multiple NULL values in the column and still have a UNIQUE constraint . That is allowed by Oracle but not in SQL Server and DB2 LUW. There is a way to make this work in SQL Server and DB2 LUW also but that requires a work -around. Consider this table : CREATE TABLE TEST_UQ (COL1 INT IDENTITY (1,1) PRIMARY KEY , COL2 NVARCHAR(10) NULL ) GO In this table , COL1 has been declared as the primary key but we want a UNIQUE constraint to be put on COL2 as well. Please note that COL2 is a nullable column and that SQL Server does not allow multiple NULL values in a UNIQUE index and treats them the same way. We can test it out prior to proceeding with the work -around: Let tus create a unique index first : CREATE UNIQUE INDEX TEST_UQ_IND_1 ON TEST_UQ (COL2) GO Now, let us try to insert these values : insert into test_uq (col2) values (’abc’); insert into test_uq (col2) values (’xyz’); insert into ...
Read more

How To search entire database?

-
While browsing the SQL Server newsgroups, there are occasional requests for a script capable of searching all the columns of all the tables in a given database for a specific keyword. Although it might seem trivial, the need for such a script became apparent in a real-world scenario. In troubleshooting a problem with Microsoft Operations Manager (MOM), which utilizes SQL Server for storing computer, alert, and performance-related information, a network administrator needed to search all the MOM tables for a specific string. Lacking a readily available script, manual searching ensued. This experience prompted the creation of a stored procedure called “SearchAllTables.” SearchAllTables Stored Procedure The SearchAllTables stored procedure takes a search string as an input parameter and systematically searches all char , varchar , nchar , and nvarchar columns of all tables (excluding system tables) owned by all users in the current database. Feel free to extend this procedure to sea...
Read more