Skip to main content
  • 215 Accesses

Abstract

In this chapter, you start the process of physical implementation by considering questions about how you should architect the solution. In order to illustrate the type of judgments you may have to make, consider the following scenarios and assess what each requires for successful implementation. Consider some of the possibilities discussed earlier in the book, such as an ODS or operational data store (used to separate reasonably current read-only structures for reporting) or simply additional hardware to improve query performance. Each is a realistic example of databases that are quite commonplace today. Let’s assume in each case that the logical design is complete and appropriate in each case.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

eBook
USD 16.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 49.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2004 Louis Davidson

About this chapter

Cite this chapter

Davidson, L. (2004). Planning the Physical Architecture. In: Pro SQL Server 2000 Database Design: Building Quality OLTP Databases. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-0708-5_9

Download citation

  • DOI: https://doi.org/10.1007/978-1-4302-0708-5_9

  • Publisher Name: Apress, Berkeley, CA

  • Print ISBN: 978-1-59059-302-8

  • Online ISBN: 978-1-4302-0708-5

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics