Re: Designer 6.0 Architecture

>>1) Create a repository and owner(s) in each database you want to use
>> Designer with?

Typically, the repository is located on its own database. The repository has one owner and many users/developers. In our case, up to 50 simultaneous users.

>>2) Create one central database to hold the repository for many other
>> databases?

Note that the repository holds the design of the databases and applications (metadata), not the actual databases.

>>If 2) hoe do you manage the simultaneous connections from Designer to
>>the central repository and to the database(s) being worked with?

 I'm not sure I understand why you would want to be connected to the Repository and the target database from Designer, except maybe for reverse-engineering/design capture. As I mentioned above, the repository is a container of metadata. When you are ready to generate the database objects, etc., simply generate them to scripts and create them by running the scripts. In the case of reverse-engineering or design capture, Designer 2.x and above support both SQL*Net connections to the target databases and ODBC connections.

If you have any questions, let me know.

Joel

Van Messner wrote:

> What is the best way to use Designer
>
> 1) Create a repository and owner(s) in each database you want to use
> Designer with?
> 2) Create one central database to hold the repository for many other
> databases?
>
> If 2) hoe do you manage the simultaneous connections from Designer to
> the central repository and to the database(s) being worked with?
>
> Van
>
> * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
> The fastest and easiest way to search and participate in Usenet - Free!
Received on Fri Jan 21 2000 - 02:09:12 CET