truncate on checkpoint not truncating

The log on one of my databases keeps filling up, even though I have it set to truncate on checkpoint. the only real difference between this database and the others on my server is that it is built from the dump of another database (on another server) where the tables are marked for replication.

I'm wondering if the fact it is built from a replicating database could be causing this. I've noticed I can't drop any of the table, even though my database isn't set to replicate (or publish).

two questions
1) Any ideas?
2) Is there anyway I can make my server realize I'm not replicating so it will let me drop those tables? (nothing in Enterprise manager indicates that my database is replicating or publishing).


Thanks,
Jim

Jim,

See below how to purge the log.
Dump Tran YourDataBaseName with No_Log
Use YourDataBaseName dbcc checktable (syslogs) with no_infomsgs

This is for information, in fact I suggest to read carrefully the documentation about Log Strategies. The option that you will take depends of your application. Here we don't know what goes behind the scenes.

Regards
Patrick


On 12/30/98 9:40:30 AM, Jim Craddock wrote:
> The log on one of my databases keeps filling up, even though I have it set
> to truncate on checkpoint. the only real difference between this database
> and the others on my server is that it is built from the dump of another
> database (on another server) where the tables are marked for
> replication.

I'm wondering if the fact it is built from a
> replicating database could be causing this. I've noticed I can't
> drop any of the table, even though my database isn't set to replicate
> (or publish).

two questions
1) Any ideas?
2) Is there anyway I can
> make my server realize I'm not replicating so it will let me drop those
> tables? (nothing in Enterprise manager indicates that my database is
> replicating or publishing).


Thanks,
Jim

Check your recovery interval setting. If set too high (30 min. etc,) the log will fill up and not have a chance to truncate.
On 12/30/98 11:05:35 AM, Patrick Fediere wrote:
> Jim,

See below how to purge the log.
Dump Tran YourDataBaseName with
> No_Log
Use YourDataBaseName dbcc checktable (syslogs) with
> no_infomsgs

This is for information, in fact I suggest to read
> carrefully the documentation about Log Strategies. The option that you will
> take depends of your application. Here we don't know what goes behind
> the scenes.

Regards
Patrick


On 12/30/98 9:40:30 AM, Jim Craddock
> wrote:
> The log on one of my databases keeps filling up, even though I
> have it set
> to truncate on checkpoint. the only real difference
> between this database
> and the others on my server is that it is built
> from the dump of another
> database (on another server) where the tables
> are marked for
> replication.

I'm wondering if the fact it is
> built from a
> replicating database could be causing this. I've
> noticed I can't
> drop any of the table, even though my database
> isn't set to replicate
> (or publish).

two questions
1) Any
> ideas?
2) Is there anyway I can
> make my server realize I'm not
> replicating so it will let me drop those
> tables? (nothing in
> Enterprise manager indicates that my database is
> replicating or
> publishing).


Thanks,
Jim