Question

Add field to existing repository

Laserfiche

Updated June 23, 2020

asked on June 22, 2020

Hello,

We have a repository with about 290 templates and 1723365 documents. We need to add a field to each of these templates. We would add the field on each template at a time. Each template has about 50000 documents which would get updated. Wanted to know the impact on the database and if there is anything we should be aware of.

0 0

Replies

replied on June 22, 2020

If we are talking about modifying the template definition to add the field, then the impact is minimal. No documents will be updated in the process. Once it's part of the template, the field will automatically be displayed on documents (though, obviously, it would be blank or use its default value).

If you want to set a value for each document, then each document would be modified, so there would be more work in SQL, but still unlikely to cause problems. What exactly is the concern over SQL load?

It's not clear to me whether you're planning to do this by modifying the database directly, but, just in case, directly editing the database is not supported.

1 0

replied on June 22, 2020

Not modifying the database directly. Adding the empty field to the templates by template definition in admin console. Later users would add a value to it as required.

0 0

replied on June 23, 2020

I just tested adding a field to a template assigned to over 9,000 records. There was a 5-7 seconds period of 'working' as it added the field to each document in the SQL Database. And a 2-3 second period where it was deleted from the database when I removed it from the template.

So, yes, there will be some impact. If you are already taxing your SQL server, you may want to do this outside of standard business hours, or during a maintenance schedule when access is already expected to be diminished.

1 0

You are not allowed to follow up in this post.

Question

Question

Add field to existing repository

Replies

Sign in to reply to this post.