|
|
|||||||||
|
|||||||||
|
|||||||||
| |
||
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Hi,
We are designing a large-scale database application. The current one will receive information from many inputs constantly. We expect it to grow in one year to 60GB (on average of 4-5GB/Mo). The database then (after one year) will have a cleaning procedure that will delete information and the size of the database will not increase in such a way. Here are a few questions: 1. What are the guide lines to design and implement such a database? Where can I find information on the web on such cases? 2. From database creation point of view - should we use a few files that will create the database or should we use only one ? If we use a few files, what happends to clustered indexes? Where can I find more reading material? 3. The database has the management tables of the application and the data tables. On data table will hold most of the information in that database. Do you think I need to divide te table? if so, how do we do it? how do you build efficient queries? How do you manage the data in the separate tables? How do you manage indexes? and again where can I find material on this? TIA!! Noam |
|
#2
|
|||
|
|||
|
If you are referring to a MS SQL Server dbms, try the Books Online that come with the code and are also available online at http://msdn.microsoft.com/library
__________________
====== Doug G ====== I didn't attend the funeral, but I sent a nice letter saying I approved of it. --Mark Twain |
|
#3
|
|||
|
|||
|
Quote:
Thanks Doug G, but the issue is not the books - its the common practices. Thanks for the fast reply. |
![]() |
| Viewing: ASP Free Forums > Database > Microsoft SQL Server > Large Scale Database issues |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|