Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-08-30 : 06:19:54
|
| Kadar writes "We want to design a SQL2000 database which should handle minimum of 30,00,000 records per year. The database is used to capture the travel data and based on the data the user can search the database of their choice with different search conditions.We are developing the system using Borland Delphi under Windows XP platform.How best can I design the database to optimize usage of resources and better result based on search. Will a partitioned database will help me. How the partion should be done.Help me at the earliest." |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-08-30 : 08:02:27
|
| 30 million records isn't that much if the system is designed correctly.1. Normalization. There's a reason people use this. As systems start to get bigger, the benefits increase exponentially.2. Selected denormalization and rollup processes. This can greatly help your searching depending on how complicated it is.We'll need more information to help you out though. It depends on how big the records are, how complex the database, and how you will be doing your searches, etc.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
|
|
|
How to Design Very voluminous database