Home > Articles > Data > SQL Server

Creating the SQL Spy Net Application Database

As in most tasks within SQL Server 2000, there are many different ways to achieve the same thing. You can use a nice user interface or you can enter Transact-SQL directly against the database.

Even most of the configuration options for the model database that we just went through can be set using Transact-SQL!

What methods are available to create a database in SQL Server 2000? Listed here are the three basic methods you can use to create a database:

  • Run the Database Creation Wizard, which is contained in Enterprise Manager. This is a simple wizard that allows you to enter the parameters that you require to model your database on. Although using the wizard is an effective and simple way to create an application database, as a DBA you usually will use one of the two following methods because they are a little quicker. For this reason we will not cover the creation of a database through the wizard.

  • Using the UI in Enterprise Manager to create a database. This is done by selecting the New Database option from the pop-up menu when you right-click the database folder within Enterprise Manager. This is the most common way of creating a database in SQL Server 2000, probably because of the friendly user interface you are provided. We will initially create our application database with this method.

  • Enter the CREATE DATABASE Transact-SQL statement directly into Query Analyzer. This is by far the most difficult to remember (I always have trouble remembering the exact syntax), but it gives you the most flexibility and is probably the preferred way for most DBAs. The reason? The knowledge is cross-transferable. Even if you move to another database management system (heaven forbid), you will know the basic structure of the statement.

As you can see, the ability to create a database quickly and easily (by all levels of users) is well catered for in SQL Server 2000.

Using Enterprise Manager to Create Our Application Database

In this section we will develop the database through the user interface in Enterprise Manager. Unfortunately though, I am going to make an assumption about the PC on which you are running SQL Server 2000.

I am assuming that you do not have multiple hard drives. On the PC that I am using I have three separate hard drives, but not everybody will have the same configuration, so we will go with the lowest common denominator. However, if you do have the ability to specify different drives for the data and transaction logs, feel free to do so (this was discussed in the section "Configuring the Model Database to Meet Our SQL Spy Net Application Requirements," earlier in this chapter).

Well, let's get down to business!

If you do not have Enterprise Manager running, start the application now. Drill through the tree-view control and locate the Databases folder. If you right-click the Databases folder you will be presented with a pop-up menu similar to that shown in Figure 3.11. Select the New Database option.

Figure 3.11
The create a new database command in Enterprise Manager.

The next screen collects some basic information in regard to the creation of a database. We are going to call our database SQLSpyNet. This is the name that SQL Server 2000 will use to recognize our application database. You could name your database something else, but throughout the rest of the book I will refer to the SQLSpyNet naming convention, so it will be easier if you use this name. The new screen will look similar to that shown in Figure 3.12.

Figure 3.12
The Create New Database Properties dialog screen.

The General Tab

The General tab is relatively limited in the actions that you can perform. Other than entering the database name the only other action is the collation name. This is used to set the type of locale configuration that the database will have. You only need to alter this if your database will talk to a computer that has a different locale setting than your server (your PC) has.

The locale refers to the way the characters on your computer are displayed and stored. The locale is set for your machine when the operating system is installed. Different countries and languages use different locale settings so that unique characters to their language can be displayed. For example, the U.S. English character set uses the Latin1_General locale.

Because we are developing our application from scratch and currently do not have a requirement to communicate with other databases, we shall leave the database default to the server's settings.

Notice that the screen has two other tabs: the tabs for configuring the data files and the transaction logs. If you have a quick look, you will see they imitate the settings (except the filenames) that we adjusted in the section, "Configuring the Model Database to Meet Our SQL Spy Net Application Requirements."

Click OK now, and SQL Server 2000 will create your first database for you! Simple, isn't it?

Note - If you don't see your new database in the Databases folder, right-click and select Refresh.

The Properties Tab

Now select the SQLSpyNet database, right-click, and choose the Properties option. You will be presented with a screen similar to the one that we saw in Figure 3.9. Click the Options tab and you will see the screen shown in Figure 3.13.

