Home > Store

Microsoft SQL Server 2000 Database Development From Scratch

Register your product to gain access to bonus material or receive a coupon.

Microsoft SQL Server 2000 Database Development From Scratch

Book

  • Sorry, this book is no longer in print.
Not for Sale

Description

  • Copyright 2001
  • Edition: 1st
  • Book
  • ISBN-10: 0-7897-2447-2
  • ISBN-13: 978-0-7897-2447-2

Microsoft SQL Server Database Development from Scratch is a road map to database management, implementation, and administration. Author Rob Hawthorne teaches readers how to create, maintain, and increase performance within the application. Concepts and techniques are reinforced as readers create a spy tracker database.

Downloads

Source Code


Zip file containing code - 86KB -- ch12_SpyNetWebSite.zip
Zip file containing code - 9KB -- ch13_SQLSpyNetExcelSheets.zip
Zip file containing code - 143KB -- SQLSpyNetDatabase.zip
Zip file containing code - 16KB -- final_listings_by_ch.zip

To restore the SQLSpyNet database you will need to use the above code within Query Analyzer of course!

1: RESTORE DATABASE SQLSpyNet

2: FROM DISK = 'Download Location of SQLSpyNet.bak'

3: WITH REPLACE,

4: MOVE 'SQLSpyNet_Data' TO 'Location of Data files with the name

SQLSpyNet_Data.mdf',

5: MOVE 'SQLSpyNet_Log' TO 'Location of Log files with the name

SQLSpyNet_Log.mdf',

6: STATS = 10

Just remeber though on Line 2 you will need to replace "Download Location of SQLSpyNet.bak" with the path that you downloaded the SQLSpyNet.bak file to For example'C:\Temp\SQLSpyNet.bak'. The same for lines 4 & 5. Replace the text I have there with the paths that you wish to save the .mdf and .ldf files to. The following code snippet gives you an example of what your code may look like after changing the text as I have specified.

RESTORE DATABASE SQLSpyNet

FROM DISK = 'C:\Program Files\Microsoft SQL

Server\MSSQL$MYSQLSERVER\BACKUP\SQLSpyNet.bak'

WITH REPLACE,

MOVE 'SQLSpyNet_Data' TO 'C:\Program Files\Microsoft SQL

Server\MSSQL$MYSQLSERVER\DATA\SQLSpyNet_Data.mdf',

MOVE 'SQLSpyNet_Log' TO 'C:\Program Files\Microsoft SQL

Server\MSSQL$MYSQLSERVER\DATA\SQLSpyNet_Log.mdf',

STATS = 10

For more information on restoring databases refer to Chapter 10 in the book. The process is described in a little more detail there. The code listings on the site have been made available to make life a little easier for you. However you should note that in some instances you cannot run the whole code file for whole a chapter in one go. Instead the recommended approach is to run each code listing seperately. The reason for this is the code appears as it does in the book. However SQL Server requires that CREATE statements i.e. CREATE PROCEDURE are the first lines of code in batch.

Also you need to be aware of the placeholders in the listings. You may find in the code listings that I have a direct reference to the physical location of a file on disk. You NEED to change this before the code will run. For example if I have BACKUP DATABASE SQLSPyNet TO DISK = 'x:\SQLSpyNet.bak' you would need to change the "x:\" to the actual path where you would like the backup to be saved to.

Anyway enjoy the book, and most of all have fun!

Sample Content

Online Sample Chapters

Assigning Roles for Our Users in SQL Server 2000

Creating an Index on Our Person Table to Increase Query Performance

Performing General Administration Tasks in SQL Server 2000

Using Online Resources to Explore SQL Server 2000

Using SQL Profiler to Find Errors

Table of Contents



Introduction.


1. Taking Spy Net from Idea to SQL Server Database.

A Case Study for Spy Net Limited.

An Overview of the SQL Spy Net Application. Determining What the Application Should. What Are We Going to Achieve?

Modeling the SQL Spy Net Application.

Designing the Spy Net Tables. Using Relational Theory to Model Spy Net's Application. Building Relationships Between Enemies.

Taking a Broad Overview of Spy Net. Summary. Next Steps.



2. The Tools of SQL Server 2000 for Managing an Instance.

Exploring Database Objects with Enterprise Manager.

Why You're Sure to Love Enterprise Manager. How This Tool Fits into Our SQL Spy Net Application.

Getting the Answers with Query Analyzer.

What You Can Do with Query Analyzer. Using This Tool for the SQL Spy Net Application.

Tracking Code Crimes with Profiler.

When You'll Use Profiler. Profiling and the SQL Spy Net Application.

Importing and Exporting Data the Easy Way.

Why You Should Use DTS. Generating SQL Spy Net Data with DTS.

Checking Out SQL Server 2000's Other Tools. Summary. Next Steps.



3. Making Virtual Spies-Creating Spy Net in SQL Server 2000.

