Re: [cms-list] CMS co-mingled data issue

[Charles Reitzel]

In all likelihood, co-mingled data will cause many more problems than it will solve. It will complicate data replication, Application availability (think SLAs for each user group), backup/restore, access controls. The list goes on. The only time co-mingling would represent an advantage is in a static, unchanging environment. But it's been a while since these have been seen in the wild...

take it easy,
Charles Reitzel

At 01:28 AM 2/17/2003 -0500, tonyl/pillarsoftware wrote:

Has anyone looked at IBuySpy?

It requires a separate database installation for each instance that is running. EVEN on the same server each IBuySpy would require a different DSN.

Something like Yahoo Groups is an example of co-mingled data.

I wonder how many CMSes/Portals support co-mingled data?

IMHO co-mingled data is great because you can manage schema and database backups...and from an ISP view point it saves resources.

Opinions? Pro / Con for co-mingled data.

--
http://cms-list.org/
more signal, less noise.