Module 9: Data Storage Considerations

Module 9: Data Storage Considerations THIS PAGE LEFT INTENTIONALLY BLANK Module 9: Data Storage Considerations Module 8: Designing Data Services Module 1: Course Overview Module 2: Solution Design Processes Module 7: Implementing Data Integrity Module 6: Deriving a Physical Data Design Designing Data Services and Data Models Module 3: Using a Conceptual Design for Data Requirements Module 4: Deriving a Logical Data Design Module 5: Normalizing the Logical Data Design Choosing a Database Product Module 9: Data Storage Considerations Activity 9.1: Data Quiz Data Storage Considerations Data Storage Technologies Module 9: Data Storage Considerations 195 ! Overview Slide Objective To provide an overview of this module’s topics and objectives. Lead-in In this module, you will look at data storage considerations and data storage technologies. ✂Choosing a Database Product ✂Data Storage Technologies ✂Data Storage Considerations ✂Activity 9.1: Data Quiz ✂Review In thismodule... At the end of this module, you will be able to: ✂✁Identify different types of hardware and software for implementing a data store. ✂✁Choose the appropriate hardware or software for implementing a data store. 196 Module 9: Data Storage Considerations ! Choosing a Database Product Slide Objective To provide an overview of this section. Lead-in This section discusses some of the factors to consider when choosing a database product. ✂User Community ✂System Performance ✂System Maintenance In thissection... In this section, you will learn about several factors that you should consider when selecting a database product. Module 9: Data Storage Considerations 197 User Community Slide Objective To explain how the number of users affects a database decision. Lead-in When selecting a database technology, you should consider how many users the system will have to support. ✂Total number of users ✂Total number of concurrent users ✂Scalability for current and future requirements ✂Security One important consideration when examining database technologies is the user community—the number of users who need to be able to use the database. Users are not only the people, but also the other applications that can interactively access the database. If a different application or system needs to access a database, its impact on the database must be taken into account. The total pool of potential users directly impacts a data store’s ability to support an application. The number of actual users concurrently accessing the system at any time is also extremely important. Generally, most database systems provide concurrent, multiuser capabilities, and most multiuser data stores are tuned to support a specific range of concurrent users. How many concurrent users a system can support, as well as how performance might degrade as the number of concurrent users increases, is typically referred to as a database system’s scalability. When identifying concurrent usage patterns, you should identify the average and peak numbers of concurrent users for the application. These numbers will also translate into the number of concurrent users for the data store itself. They can be one-to-one ratios, as with most client/server applications. However, distributed application designs typically decrease the number of concurrent data users per concurrent application user because not all users access the data server every time they use the application. It is also important to expect and plan for the total number of users to grow over time. The application design and the choice of data stores should reflect the expected growth in application use. Finally, most systems provide some level of user security. Security can be categorized as authentication, access, encryption, or auditing, depending on whether data stores provide services to identified users, allow access to particular data elements, encrypt critical information, or keep a record of transactions. ... - tailieumienphi.vn