One database or three? How does one know how many databases to set up?
Keith Kratochvil
We are building several applications that will access our database(s) (SQL
Server 6.5). We are not sure how many databases to set up. The databases
are somewhat related. For example, one set of data would be financial data
(such as journal entry stuff). The information in the financial database
would be related to the other two databases (lets say employees and
customers for the sake of argument). Information in the two databases would
be independant of each other.
We plan on building applications which will be deployed in-house as well as
some web applications to enter and display the information that we have
within the database(s).
The real question is how many databases should we set up? Would one large
database be better because we can set up referential integrity across
everything, or are we better off splitting up the databases into three
separate entities? What performance issues should we consider in making our
decision? Are there any other issues to be made aware of that will help
influence our decision?
Thanks for the help!
Keith Kratochvil
Richard Waymire
The biggest issue will be your RI - you'll need it all in one database to
use it successfully.
--
Richard Waymire, MCT, MCSE+Internet, MCSD, MVP (SQLServer)
Senior Principal Instructor/Consultant, ARIS Corp.
President, Pacific NW SQLServer Users Group (http://www.pnwssug.org)
Visit us at http://www.aris.com
Keith Kratochvil wrote in message
<#nu0NoKa...@uppssnewspub05.moswest.msn.net>...