SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 164 of 365 Next >

As you can imagine, the database engine doesn't just accept data input and store the elements for later retrieval. There is an entire processing engine around accepting, changing and reviewing the data. There are a lot of parameters the engine uses to get at the data. Many of these parameters are set by Microsoft, and are hard-coded into the Query Processor. These parameters often have performance impacts.

But there are also quite a few parameters that you can use to change the behavior of how the processor will deal with the data. You can set many of these options at the server or database level, which means that any query that connects to the server will use these parameters. These "knobs" are available in the management tools for both SQL Server 2000 and 2005 in the "Properties" of each of the objects such as servers, databases and so on.

You can, however, "override" these server-level settings by specifying a SET command in a query. There are quite a few SET commands you can use to affect all kinds of behavior. In this overview I'll cover only a few of those that relate to some specific query behaviors, but there are quite a few that affect other things such as performance and other conditions. Here's a list of the SET options for SQL Server 2000 and 2005. Each has a link to the Books Online entry for that option show you can drill down a little further in each.

SQL Server 2000 SET Options	SQL Server 2005 SET Options
ANSI_DEFAULTS	SET ANSI_DEFAULTS (Transact-SQL)
ANSI_NULL_DFLT_OFF ANSI_NULL_DFLT_ON	SET ANSI_NULL_DFLT_OFF (Transact-SQL) SET ANSI_NULL_DFLT_ON (Transact-SQL)
ANSI_NULLS	SET ANSI_NULLS (Transact-SQL)
ANSI_PADDING	SET ANSI_PADDING (Transact-SQL)
ANSI_WARNINGS	SET ANSI_WARNINGS (Transact-SQL)
ARITHABORT	SET ARITHABORT (Transact-SQL)
ARITHIGNORE	SET ARITHIGNORE (Transact-SQL)
CONCAT_NULL_YIELDS_NULL	SET CONCAT_NULL_YIELDS_NULL (Transact-SQL)
CONTEXT_INFO	SET CONTEXT_INFO (Transact-SQL)
CURSOR_CLOSE_ON_COMMIT	SET CURSOR_CLOSE_ON_COMMIT (Transact-SQL)
DATEFIRST	SET DATEFIRST (Transact-SQL)
DATEFORMAT	SET DATEFORMAT (Transact-SQL)
DEADLOCK_PRIORITY	SET DEADLOCK_PRIORITY (Transact-SQL)
DISABLE_DEF_CNST_CHK	SET FIPS_FLAGGER (Transact-SQL)
FIPS_FLAGGER	SET FMTONLY (Transact-SQL)
FMTONLY	SET FORCEPLAN (Transact-SQL)
SET FORCEPLAN	SET IDENTITY_INSERT (Transact-SQL)
IDENTITY_INSERT	SET IMPLICIT_TRANSACTIONS (Transact-SQL)
IMPLICIT_TRANSACTIONS	SET LANGUAGE (Transact-SQL)
LANGUAGE	SET LOCK_TIMEOUT (Transact-SQL)
LOCK_TIMEOUT	SET NOCOUNT (Transact-SQL)
NOCOUNT	SET NOEXEC (Transact-SQL)
NOEXEC	SET NUMERIC_ROUNDABORT (Transact-SQL)
NUMERIC_ROUNDABORT	SET OFFSETS (Transact-SQL)
OFFSETS	SET PARSEONLY (Transact-SQL)
PARSEONLY	SET QUERY_GOVERNOR_COST_LIMIT (Transact-SQL)
QUERY_GOVERNOR_COST_LIMIT	SET QUOTED_IDENTIFIER (Transact-SQL)
QUOTED_IDENTIFIER	SET REMOTE_PROC_TRANSACTIONS (Transact-SQL)
REMOTE_PROC_TRANSACTIONS	SET ROWCOUNT (Transact-SQL)
ROWCOUNT	SET SHOWPLAN_ALL (Transact-SQL)
SHOWPLAN_ALL	SET SHOWPLAN_TEXT (Transact-SQL)
SHOWPLAN_TEXT	SET SHOWPLAN_XML (Transact-SQL)
STATISTICS IO	SET STATISTICS IO (Transact-SQL)
STATISTICS PROFILE	SET STATISTICS PROFILE (Transact-SQL)
STATISTICS TIME	SET STATISTICS TIME (Transact-SQL)
TEXTSIZE	SET STATISTICS XML (Transact-SQL)
TRANSACTION ISOLATION LEVEL	SET TEXTSIZE (Transact-SQL)
XACT_ABORT	SET TRANSACTION ISOLATION LEVEL (Transact-SQL)
	SET XACT_ABORT (Transact-SQL)

