bloated database

[SpaceMonkey]

Greetings

I have inherited a replicated database which is now large and unmanagable. It has been replicating every minute for the last 18 months and as a result there are 300000 records in the MSysExchangeLog table where Access has added a record for each replication.

I would like to delete some but can't as the table is read-only. Does anyone know how I can rid myself of these seemingly useless records?

 

[Parker]

Greetings

I have inherited a replicated database which is now large and unmanagable. It has been replicating every minute for the last 18 months and as a result there are 300000 records in the MSysExchangeLog table where Access has added a record for each replication.

I would like to delete some but can't as the table is read-only. Does anyone know how I can rid myself of these seemingly useless records?

Drink 3 botles of Jack Danniel's through a straw and go home early. You won't see them

 

[SpaceMonkey]

tried that and it worked... fantastic!! Should help with all my helpdesk calls as well!! Thanks!!!

 

[neileg]

When you've sobered up and the headache has mostly gone away, you could create a new database and import all of your objects from the old one. Other than that, I don't know.

I just wonder why would you replicate every minute.....

 

[SpaceMonkey]

When you've sobered up and the headache has mostly gone away, you could create a new database and import all of your objects from the old one. Other than that, I don't know.

I just wonder why would you replicate every minute.....

It was replicated so often so changes would reflect quickly and increase workflow but it isn't really necessary - I've changed it so it updates every ten minutes now.

I've re-imported all the objects which does get round the problem (the system tables won't import anyway).

The moral of the story? Don't replicate often otherwise you get database bloat

Cheers and thanks for the advise

 

[DBL]

Just curious to know what your set up is. Is it a multi-user database, is that why you are replicating? If it is no multi-user can the backend no reside on the server so that everyone access it direct to stop the need for replicating completely?

 

[SpaceMonkey]

Just curious to know what your set up is. Is it a multi-user database, is that why you are replicating? If it is no multi-user can the backend no reside on the server so that everyone access it direct to stop the need for replicating completely?

Yes, it's a multi-user database spread over two sites. One is updated via the web and sits on a secure server in the IT building and the other is sited the other side of town using an Access Front end with extra functionality. They're conected by a WAN.

The WAN is percieved to be to slow to cope with Access and security issues are less complicated. But I wonder wheather the real reason it was implemented like that was because the guy that i replaced wanted to try out replication cos he hadn't done it before!!