Comments
1 comment
-
Hi,
The static data population by default will pull in all the rows of data on the table you wish to link static data upon. Which with the row counts of 50,000 and 100,000 will be a performance hit. The static feature was originally added to provide lookup data that rarely changes for example zip or postal codes or country lists.
I recommend that you take a look at the Offline method offered in this help document, where you prepare a script that describes the data changes before deploying the changes to the database. Removing the requirement to add the table to static data.
Many Thanks
Eddie
Add comment
Please sign in to leave a comment.
I have a table with > 100.000 rows. Is it possible to use seed data to get the initial state and then continue using the table with migration scripts? I tried to achieve this, but when I add the table to static data tables it will then generate a full migration script and doesn't now anything about the seed data file.
Some background information:
Our team wants to use local DB for developing process. While developing we are changing static data in local DB. I would like to use Change Automation to generate migration scripts for those changes locally and then push to repo. Some of our static tables are very large > 50.000 rows and one table with > 100.000 rows. In developing process the changes will affect only 500-1000 rows of these large tables. the other rows remain the same