Playing Program Director (Sys Admin) for SpyNet.

Setting the sa Password. Configuring the Model Database to Meet Our SQL Spy Net Application. Requirements.

Creating the SQL Spy Net Application Database.

Using Enterprise Manager to Create Our Application Database.

Using the Data Definition Language (DDL) to Create Databases and Objects.

Building Tables for Our Spies. Revisiting the Analysis of the SQL Spy Net Application.

Bringing Our Data Model and Database Together.

Developing the First Database Table for the SQL Spy Net Application. Creating Tables the Fun Way-With Code. Filling in the Blanks.

Summary. Next Steps.



4. Manipulating Data with Transact-SQL.

What Is This SELECT Statement Then?

The First Building Block for SELECT. Where Does the Data Come FROM? Limiting Data with WHERE. Put Those Spies in Order!

Let's Get Some Data in with the INSERT Statement.

Defining the Table and Columns We Want to Insert Into. Let's Put In Some New Data!

Keeping Everything Up-to-Date.

Which Table, Please? Correcting Data to Fix Data Problems. WHERE to Put the New Value.

When a Good Spy Dies...DELETE 'em. What Else Can We Do with Transact-SQL Besides DMLs and DDLs?

Declaring Variables. Assigning Values to Our Variables with the SET Statement. The IF Test--Is What We Have in Our Variable What We Expect? Using WHILE Loops.

Summary. Next Steps.



5. Pushing the Boundaries of Our DDL Knowledge to View and Update Data.

Adding Information About Our Spies. Finding a Good View.

Getting Your First Look at a View. Looking at JOINs. Comparing Views to Tables. Restrictions on Views.

Streamlining Updates with Stored Procedures.

Creating the Stored Procedure Code. Checking the Table for Places to Fill. Letting the Stored Procedure Do the Work. Creating the Stored Procedure to Insert into Both the Person and BadGuy Tables. Checking For and Filling In NULLs. Guidelines for Using Stored Procedures.

Pulling Triggers to Catch Events.

Creating a Trigger to Catch Double Spies. Testing the Trigger. Setting a Trigger on the Spy Table.

Dropping Objects All Over the Place. Going Round and Round Using Cursors. Summary. Next Steps.



6. Getting Clearer Results with Functions.

Understanding the Role of Functions. Using Built-In Functions.

Using CONVERT to “Make Money”. COUNT-ing Spies. Using the SUM Function to Tally Paychecks. Putting STUFF into Strings.

Creating Your Own Functions to Manipulate Data.

Tweaking Dates from Around the Globe. Executing a User-Defined Function.

Building Your Function Library.

Scalar Functions. Aggregate and Rowset Functions.

Summary. Next Steps.



7. Securing Data Entry with Custom Rules and Defaults.

Introduction. Ruling Your Data World.

Checking for Underaged Spies. Binding and Testing the Rule.

Setting Default Values.

Filling in the Missing Data for Our Users. Testing the Default.

Adding Custom Data Types to Keep Data Uniform.

Validating Phone Numbers. Using the Data Type.

Summary. Next Steps.



8. Ensuring Data Consistency with Transactions, Locks, and Error Trapping.

Keeping Data Consistent with Transaction Wrappers.

Making Transactions Pass the ACID Test. Choosing a Transaction Type. Creating a Transaction for Spy Net. Getting the Most from Your Transactions.

Maintaining Data Integrity with Locks.

How SQL Server 2000 Automates Locking. Developing a Locking Strategy. Locking Considerations.

Handling Errors So Our Application Doesn't Break.

What Is an Error Composed of in SQL Server 2000? Catching an Error. Making Errors Work for You. Changing Our Stored Procedure to Implement Error Trapping.

Summary. Next Steps.



9. Implementing Security in Spy Net.

Sharing Spy Net with Other Users.

Creating Logins to Spy Net. Logging In as SQLSpyNetUser to Test Permissions.

Assigning Roles for Our Users.

Assigning Roles to the SQL Server Instance. Creating a Role Model. Exercising Our Rights.

Auditing: Yes, Big Brother Really Is Watching!

Basic Auditing in SQL Server 2000. Looking at C2 Auditing.

Considerations for Developing a Security Strategy. Summary. Next Steps.



10. Ensuring Data Availability.

Creating a Database Backup Strategy.

How to Prevent Losing Everything. Using Transaction Logs in Backup and Recovery. Choosing the Appropriate Recovery Model. Finding the (Right) Time. Where Do I Back Up To? What Do I Back Up? Backing Up Spy Net Using Enterprise Manager. Backing Up Spy Net Using Transact-SQL in Query Analyzer.

Restoring Spy Net.

How to Get It All Back. Applying Transaction Logs. Restoring Spy Net Using Enterprise Manager. Restoring Spy Net Using Transact-SQL in Query Analyzer.

