Do you need to speed up your edit sets? Check out the tips below.
Edit sets are interesting. If you have a 1GB HEAT system and perform several changes and then commit, the edit set could take several hours to complete. To improve this, you can make a few changes when committing the edit set and find the process to be a lot shorter.
The following are some best practices for edit sets:
Commit Locally: Try and commit the edit set on the same server the database is on as it keeps the data local. If your policy does not allow you to run the Admin tool on the SQL server, then keep the edit sets small. One table at a time, on a machine that shares the same network switch to limit the the possibility of a network failure during commit.
Consider Your Changes: The changes you make directly affect the length of time of the commit. For example, if you add a field to the CallLog table, which has 750K records, those 800K records will have to unload, then load back into the table after the commit adds the new field. If you make several changes to the CallLog table, it will only unload and load those records once. If you have many changes to make in one table, do it all at once, instead of making multiple commits. The same rules apply to all other tables.
Know How Commits Work: Edit sets commit the tables alphabetically. HEAT's main tables are Assgnmnt, CallLog, Config, Detail, Journal, Profile, and Subset. You will know that your edit set is almost done when you see the Subset loading back in.
What Type of Change is Appropriate: Adding, renaming, changing field types, and removing fields and tables require an edit set. Marking a field read-only or required, setting a field to validate or autofill, along with normal form changes only require a quick customize. A quick customize with 750K records only takes a few seconds.
Always back up your HEAT system before making any changes.