DB architecture
From: PeyoQuintero (pedroquintero_at_earthlink.net)
Date: 04/05/04
- Next message: Yuan Shao: "RE: Windows Authtication problem?"
- Previous message: Dan Guzman: "Re: Enterprise Manager Icon"
- Next in thread: Bob Simms: "Re: DB architecture"
- Reply: Bob Simms: "Re: DB architecture"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 05 Apr 2004 02:03:06 GMT
Hi there.
We are building a new mission critical application in our company, using SQL
server 2000 as the RDBMS. The new database is replacing a legacy system that
used to run in two platforms: the day to day operations (OLTP) was
maintained in a small DB2 database running on a OS/2 PC (only 1 week of
data) and the rest was moved periodically to an iseries IBM server (DB2).
all the OLTP was done on the PC, and most of the reporting was done against
the iseries DB2 database.
So far we only have one database to replace the two systems mentioned. We
are planning to either separate the data and have the reporting done in
another SQL server machine (with the same schema,and using log shipping) or
create a set of tables that would pre-process the information and would be
used by the reporting tools. When planning for theses, we created a set of
views tha are being use by our current reports (this layering protects us if
we need to change the underlying schema). The current DB is highly
normalized and I don't think would operate well for OLAP. Is the log
shipping approach recommended? Is there a better alternative? I wouldn'
like to have to maintain two different schemas.
Thank you,
Pedro.
- Next message: Yuan Shao: "RE: Windows Authtication problem?"
- Previous message: Dan Guzman: "Re: Enterprise Manager Icon"
- Next in thread: Bob Simms: "Re: DB architecture"
- Reply: Bob Simms: "Re: DB architecture"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
