Ships from: Rockford, IL
Usually ships in 1-2 business days
Ships from: Nashua, NH
Usually ships in 1-2 business days
Ships from: san francisco, CA
Usually ships in 1-2 business days
Ships from: Murphy, TX
Usually ships in 1-2 business days
Ships from: fallbrook, CA
Usually ships in 1-2 business days
Ships from: acton, MA
Usually ships in 1-2 business days
MICROSOFT® SQL SERVER™ 2000 ADMINISTRATOR’S POCKET CONSULTANT is the ideal concise, immediate reference you’ll want with you at all times as you deal with the details of Microsoft SQL Server 2000 database administration. Whether you handle administration for 50 users or 5000, this hands-on, fast-answers guide focuses on what you need to do to get the job done quickly.
With extensive easy-to-read tables, lists, and step-by-step instructions, it’s the portable, readable guide that will consistently save you time and minimize system downtime by giving you the right information right now.
This hands-on guide gives you the fast answers you need to:
A single database server instance can have up to 32,767 databases, and each database can have over 2 billion objects. These are theoretical limits, of course, but they demonstrate that SQL Server can handle just about any chore. To perform most administration tasks, you'll need to log in to the database using an account that has the Sysadmin role, such as the local sysadmin account (sa). Detailed information on roles and SQL Server security is found in Chapter 5.
SQL Server databases and transaction logs are contained inseparate database files. This means that each database always has at least two files associated with it— a data file and a log file. Databases also can have secondary data files. SQL Server uses three types of database files:
NOTE:
SQL Server also uses backup devices. Backup devices can be physical devices, such as tape drives, or files that are stored on a local drive or a network share. SQL Server data and log files can be stored on either FAT or NTFS partitions but can't be stored on any compressed file system.
Database files are set when you create or modify the database. By allowing for multiple database files, SQL Server can create databases that span multiple disk drives and that can grow in size as needed. Although the size of a SQL Server database is often measured in GBs, with all editions of SQL Server except the Personal Edition, databases can range in size from 1 MB to a theoretical limit of 1,048,516 TBs. With the Personal Edition, databases have a maximum size limit of 2 GB.
As you set out to work with databases, keep in mind that SQL Server is designed to expand databases automatically as necessary. This means that master, tempdb, msdb, and other critical databases won't run out of space under normal conditions—provided, of course, that there's file space on the configured drives and that you don't set a maximum database size manually. System databases are the most important ones on the server. You should never directly update tables in system databases. Instead, you should use the appropriate management tools or stored procedures to modify the databases if you need to. The only exception is the model database, which you can update with settings for new databases.
The sections that follow examine each of these tasks.
NOTE:
If you haven't authenticated the server connection, you may need to provide a SQL logon account and password. You may also need to reestablish a connection with the server. In either case, enter any necessary information and then click OK/Yes to continue.
...Figure 4-1. The General view provides a summary of the selected database and also gives quick access to start key administration tasks. Move the mouse pointer over a category button to display a shortcut menu.
sp_helpdb <dbname>where dbname is the name of the database you want to examine.
When you view database information in this way, you get an overview of the database as well as a listing of current data and log files. Table 4-1 gives a summary of this information.
Table 4-1. Database Properties Viewable Using T-SQL
| Column Name | Description |
| compatibility_level | The current compatibility level of the database. 80 indicates SQL Server 2000 compatibility. |
| created | The date the database was created. |
| db_size | The total size of the database including all data and log files. |
| dbid | The unique identifier for the database on thecurrent server. |
| filegroup | The filegroup associated with the database file. Filegroups allow you to group sets of database files together. |
| fileid | The unique identifier for the file in the current database. |
| filename | The full filename and path. |
| growth | The number of megabytes or percent the file grows by. |
| maxsize | The maximum file size. Unlimited means there is no limit. |
| name | The name of the database or file (without a file extension). |
| owner | The database owner. |
| size | The current size of a file. |
| status | The database status. |
| usage | The way the file is used, such as data only or log only. |
Table 4-2. Summary of System and Sample Databases
| Database Name | Database Type | Description |
| Master | System | Maintains information on all databases installed on the server. This database is modified anytime you create databases, manage accounts, or change configuration settings. Back up the master regularly. |
| model | System | Provides a template for all new databases. If you want new databases to have certain properties or permissions, put these changes in the model database and then all new databases will inherit the changes. |
| tempdb | System | Provides a temporary workspace for processing queries and handling other tasks. This database is recreated each time SQL Server is started and is based on the model database. |
| pubs | Sample | Provides a sample database and is often used to demonstrate SQL/Transact-SQL commands. |
| Northwind | Sample | Provides a sample database with application programming interface (API) examples. |
| msdb | System | Used by the SQL Server Agent service when performing handling alerts, notifications, and scheduled tasks. You can access all the information in this database using Enterprise Manager options. |
You can also associate users, roles, rules, and full-text catalogs with databases.
To examine objects within a database, complete the following steps:
| Acknowledgments | ||
| Introduction | ||
| Pt. I | Microsoft SQL Server 2000 Administration Fundamentals | |
| 1 | Microsoft SQL Server 2000 Administration Overview | 3 |
| 2 | Configuring and Tuning Microsoft SQL Server | 19 |
| Pt. II | Microsoft SQL Server 2000 Administration | |
| 3 | Managing the Enterprise | 65 |
| 4 | Core Database Administration | 95 |
| 5 | Microsoft SQL Server 2000 Security | 129 |
| Pt. III | Microsoft SQL Server 2000 Data Administration | |
| 6 | Manipulating Tables, Indexes, and Views | 161 |
| 7 | Importing and Exporting Data with DTS and BCP | 205 |
| 8 | Linked Servers and Distributed Transactions | 243 |
| 9 | Configuring Snapshot, Merge, and Transactional Replication | 261 |
| Pt. IV | Performance, Optimization, and Maintenance | |
| 10 | Profiling and Monitoring Microsoft SQL Server 2000 | 307 |
| 11 | Database Backup and Recovery | 337 |
| 12 | Database Automation and Maintenance | 379 |
| Index | 433 |
Anonymous
Posted Tue Jul 10 00:00:00 EDT 2001
This book is great as a reference book. It's not filled with all the clutter that you might find in other SQL books. If you need detailed information then this book might not be for you, but if you need something that you can use as a daily reference book then this is it.
Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.Anonymous
Posted Sun Nov 19 00:00:00 EST 2000
Hats off to author William Stanek for another fine Pocket Consultant. I have 5 of these books in my library now (Windows NT 4, Windows 2000, Exchange 2000, SQL Server 7 and SQL Server 2000.) Since I picked up the first Pockete Consultant a yaer ago I haven't found a daily administration question that wasn't answered. You'll find that SQL Server 2000 Pocket Consultant is more of the same. The attention to detail and the focus on day to day administration tasks is fantastic! <P>Mr. Stanek always starts with an overview of the subject of discussion and then digs right in. I've found that this book (and the rest in the series) answer 100% of my questions quickly and meanwhile the 1,000 page luggables used by my colleagues just get them frustrasted. I've made quite a few converts in the office. <P>The nice thing about these books is the day to day focus. You get what you need to accomplish your task spelled out clearly and concisely in a style that I've found that only Mr. Stanek can deliver. It is refreshing. Now I'm not saying the books are pefrect. If you need to learn from scratch this isn't the answer. Look elsewhere. If you need to brush up and extend your skills to new stuff (like going from SQL 6.5 or SQL 7 to SQL 2000), is a good choice. If you need a book to help with day to day, is a good choice. If you need a book to put in your backpack and carry with you, is a good choice. <P>Last I want to say thank you to Mr. Stanek. Thank you, I'm looking forward to more. --JW
Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Overview
MICROSOFT® SQL SERVER™ 2000 ADMINISTRATOR’S POCKET CONSULTANT is the ideal concise, immediate reference you’ll want with you at all times as you deal with the details of Microsoft SQL Server 2000 database administration. Whether you handle administration for 50 users or 5000, this hands-on, fast-answers guide focuses on what you need to do to get the job done quickly.
With extensive easy-to-read tables, lists, and step-by-step instructions, it’s the portable, readable guide that...