Question

Cross Database Chaining

Updated February 7, 2018

asked on February 7, 2018

We have a custom database called "Custom_LF_Data" that we use for creation of views and stored procedures that reference other databases in the system, including the Laserfiche databases (LFDS, Repo, WF etc.). Users typically get access to the data via an Excel file linked to certain views for reporting. We have encountered some issues now with creating a view, then giving the AD user account of the end user access to that view (as opposed to using a SQL login). We can address the access permissions issue we have, but need to clarify we don't break anything.

The Question from the DBA:
Can we enable cross database ownership chaining to allow views created in our "Custom_LF_DB" database to reference tables in other Laserfiche databases without having to grant permissions on individual tables in the Laserfiche databases? The script in the screenshot below is the view that requires to cross database ownership chaining.

0 0

Answer

SELECTED ANSWER

replied on February 7, 2018

I'm not really understanding how this database ties into Laserfiche software. Cross database access granted to some AD users doesn't change how Laserfiche is accessing its own databases or affect that access. Laserfiche doesn't query across databases.

0 0

Replies

replied on February 7, 2018

Would it make more sense to sync the data (workflow or SDK) from the view to the documents as field data? Give field access to the users that need it.

We have also used database triggers to do this. When docs are created or certain fields are edited (the ID field value), the trigger runs: queries the other data view and updates the template fields.

0 0

You are not allowed to follow up in this post.

Question

Question

Cross Database Chaining

Answer

Replies

Sign in to reply to this post.