Hi all,
I am not very familiar with the ‘dark’ side of Business Objects (the repository, dlls, .keys, oraenv.whatever 
I could not fathom how to search the archives for my answers to this one so forgive me if this is repetitive.
We have a production repository. The database in which it resides is sometimes dropped for backups, releases, etc. We are getting ready to develop a new universe and report set to support business processes that are critical and cannot be subject to frequent outages.
Can we/should we make a new, second, production repository to support this reporting? Could we alternatively point our existing repository to a different database during outages so the repo and the data would be available for reporting because these databases would not be down? If we must create a new repository, can it and the ‘meaty employee data’ be housed in the same database?
Thanks in advance. Any and all suggestions are appreciated and welcome!
Cindy
Cindy Clayton - Business Objects Consultant AT&T
336.698.2144
Give people more than they expect and do it cheerfully. Talk slowly but think quickly.
Smile when picking up the phone. The caller will hear it in your voice. Mind your own business.
Learn the rules then break some.
Judge your success by what you had to give up in order to get it.
Listserv Archives (BOB member since 2002-06-25)