Guy,

If you don't intend to do any RI between the two sets of tables, then you will be okay putting them in two separate databases.

Any difference in query time will come from your hardware, actually. If you have a nice server with plenty of RAM and a fast RAID setup, your queries should execute just fine.

If you don't have any client-side logic in your transactions, they will be fine too.


>Hi Keith,
>
>Thanks for the response.
>
>Thanks for the suggestion about the prefix, actually we are doing this now for any objects that we create on the database, if not it would be a total mess.
>
>
>"Not to mention inserts, updates & deletes, which would require some sort of quasi-referential integrity checks being performed on the client."
>
>What do you mean by quasi-referential(hispanic here), you mean that you have to do your own referential integrity instead of using SQLS2000's Diagram? Well, we wouldn't include any tables from the accounting software in the diagram regardless if the custom database is in the accounting database or not. So if this is not an issue, then the only issue would be the query time and maybe transaction processing. Does joining one table to another table in another database (within the same server) take a big hit as compared if both were on the same database? How about transactions?
>
>
>Thanks.