Skip to main content
  • 220 Accesses

Abstract

This chapter consists of tasks that don’t play a large role in database design, and therefore aren’t normally considered part of the data architect’s remit. However, now that you’ve physically implemented your design, you have some idea of the volume of data the hardware will be required to handle. In considering these requirements, the rest of this chapter is a primer rather than a complete reference for such matters, because you won’t always have the luxury of database administration staff to handle them.

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). Determining Hardware Requirements. In: Pro SQL Server 2000 Database Design: Building Quality OLTP Databases. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-0708-5_14

Download citation

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

  • 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