We are going to check that the options that we set in the model database are reflected in our new database. If the settings are correct they should mirror the settings in Figure 3.13. When you are happy with the settings, click OK.

If you explore in the new database (namely the Tables, Views, and Stored Procedures folders), you will see that some database objects have already been created. These are the system objects that SQL Server 2000 uses to keep track of the objects contained in our database. For example, if you open the Tables folder you will see a list of system tables.

Figure 3.13
SQLSpyNet Database Properties screen—Options tab.

Note - If you do not see the system tables, you will need to alter the registration properties of Enterprise Manager. You can do this by selecting the ServerName\InstanceName icon, right-clicking, and then selecting Edit SQL Server Registration Properties; you will see the registration dialog window.

When the dialog window starts, ensure the Show System Databases and System Objects box is selected. Click OK.

For more information, see the section "Configuring SQL Server 2000" in Appendix B or "Setting the sa Password," earlier in this chapter.

These system tables contain information about the schema of the database, for example the names of tables, views, and stored procedures (in the sysobjects table), the names, size, type of columns within tables (the syscolumns table), and the names and access of the users (the sysusers table). This allows SQL Server 2000 to track not only the tables, views, and stored procedures, but also the users and many other objects defined in our database.

Well, that is about all we have to do with our database so far. We can now delete (drop) the database. "What?!?" I hear you cry.

We know how to develop a database through the nice UI that Enterprise Manager provides, so let's learn how to do this through Transact-SQL code.

Note - For the rest of the application development we are going to use a mixture of Transact-SQL code (my preference) and the UI in Enterprise Manager. However, we will not repeat tasks as we have done in this section. Instead, we will implement our changes and move to the next task, or else we will never get our application up and running!

Dropping Spies Like Flies

First, though, we need to drop the SQLSpyNet database that we just created.

Start Query Analyzer through the start menu group or by selecting Tools from the menu bar in Enterprise Manager and selecting the SQL Server Query Analyzer option. Then enter the code in Listing 3.1 into the Transact-SQL window, as shown in Figure 3.14.

Figure 3.14
Removing our database by using code in the Query Analyzer window.

Listing 3.1—Deleting Our SQLSpyNet Database Using Transact-SQL Code

1: USE master
2: GO
3: IF EXISTS (SELECT name FROM master.dbo.sysdatabases
3a:WHERE name = 'SQLSpyNet')
5: GO

After you have entered the code in the window, click the Green Triangle in the toolbar, or use the hotkeys Alt+X to run the code.

After the code has finished running you will see two statements of confirmation that the task has completed. They will be similar to these:

1: Deleting database file 
2: Deleting database file

Tip - Save these file paths because you will need them later when we re-create the database.

This confirms that the data file and the transaction log have been deleted.

Note - If you did not name your database SQLSpyNet, enter the name you chose in place of SQLSpyNet.

The meaning of the code is relatively simple. The first two lines of code (1 and 2) ensure that this statement is being fired from the master database. All database manipulation such as DROP and CREATE should be fired from the master database.

The third two lines (3 and 3a) check the existence of your database within our instance of SQL Server 2000; this is called a control-of-flow statement, and there will be more on this in Chapter 4.

The fourth line of code actually performs the database drop, and the fifth line executes the two former statements consecutively.

Do not worry about the SELECT statement or the WHERE criteria; I explain this in more detail in Chapter 4.

If you now refresh your Databases folder in either Enterprise Manger or Query Analyzer (through the Object Browser; refer to Chapter 2), you will see that the SQLSpyNet database has gone!

There we go; so far we have created and deleted a database by using two of the tools available in SQL Server 2000. We will now re-create the SQLSpyNet database through Transact-SQL code; so don't close down Query Analyzer yet!

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.


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.


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.


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.


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


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


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.


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.


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