Finalizing Your Plan.

Keep Track of Copies. Mark the Transaction Log. Create a Warm Server. Create a Checklist of Resources and Practices. Make and Follow Your Recovery Steps.

Summary. Next Steps.



11. Administering Spy Net.

Configuring SQL Server 2000. Performing General Administration Tasks.

Scheduling Jobs. Calling on SQL Server Operators. Using Alerts. What Do SQL Server Logs Do?

Running Consistency Checks. Generating a Maintenance Plan for Database Consistency and Availability.

Using the Maintenance Plan Wizard to Create Our Maintenance Plan.

Identifying Indexes.

How Indexes Work. When to Use an Index. Creating an Index on Our Person Table to Increase Query Performance. Maintaining Our Indexes to Keep Our Application Performing. Efficiently.

Performance Monitoring.

Monitoring Current Activity.

Summary. Next Steps.



12. Designing a Front End to Support Our SQLSpyNet Database.

Understanding Basic Client/Server Architecture to Implement for Our. SpyNet Application.

What Is a Fat Client? Why Use a Thin Client? Which Configuration Is Best?

Choosing a Front-End Development Environment for Our Application.

Microsoft Visual Basic (VB). Microsoft Access. Microsoft Active Server Pages (ASP).

Establishing a Connection to Our SQLSpyNet Database.

Using the Tried and True Method of ODBC (MSDASQL). Using the New-Fangled OLE DB Provider for SQL Server (SQLOLEDB).

Building the SpyNet User Interface.

Determining the SpyNet Web Pages. Setting Up Your Machine to Run the SpyNet Application. Setting Up Our Web Site to Run Under PWS. Creating a New User to Establish a Connection. Creating Our First Page, the Global.asa. Creating the Default.htm Page. Building the Include Pages. Validating the User's Login. Greeting Users with the Welcome.asp Page. Creating the Search.asp Page to Retrieve Data from SpyNet.

Watching Speed and Consistency. Surfing the SpyNet Site. Summary. Next Steps.



13. Putting All the Pieces Together.

Putting New Data into SQLSpyNet with the DTS Wizard. Backing Up the Database Before the Transfer. Creating a Stored Procedure to Clean Out the Data.

Using Enterprise Manager to Create a Stored Procedure. Denying Access to the Power of Deletion. Running the Stored Procedure.

Using the DTS Wizard to Reload Our SQLSpyNet Database with Data. Checking the Results of the Import. Where Does Our Application Go Now? Summary. Next Steps.



14. Troubleshooting and Debugging in SQL Server 2000.

Using SQL Profiler to Find Errors.

Creating the Trace. Spying on Users.

Using the Client Network Utility to Resolve Connection Problems. Debugging Stored Procedures. What? No More Room?

How Memory Affects Database Transactions. Shrinking Your Data Files to Reduce the Database. Altering the Size of the Transaction Log Files. Truncating the Transaction Log. Keeping the Faith with Fail-Over Clustering

Summary. Next Steps.



15. Exploring SQL Server 2000 on Your Own.

Using Online Resources to Explore SQL Server 2000.

Search and Retrieval Tips for Books Online. Finding Help on the Web.

Seeing Double (or Triple, or...).

Running Multiple Instances on One Machine. Using Multiple Collation. Keeping Multiple Database Applications in Sync with Replication.

Leveraging Enhancements to Improve Development.

Using Cascading Declarative Referential Integrity (Cascading DRI). Mimicking Built-In Functions with User-Defined Functions. Coding with Three New Data Types. Getting More from Query Analyzer. Scripting Database Objects. Using AFTER and INSTEAD OF Triggers. Looking at Distributed Views. Creating Enhanced Indexes. Leveraging XML Support.

Using the New Wizards in SQL Server 2000.

Tuning Indexes. Copying Databases.

Improving Security.

Understanding Kerberos and Security Delegation. Using Password Security on Database Backups. Using C2 Auditing.

Summary.



Appendix A. Setting Up Your PC as a Web Server.


Appendix B. Installing and Configuring SQL Server 2000.

Selecting the Type of Installation. Installing the Application Following the Step-By-Step Wizard. What Happens If I Select the Custom Install Option? Checking the Installation's Success. Configuring SQL Server 2000.

Connecting to SQL Server 2000 for the First Time. Using a Wizard to Connect to SQL Server 2000. How Does It All Work?



Appendix C. Where to Go from Here.

Microsoft Certification.

How to Become a Microsoft-Certified Professional (MCP). How to Become a Microsoft-Certified Solution Developer (MCSD). How to Become a Microsoft-Certified Systems Engineer (MCSE). How to Become a Microsoft-Certified Database Administrator (MCDBA). How to Plan for Microsoft Certification.

Study Guides. Job Opportunities A Thank You to You, the Reader.



Index.

Updates

Submit Errata

More Information

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.

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