I don't know what your application looks like, but we're handling a similar situation by using several databases in a single cluster. In our case, the apps are JDBC-based, so it is possible to open a connection pool to each database & easily point the same application code at different sources. This does *not* allow queries across the databases, but *does* allow us to use a single instance of the application to serve up data from different databases depending on who is asking for it. Would this address your needs?
-Nick -------------------------------------------------------------------------- Nick Fankhauser [EMAIL PROTECTED] Phone 1.765.935.4283 Fax 1.765.962.9788 Ray Ontko & Co. Software Consulting Services http://www.ontko.com/ > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Ravindra Wankar > Sent: Thursday, December 20, 2001 2:02 AM > To: [EMAIL PROTECTED] > Subject: [ADMIN] Data partitioning > > > > We offer a web based application to companies. By keeping a company_id > in the schema we differentiate the data amongst companies. e.g the user > table has a company_id field to distinguish users between companies. > > However, most companies are feeling "insecure" about their data not > being stored separately from others. Also from a maintenance perspective > it seems it might be better. e.g restoring the data of an individual > company will be impossible. > > Is there a way to handle this? Preferably using a single database? > > Thanks, > -- Ravi. > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED]) > ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
