I have to run MobiLink synchronization with the -tu parameter due to the database design so I cannot change that.
Yesterday a yearly cleanup was performed in the database, altering some ten-thousand rows and creating new ten-thousand rows (approximate)
Now I have 13 000 000 transactions/log offsets to synchronize from the remote database which in it's own should not present any problem.
This creates a temp file with the size of 92 gigabytes (!)
The database file is 89 megabytes and the transaction log file is 497 megabytes.
How is it possible that the temp file for synchronization becomes to large ?
Add to that; there are 15 remote databases and one consolidated located on the server. The temp files does not seem to be cleaned up immediately, in a worst case scenario with scheduled synchronizations triggering one-after-another, should we estimate that we need about 1,5 terrabyte of free space to hold the temporary files ?
asked 30 Aug '13, 03:03