SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 148 of 365 Next >

The interesting part of writing code using T-SQL is that it isn't really a full programming language; it's a platform programming language. That means that important programming concepts, such as User Interface design and file manipulation aren't part of what T-SQL handles. In that aspect, Transact-SQL isn't a "full" or complete programming language.

On the other hand, T-SQL does have more than the basics of a programming language. As we've seen already, it contains statements and operators, code blocks, scope, error handling and variables. In upcoming tutorials, we'll cover more about the best practices to follow when using Transact-SQL to code.

Right now, it's most helpful to look at the T-SQL constructs that are part of "full" programming and what are not. While the chart below is by no means complete, it does show the major concepts and whether T-SQL implements them:

Concept or Construct:	T-SQL Implementation:
Recursion	Can be implemented in T-SQL code
Arrays	Can be implemented with tables or table variables
Casting	CAST and CONVERT
Statements	Data Manipulation and Data Definition
Code Blocks	Each transaction is a block, plus BEGIN and END statements
Decision Trees	Inherent
Scanning	Inherent
Search	Inherent
Sorting	Inherent
Program Flow	Manual – could be implemented by nested calls
Operators	Mathematical, Equivalency, Boolean, Statistical
Object handling	Minor
OS integration	Minor
Variables	Multiple Types, Local scope only
Device control	N/A
File Manipulation	N/A
Graphics	N/A
Pointers	N/A
Print control	N/A
Queues	N/A
Stacks	N/A
User Interface	N/A
Functions	Not the same as programming functions, more akin to stored procedures
String Manipulation	Single and Multiple Character
Debugging	Yes
Syntax Parsing	Yes
Error Handling	Partial
Lexical Units (literals, comments, delimiters)	Yes
Declarations	Yes
IF-THEN-ELSE	Yes
Iterative Loops	Yes
Collections	N/A

If T-SQL isn't a complete language, shouldn't it be considered part of a pure developer's job to learn the best way to write stored procedures and dynamic SQL? Is there really a need for a "Developer-DBA"? The answer is yes – to both questions.

Some developers never have to bother with much database interaction. Game designers, statistical programs and the like have minimal contact with databases. In those cases, the developer won't have a lot of experience or desire to focus on database constructs.

In other cases, business system developers certainly need to understand how to write code against a database system. Even then, however, there are levels of SQL Server knowledge required that are outside the time and skill constraints of the average developer.

In both of these cases, there is certainly a need for a skilled DBA to know how to program. In addition, while a developer might have a good deal of T-SQL knowledge, writing code that behaves well in a multi-database system is another thing.

In addition, the Developer-DBA is left to hone her T-SQL skills, giving an advantage in knowledge. This allows the "distribution of labor" concept that works on many levels.

So if there is a difference between these two developers, when do we draw the line between things that are written in a specific language (such as C# or Java) and those written in T-SQL? Put another way, where should the processing take place: at the client or middle-tier or at the SQL Server level?

A simple answer might involve merely comparing the feature we need with the ones SQL Server provides (as shown on the earlier chart). You use T-SQL where it has an advantage and the other language where it's better suited to handle the task.

Using this method leaves us with a few gaps, however. For instance, SQL Server is great at sorting (it does that using the ORDER BY statement), not as great with scope on variables. If these two constructs are needed in tandem, it might not even be possible to create the proper statements and handoffs.

The other method of deciding where to place the code is to make a decision at the outset about where the T-SQL will reside. When T-SQL code is written into the programming language on the client or in the middle-tier and then sent to be processed by SQL Server, it's called Dynamic SQL. The alternative is to code the T-SQL into Stored Procedures, and then call those procedures from the client or middle-tier.

The advantage of this approach is encapsulation. In this method, the programming language calls a Stored Procedure, providing inputs and accepting outputs. The T-SQL inside the Stored Procedure can be maintained and optimized separately, leaving the programming language to handle things that T-SQL does not.

Another advantage to this approach is that the Stored Procedures aren't compiled into an executable file, so they can be edited without a recompile. If you upgrade SQL Server to a newer version, the Stored Procedures can be optimized for that platform and dropped into place without changing a single line of programming code on the client or middle-tier.

Finally, this approach allows SQL Server to cache the Stored Procedures, making them faster. What this means is that the query engine can evaluate the T-SQL and develop the most efficient plan to execute the commands. When that procedure is called for again, the plan is already available and acted on even more quickly.

While these advantages are quite compelling, it's a bit too simplistic to set one method into place blindly. There are conditions which call for either approach, or even a mixture of both.

In any case, it's important to figure out from the outset what the goal is. The T-SQL code is only part of any larger design, and it's important to think in terms of an entire system.

Business processes and rules, budget constraints, design goals (and other criteria) will determine, in large part, where to place the T-SQL code.

After we cover the concepts and mechanical parts of T-SQL programming, we'll discuss the process to create an entire system. Stay tuned – we have a few things to learn before we put it all together.

Online Resources

Erland Sommarskog has a really good treatment of Dynamic SQL and Stored Procedures where he covers the concepts I've mentioned here a bit deeper. It's a good resource.

InformIT Tutorials and Sample Chapters

Ready to jump ahead and learn a lot more about software design? Thomas J. Mowbray and Raphael Malveau have a great reference on Safari called "Software Architect Bootcamp, 2nd Edition."

< Back Page 148 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