Database Replication Problem

[michaelak117]

I am currently attempting to replicate my database for mobile use, but continue to get the error that either "the database has exceeded the 2gb capabity or there is not enough room on the disk", which neither are the case. I am simply trying to convert it to the design master and cannot get past this point.

The database is very large at about 500mb right now, I have just replicated others which are almost identical that are at about 400mb. I can't seem to understand why I can't replicate this one but must get it done.

Does anyone know how to get over this obstacle and get this thing replicated? Thanks

 

[!Blue]

Have you tried compacting the database before replication..?

 

[michaelak117]

Yes, it didn't seem to matter. I even tried manually bulding a repica. I created a replica with very little data and then manually ran append queries to build the database back up to its 500mb level. So I successfully reached the point of having a design master and replica, but then when trying to syncronize recieved the error that maxlocks should be increase in the registry. I max it out and still makes no difference.

I saw the saw error previously when I imported the table and tried to covert it to "replicable" under properties.

So, I just concluded that it must the size of the database that wont allow me to replicate or syncronize for the first time at that size. I've come to the realization that I may have to do all the replicating with a small database and then do as I've done and build the database along, while syncronizing throughout the process, giving a gradual syncronizations process so I will get a good reaction from the DB and no errors. I dont know.

Thanks for the reply

 

[michaelak117]

For now, atleast for this particular database I have just been working on it mobile, and saving over the other backend on the server. Meaning I replace the entire backend by saving over it with my mobile backend. Not the most efficient way obviously, but my only option right now since I obviously cannot sycronize.

 

[dfenton]

Just curious, but are you storing OLE data in your database? If not, how do you end up with such a large database? Do you have 100s of thousands or millions of records in your tables? Do you have lots of memo fields? OLE fields and memo fields have much higher replication overhead than other kinds of fields because information on each field has to be maintained seperately, since the actual data is stored in different data pages than the main record. If you have lots of memo fields, restructuring to store your memo data in a separate table, one row per memo with field for memo type, would definitely reduce the replication overhead. For instance, a table with 20 memo fields would have 20 new replication fields (one for each memo), but if you moved that to a related table with one memo per record, it would require only one additional replication field in that table.

Just some thoughts, as I've never heard of this kind of problem.

 

[michaelak117]

Good points, but I have no OLE objects or memo fields, it is either text, date, or number. And yes, I do have over a million records in this table.

 

[michaelak117]

Im considering just archiving off the database since its getting close to 1GB anyways and just starting fresh and establishing the replication feature from the start with a small table, and going from there. I'm realizing this is a funky problem and probably just has to do with the massive size of my DB, but atleast there are options and although no easy or immediate solution, something that I can fix.

 

[SOS]

Im considering just archiving off the database since its getting close to 1GB anyways and just starting fresh and establishing the replication feature from the start with a small table, and going from there. I'm realizing this is a funky problem and probably just has to do with the massive size of my DB, but atleast there are options and although no easy or immediate solution, something that I can fix.

You are replicating ONLY tables, correct (no forms, reports, macros or modules)?

 

[michaelak117]

That is correct

 

[SOS]

That is correct

Good, just checking, in case

 

[michaelak117]

Thanks