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 |
|
groggy_froggy
Starting Member
1 Post |
 Posted - 2004-12-17 : 01:44:02
|
| I need to design a database for an application that will be using this database mainly for generating reports of various kinds. Naturally, there will be data input and editing requirements, but it is not a transactional type of database. Given that the main aim is report generation, are there specific design principles I should be aware of for this type of database? Or is there essentially not much difference in designing a transactional type of database compared to a reporting type? I'd bee keen to hear more experienced developers' ideas on this. |
|
|
|
|
|
Database Design: mainly for reporting