What is the Laserfiche policy, or recommended best practice, about creating dynamic fields tables within the same SQL database as the Laserfiche repository where it is to be used?
Will this create any issues we should know about?
What is the Laserfiche policy, or recommended best practice, about creating dynamic fields tables within the same SQL database as the Laserfiche repository where it is to be used?
Will this create any issues we should know about?
I would expect that modifying the Laserfiche database wouldn't be recommended at the very least because updates could change things and possibly cause issues.
What we've done in our environment is create separate/dedicated databases for our data source tables, in many cases on the same SQL server. I don't think you'd really gain much from having it in the actual LF database.
On a side note, that may open up a can of worms because linking that data source would give access to ALL of the tables so it increases the odds of mistakes that could impact performance.
Thanks. We are going to create the dynamic fields table(s) in a separate database.
Laserfiche documentation seems to indicate that they are not against creating such tables within the repository database -- see this link.
However, our VAR said no -- they want us to use a separate database.