US 12,443,578 B1
Systems and methods for a database archive
Peter Gassner, Pleasanton, CA (US); Jonathan Stone, Olympia, WA (US); Andrew Han, Needham, MA (US); and Graham Gelwicks, San Francisco, CA (US)
Assigned to Veeva Systems Inc., Pleasanton, CA (US)
Filed by Veeva Systems Inc., Pleasanton, CA (US)
Filed on Mar. 21, 2025, as Appl. No. 19/086,607.
Int. Cl. G06F 16/215 (2019.01); G06F 16/21 (2019.01); G06F 16/23 (2019.01)
CPC G06F 16/219 (2019.01) [G06F 16/215 (2019.01); G06F 16/2358 (2019.01)] 20 Claims
OG exemplary drawing
 
1. A method for archiving data records in an archive repository, the method comprising:
modifying, by a content management server, a first data record;
generating, by the content management server, a first change data record based on the modification of the first data record;
selecting, by the content management server, a repository status;
storing, by the content management server, the first change data record in a first repository based on the repository status,
wherein the first repository is configured to store data records;
determining, by the content management server, the first repository includes a first plurality of change data records that includes at least a first threshold number of change data records;
determining, by the content management server, a second repository includes a second plurality of change data records that includes at least a second threshold number of change data records,
wherein the second repository is configured to store data records, and wherein the first threshold number and the second threshold number are equal;
retrieving, by the content management server and in response to: the first plurality of change data records of the first repository including at least the first threshold number of change data records and the second repository including the second plurality of change data records including at least the second threshold number of change data records, the second plurality of change data records of the second repository;
generating, by the content management server, a plurality of change files,
wherein each change file includes at least one change data record of the second plurality of change data records, and wherein the archive repository is configured to store data files;
storing, by the content management server, the plurality of change files in the archive repository;
selecting, by the content management server, the repository status;
modifying, by the content management server, the repository status;
modifying, by a content management server, a second data record;
generating, by the content management server, a second change data record based on the modification of the second data record; and
storing, by the content management server, the second change data record in the second repository based on the modified repository status.