If you will be at TechEd in Orlando, I will be doing the session: Database Design Patterns on Monday and I was just told that we will repeat it Thursday afternoon as well.
The session is a great sesson. It is listed on the Architecture track. We won't be talking about data modeling but we will be talking about how to design the right database structure for the right situation.
I have 5 demos:
1. A Slowly Changing Dimension
2. Fact Tables
3. Horizontal Partitioning
4. SQL Server 2005 Table and Index Partitioning
5. Vertical Partitioning
Database Design Patterns: Architecting the Right Data Model for the Right Application
Architecting an application starts with the database. Different applications need different data models. Fifth normal form is great for an OLTP database, but reporting databases need more of a flat denormalized structure and different Web sites need several different types of data models: eCommerce sites need different data models than traditional publishing sites. You need to optimize your data model for your application's performance needs. Concurrent users, data load, transactions per minute, report rendering, and query seek time all determine the type of data model you will need. See how different applications and different parts of an application can use different data models and how you can architect your database to fit into your application's needs—not the other way around.
Page rendered at Friday, December 4, 2020 3:32:11 AM (Eastern Standard Time, UTC-05:00)
The opinions expressed herein are my own personal opinions and do not represent
my employer's view in anyway.