First step to design Database?

[suklee64]

We currently have corporate level Oracle DB server in corporate headquarter. And corporate level decided us (Business Analysts) to limit our accessing DB, because of the burden of data transaction. Therefore, we decided to make a small MS Access DB into network drive, download monthly some parts of Oracle DB, and all business analysts can share the small sized Access DB.

Now, my concerning is how to design the small DB which all department analyst can share with. Because all analysts from different department usually select different column in different tables from the huge Oracle DB, the success of my Access DB design comes from everybody’s satisfaction.

I wonder if DB specialist in this group can provide me the guide line/ steps/ awareness before design the DB. What is the first step to design DB? Are there any tools to help DB design?

Thanks,

 

[suklee64]

Dear Pat Hartman;

Thank you for the reply. It will really help my current project. However, I need your verification for pre-built report and “Data” database. Is this same meaning of shared database? I just want to understand your suggestion correctly.

Many thanks,

 

[KenHigg]

FYI: This is commonly known as a datawarehouse. A lot of larger companies have their IT dept set these up -

 

[gemma-the-husky]

presumably, your main areas of concern will be to decide

a) what data fields you need in your access database
b) what is the "atromic level of these" - eg do you intend to totalling certain transactions and storing them as weekly/monthly totals, as doing stuff like this will reduce the size of the Access DBs, and increase speed of access, but will also restrict the level to which you can drill into your data