asked on

Replica sans attachments

I want to replicate some databases that are huge in size, primarily because of attachments. THere are replicas of the databases on user workstations. There is no utility of attachments on the workstation however they might want to work with the local database for read only purpose. Changes are not to be updated back to server. The no of workstations would be a couple and the required update frequency a couple of hours.

What is my solution?

Thanks for sharing your expertise.

ASKER CERTIFIED SOLUTION

HappyFunBall

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

RanjeetRain

ASKER

Nope. Those workarounds aren't as neat as I want. 40K method ain't good anyway. These documents might be under 4K wihtout attachments. Why spend 40K?

Programmatic solution, is the first thing that comes to mind but also the last thing I am looking at.

HappyFunBall

Actually, I just noticed in R6 there's an option to choose what size limit you want for attachments. Try to create a new replica and click the More Options button before hitting OK. Change the receive documents from server option to Partial Documents, then change the "Limit attachment size to" field to 0kbs.

It worked for me - documents were replicated but not the attachments.

RanjeetRain

ASKER

Seems, it was necessary to give the version. R 5.0.3 - 5.0.8

HFB, that would just be what I am looking for. Could you please see if there is something of the same kind in R5?

HappyFunBall

I've been looking around but can't find anything better than the < 40KB idea to use in R5. I've been thinking about how to do this programmatically and that seems like a nightmare.

I'm reaching, I know, but if you have even one R6 server in the environment and people replicate with only that server then the attachment size limit idea could work.

I'll keep thinking...

RanjeetRain

ASKER

Lets hope you come out with some smart workaround.

HappyFunBall

I've been thinking about this now and then and nothing has come to mind. I guess for a programmatic solution, you can create a database copy which users will replicate from. This copy will be maintained by agents that update it from the original database. Basically, you can just write an agent to do a loop through all docs of the original db. During the loop, do a subloop that scans all the items in the original doc. Copy all items to the database copy that are not of type RICHTEXT.

Actually as I think about it, that isn't too bad of a workaround. It shouldn't take too long to write that. Let me know if you need help writing the agent.

RanjeetRain

ASKER

Okay, time to close this one. Thanks for all the help HFB. I wish there was an easy way to do this without writing code. Thanks anyways.