svanderclock wrote:

>
> a table that have no primary key (cause don't need) it's good or not ?

Generally having a primary key is good and not having one is bad.
Most replication systems don't work with tables without primary
keys.

>
> the table it's only to log the error in the app
>
> Table Error_Log
> Date Timestamp default 'NOW'
> Data Varchar(10000)
>
> or i must add an primary key, even if we will never use it ?
>

You might use a generator/sequence to create an artificial
primary key, maintained with triggers. It might be useful
if you get two errors with the same timestamp - the primary
key will indicate their order. Or you might decide that
you don't plan to replicate this database - or that table,
and skip the whole thing.

Good luck

Ann