I want to be clear about the behavior of these options. There are always defaults set on the server by Microsoft after a "clean" or new installation. You can change these on the server, and any query that runs without a SET option will run with your server's settings. But if the query block, or transaction, contains one of the SET options, that behavior will override what is on the server. Let's take a quick example.

One of the examples I'll show you in a moment deals with how NULLs are handled. Let's assume that the server setting for these values are set to some option we'll call "A." If a query comes in that has a NULL in it, it will be handled in "A" way. But if the server says "A," and a query has a setting for NULLs we'll call "B," then the NULLs will be handled in "B" way. The very next query that comes in without any SET options gets the "A" setting from the server again.

Let's break down the more common SET options that you'll use in your queries, stored procedures and other code. These are by no means exhaustive, but they are the ones I've seen used in many situations. I'll cover some of the information about the setting, but not all. You should click on the links above

SET NOCOUNT

One of the most common settings you should include in your queries, code and stored procedures is SET NOCOUNT ON. By default, this setting is OFF. What this option does is either show (OFF) or not show (ON) the count of rows returned by the query. While this is useful in the query tools, it's not normally needed by an application. While it might sound trivial to provide this count, it is done by the engine – which means that when thousands of queries are processed, it counts each of the rows returned (even if that's just one row) thousands of times. To make matters worse, this doesn't count as a data element, but is transmitted via a message. That takes time and processing power, and almost every time it's data you don't care about. So you should almost always include this line in the top of your scripts:

SET NOCOUNT ON;
GO

SET ARITHABORT and SET ARITHIGNORE

I'm not going to spend a lot of time on these two options, but I want to mention them because the Books Online entries go into great detail about them, with samples and examples. I mention them here because you may either see them in use or need to use them yourself. They both deal with arithmetic handling, specifically for divide by zero errors.

As you know, if you divide a number by a zero value, you'll cause an error on a computer. Computers will happily try to do the work, but they don't always know how to deal with the results. In code, this is usually easy to catch, but it isn't always easy to find in a database program because you're often just pulling back rows from the database. Those rows may contain values you need, but one or two of them might have a zero you didn't anticipate, and if you don't use these settings appropriately you could end up with an error that is very difficult to find. Once again, look up the Books Online entries to see examples of how to find them.

SET TRANSACTION ISOLATION LEVEL

This option deals with the way the system locks the data as you read or change it. The default locking behavior is normally quite acceptable in SQL Server, but there are times when you want to override it. I've got another tutorial that explains this option that you can read here.

ANSI Settings

The ANSI settings (those with ANSI in the title) are also another set I'll direct you to Books Online for further explanations and examples. These settings deal with how certain data elements and behaviors such as NULL values are handled. Mostly you'll want to read up on these when you 're developing an application against multiple platforms like SQL Server and Oracle, or perhaps when you have data that you want to standardize your code around.

SET DATEFIRST and SET DATEFORMAT

These settings become very important when you are working internationally, or any time you cross date lines where there might be a question on date formats. The DATEFIRST option sets the first day of the week, for any day you wish.

The DATEFORMAT command has more to do with display, and it lets you show the date the way you want per query.

SET CONCAT_NULL_YIELDS_NULL

Although this is a setting that won't be around forever, if you migrate an application from SQL Server 2000 to 2005 you might want to be familiar with it. Let's assume that you have the following values:

FName: 'Buck'
MName: NULL
LName: 'Woody'
If you turn this option ON, then if you concatenate a value like this:
SELECT FName + MName + LName
You'll get this back:
NULL
If you turn it OFF, then you get:
'Buck Woody'

I'll explain more of these options as in other sections of the database guide, but for now read up and play with these settings in your applications so that you're familiar with the ones that you'll encounter quite frequently.

InformIT Articles and Sample Chapters

You can find more information about server, database and session settings in SQL Server in this free chapter from Transact-SQL Desk Reference: For Microsoft SQL Server.

Online Resources

It gets even more complicated. You can also set options in your connection layer. See here for more.

< Back Page 164 of 365 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address