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

"Dirk Moolman" <DirkM@mxgroup.co.za> wrote in message news:<bk9fjf$4dl$1@terabinaries.xmission.com>...
> 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 ?
It depends on what you're using it for.

> does 7.31 have serious issues with ER ?
No, but you have to get the configs just right.

> Is it difficult to maintain ?
Startup took a lot of effort. We spent a lot of phone support time
getting
around some undocumented features. After we set ours up initially, we
ended up locking up the production database for 2 hours when we
exceeded some mis-configured thresholds. After the first 2 months, it
ran flawlessly.
>
>
> ** 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 ?

You'd have to give me more info on 'sharing tables' Couldn't just
connect remotely and get the same result?

>
> 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 ?
If data is deleted from instance a, it will also be deleted from
instance b, and pretty darn quick. Replication does not save you from
that. If the machine containing instance a goes offline, then b can
carry on for awhile depending on
how much log space you've allocated. We have 36-48 hours worth of
logs on each server. We've run 3 Disaster Recovery trials where the
primary server has been shut down for 24 hours and we've run off the
backup.

> 2. What happens if I disable ER for some reason ?
You can suspend ER or shut ER off. The transactions accumulate or
not, depending on how you "disable" it.

> 3. Is this efficient on a system that has many inserts (very busy) ?
IMO, yes. We use it on a OLTP system but our transactions all flow
from primary to backup. YMMV, becuase your idea of busy may be
different than mine.

>
>
> Maybe you can give me some tips / suggestions .......

Upgrade to at least 9.3.


>
>
>
> 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