Re: Reasons for not considering Logical Standby Databases for Reporting purposes
- From: "Dennis Williams" <oracledba.williams@xxxxxxxxx>
- To: cjpengel.dbalert@xxxxxxxxx
- Date: Fri, 3 Nov 2006 20:55:22 -0600
I can think of another reason. Changing user requirements. The way you have
described it, your reporting database will lag production by a day. Suppose
you invest the time and get this up and running and the users decide they
don't want to wait a day? It depends on your users and your industry. For
financial data, they would probably be okay with the day lag. But
manufacturing users would not tolerate that.
Dennis Williams
- References:
- RE: Reasons for not considering Logical Standby Databases for Reporting purposes
- From: Ric Van Dyke
- RE: Reasons for not considering Logical Standby Databases for Reporting purposes
- From: Carel-Jan Engel
Other related posts:
- » Reasons for not considering Logical Standby Databases for Reporting purposes
- » Re: Reasons for not considering Logical Standby Databases for Reporting purposes
- » Re: Reasons for not considering Logical Standby Databases for Reporting purposes
- » RE: Reasons for not considering Logical Standby Databases for Reporting purposes
- » Re: Reasons for not considering Logical Standby Databases for Reporting purposes
- » RE: Reasons for not considering Logical Standby Databases for Reporting purposes
- » Re: Reasons for not considering Logical Standby Databases for Reporting purposes
- RE: Reasons for not considering Logical Standby Databases for Reporting purposes
- From: Ric Van Dyke
- RE: Reasons for not considering Logical Standby Databases for Reporting purposes
- From: Carel-Jan Engel