ER ... yes / no ?
Posted in 2003
Topics: High Availability & Replication, Performance & Tuning, Stored Procedures & SPL, Versions, Editions & End-of-Life
IDS 7.31 FD3 Solaris 8 I know this statement is a bit vague, but if I have the choice to use Enterprise Replication or not, should I go for it ? IE. does 7.31 have serious issues with ER ? Is it difficult to maintain ? ** background ** I am asking this because we are completely redesigning our system, and would like to split up the business units into separate entities, sharing tables between each other. ER would be the best in terms of performance & downtime of individual business units, but what are the cons ? I understand the theory behind ER, and what it is capable of. I don't have practical experience with ER, and a couple of questions come to mind: 1. What happens if I loose integrity on a table ? 2. What happens if I disable ER for some reason ? 3. Is this efficient on a system that has many inserts (very busy) ? Maybe you can give me some tips / suggestions ....... Dirk Moolman Database and Unix Administrator MXGROUP "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." -Albert Einstein sending to informix-list
Dirk Moolman wrote: > > > IDS 7.31 FD3 > Solaris 8 > > > I know this statement is a bit vague, but if I have the choice to use > Enterprise Replication or not, should I go for it ? IE. does 7.31 have > serious issues with ER ? Is it difficult to maintain ? > > > ** background ** > > I am asking this because we are completely redesigning our system, and > would like to split up the business units into separate entities, sharing > tables between each other. ER would be the best in terms of performance > & downtime of individual business units, but what are the cons ? > > I understand the theory behind ER, and what it is capable of. > I don't have practical experience with ER, and a couple of questions come > to mind: > > 1. What happens if I loose integrity on a table ? > 2. What happens if I disable ER for some reason ? > 3. Is this efficient on a system that has many inserts (very busy) ? This sounds like a very bad idea. ER in 9.30 is OK, especially good in 9.40 where you can mix in HDR, but unless your company is a f***ing huge multinational, your probably going to be better off with a decent server and everything in one database. -- "C'est pas parce qu'on n'a rien ''' dire qu'il faut fermer sa gueule" - Coluche