Subject: Grouper Users - Open Discussion List
- From: Shaun Koh <>
- To: "Hyzer, Chris" <>, " Mailing List" <>
- Subject: [grouper-users] RE: DB SQL Query
- Date: Mon, 26 Mar 2018 23:01:35 +0000
- Accept-language: en-US, en-NZ
Thanks for your response.
I am not familiar with using the grouper loader though if I understand correctly from your suggestion and the docs, the sync can only be performed one-way from the existing app/system to Grouper. – or can the reverse also be done ?
The reason I ask is because (and apologies if I’ve not clarified) our cutover is phased such that both systems will actively be making changes at some point in time (due to business requirements and tightly coupled processes internal to the existing system) which requires a two-way sync for the data objects. – i.e. master-master relationship
This means after cutover, there would be no changes happening on the old system. Also, there are no privileges to migrate.
My thoughts are in line with yours in that editing the database registry directly should be avoided if possible due to the complexities involved so I am looking to spend some time evaluating if the loader could be of use to us in terms of applicability and performance.
Can you do a grouper loader job that does this pre-cutover (might take a while but that’s ok since cutover hasn’t happened), then do another run at cutover and it will be a lot faster. This assumes the system of record is the old app before cutover. After cutover I would assume you just need the diffs, or would changes still be happening on the old system? Are there privileges to migrate too?
We would like to not have people edit the database registry directly since it is a little complicated and want to make sure people don’t corrupt things… I assume you have analyzed the tables and will do so after (or during) the migration.
My apologies, yes in terms of the data entities/objects we are looking to sync just groups, stems, and memberships between the two systems.
From: Hyzer, Chris <>
you say groups, stems, memberships, etc. what is the "etc", or is it just groups, stems, memberships?
<> on behalf of Shaun Koh <>
We’re looking to perform a repeatable DB to DB sync to migrate a large dataset (and delta/changes thereafter) from our existing group management system to Grouper as we transition across.
An attempt via the web service resulted in slow performance due to the load size and tightly coupled internal processes within our existing system.
We are wondering if you could help point us to the source that includes the SQL logic for each type of group-related function/event (e.g. add/remove group, add/remove membership, stems, etc).
Please let me know if you would like some clarification on any of the above or if you have a recommended approach to performing this.
- [grouper-users] DB SQL Query, Shaun Koh, 03/22/2018
Archive powered by MHonArc 2.6.19.