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 |
|
mverheye
Starting Member
1 Post |
 Posted - 2008-03-27 : 11:42:59
|
| In a previous application i stored about 100.000 actions ( coming from an external system )in an access database for each day. Therefore i created everyday a new accessdatabase to have enough performance. Each month i copied automatically all databases in a new 'month' map as a backup.The goal of the application is the view all actions of one day of week in one grid. This is a kind of history of the external system.I'm afraid the application will become to slow if i save all actions in one database. ( after 1 month i will have 3.000.000 actions.How this is done in an sql server ? Do i have to use a different kind of method ? |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2008-03-27 : 11:48:21
|
You could have one main table where you store all records.When a new month arrives, aggregate and store data in a history table. This way you only get 28/29/30/31 records per month in history table.3 million records arn't that much for SQL Server. It depends on design of your system.
E 12°55'05.25"N 56°04'39.16" |
 |
|
|
myaries123
Starting Member
2 Posts |
Posted - 2008-03-28 : 01:34:14
|
| I agree with Peso that 3 million of rows in one table are not that much for SQL Server (version 7 and above). With that significant of transactions everyday, I am suggesting to create one transaction database and one OLAP database. OLAP database is used to store the archived data (in aggregate or summarize format) from the transaction database every month. All reporting will be directed to the OLAP database. You may want to do some readings on how to create an effective OLAP database. Hope this information will give you some idea how to deal with that significant amount of data.Aries CKY - MY |
|
|
|
|
|
|
How do i manage 100.000 actions a day ?