There are many implications to consider from performance, security and
maintenance points of views. Given the limited info, we can ask some
of the following questions that comes to mind very quickly:
* Does the reporting application require additional indexes to run
fast searches, which might negatively affect the transaction database?
* Are intermediate tables required / utilized by the application for
complex reporting purposes? (Although their usefulness is highly
debated)
* Is the separate reporting database on a different server which might
be serving as part of a scale-out strategy?
* Does the reporting application require specific database /
connection parameters which might not be applicable to the main
database?
* Does the reporting database also a carry a role like providing some
redundancy or data history? E.g like a snapshot database?
James
The Reporting database does have a couple of Indexes on it that the main
database does not have...
It also is not used as a Reporting Database as you would expect, it merly
delivers lists and lookups for past items
which are contained in the main database....
DaveL
"nidaar" <nid...@gmail.com> wrote in message
news:c65ad85c-b3f5-41e8...@k20g2000vbp.googlegroups.com...