Exocad CAD-Data merge

[Akki]

Hi Guys,

Is there a way to merge database into one?
I have 3 station, and we started working with default settings where every station created its own CAD-Data (folder/dB).
I would like now to merge them all and share between stations so same db is accessible to all to load/save data.

Thanks

 

[a3dl]

windows network your cad data folder

 

[Akki]

Yes, that the plan for final step.
But first i have to see if I can merge 3 dB's

 

[a3dl]

We just keep all our work parameters the same in data base and use one computer as "server" all our design stations are networked which we can see any case from any computer. I hope I am understanding your merging DB question

 

[Akki]

We just keep all our work parameters the same in data base and use one computer as "server" all our design stations are networked which we can see any case from any computer. I hope I am understanding your merging DB question

I guess we are at misunderstanding

Yes, that's the idea but currently, as explained in my 1st post, we have 3 separate stations meaning 3 separate CAD-Data folders with individual sqlite file.
Moving just project folders will not merge sqlite data, therefore; i need to see if there is a way of merging sqlite/s

 

[TheLabGuy]

I guess we are at misunderstanding

Yes, that's the idea but currently, as explained in my 1st post, we have 3 separate stations meaning 3 separate CAD-Data folders with individual sqlite file.
Moving just project folders will not merge sqlite data, therefore; i need to see if there is a way of merging sqlite/s

then you need to create one 'cad-data' file and network it to those three computers. then output your exocad to that networked cad-date file. Makes it much easier for everyone in the lab, especially milling department when you have many mills. By the way, i have seven stations and have exocad and 3Shape mixed into but they all drop into one centralized cad-data folder. This makes it easier to back up as well, because you will have to do this periodically.

 

[Akki]

then you need to create one 'cad-data' file and network it to those three computers. then output your exocad to that networked cad-date file. Makes it much easier for everyone in the lab, especially milling department when you have many mills. By the way, i have seven stations and have exocad and 3Shape mixed into but they all drop into one centralized cad-data folder. This makes it easier to back up as well, because you will have to do this periodically.

Yes Rob.
New/Centralized CAD-DATA folder is already created and all 3 stations pointed to it - that part is ok.
Now, as this is a new Cad-Data folder, a new, empty sqlite (dB) file was created, which is understandable too.

But questions remains - how to merge 3 existing sqlite dBs and all files and move them to new centralized folder? Is that doable?

 

[ANoobTech]

Yes Rob.
New/Centralized CAD-DATA folder is already created and all 3 stations pointed to it - that part is ok.
Now, as this is a new Cad-Data folder, a new, empty sqlite (dB) file was created, which is understandable too.

But questions remains - how to merge 3 sqlite dBs and all files and move them to new centralized folder? Is that doable?

I don't think it's easily doable, if at all. I'm no database engineer and I don't remember much from my college SQL class but I'm under the impressions that database related data (Case files) is specific to each database (at least in the case of exocad) and cannot be transferred between databases

 

[Akki]

I don't think it's easily doable, if at all. I'm no database engineer and I don't remember much from my college SQL class but I'm under the impressions that database related data (Case files) is specific to each database (at least in the case of exocad) and cannot be transferred between databases

Thanks! That's what i though. But wasn't sure if Exoxad maybe had a tool for merging/combining.
So I suppose, I am best of just backing up current Folders with all projects, and starting with newly created dB which is shareable between all stations.

 

[ANoobTech]

Thanks! That's what i though. But wasn't sure if Exoxad maybe had a tool for merging/combining.
So I suppose, I am best of just backing up current Folders with all projects, and starting with newly created dB which is shareable between all stations.

Exocad isn't generous enough to give us a tool of such power lol

 

[Akki]

Exocad isn't generous enough to give us a tool of such power lol

Hehe.. , thanks!

 

[TheLabGuy]

Yes Rob.
New/Centralized CAD-DATA folder is already created and all 3 stations pointed to it - that part is ok.
Now, as this is a new Cad-Data folder, a new, empty sqlite (dB) file was created, which is understandable too.

But questions remains - how to merge 3 existing sqlite dBs and all files and move them to new centralized folder? Is that doable?

It's doable, you won't merge them though and you definitely won't like how it works because it would be like using teamviewer from home designing on a computer at the lab. Sure, the network would speed it up but with more than one person, no way. It's kinda like merging three different versions of windows and you want to run that program at the same time using three different workstations using that one merged version of windows...aint going to happen my friend.

 

[Akki]

It's doable, you won't merge them though and you definitely won't like how it works because it would be like using teamviewer from home designing on a computer at the lab. Sure, the network would speed it up but with more than one person, no way. It's kinda like merging three different versions of windows and you want to run that program at the same time using three different workstations using that one merged version of windows...aint going to happen my friend.

datz lil different response from your 1st one, but yes, i kind of expected that this is not doable, and as I mentioned already - thought I maybe missed a merging tool from exocad which doesn't actually exist what ANoobTech confirmed in his 1st response

So yes, thanks anyway.

 

[roju]

Merging and combining is doable but not for faint hearted, nor it cannot be done without extensive understanding of databases etc. Thing is that Order Information in Database is linked to CAD-DATA -folder (scans), to materials, to patients etc with identifiers. Also, Tables within database (like sheets in excel) may contain identifiers which act as a link to another Table: For sake of sanity of database some identifiers are UNIQUE which means no two identifiers cannot be same. When merging 3 databases, most likely there would be overlapping unique identifiers. Essentially you would have adjust those identifiers manually: this means bulk renaming, bulk editing of xml, serious SQL trickery. Heck, even i (who understands how things might be done) would refuse to do it because ensuring that things go smoothly requires hours and hours and hours of work, testing and stuff.

And i dont see reason why one would need separate Combine/Merge? Combine/Merge is pretty much like automated (bulk) export/import. Export reads data and stores that into "package" with certain format, then import reads that package and stores it to database as new order. In Combine/Merge data is red from source, and added to target as new data.

See if exocad does (bulk) export/import: export all orders from all standalone stations and import them to one.

Bulk export/import may have some limitations and not all orders might not be exportable (eg. cases that are produced elsewhere might be locked). And there is always some limitations to you export/import orders between (major) versions: always redesign and check orders you imported before manufacturing etc etc.

 

[hades2ruler]

Merging and combining is doable but not for faint hearted, nor it cannot be done without extensive understanding of databases etc. Thing is that Order Information in Database is linked to CAD-DATA -folder (scans), to materials, to patients etc with identifiers. Also, Tables within database (like sheets in excel) may contain identifiers which act as a link to another Table: For sake of sanity of database some identifiers are UNIQUE which means no two identifiers cannot be same. When merging 3 databases, most likely there would be overlapping unique identifiers. Essentially you would have adjust those identifiers manually: this means bulk renaming, bulk editing of xml, serious SQL trickery. Heck, even i (who understands how things might be done) would refuse to do it because ensuring that things go smoothly requires hours and hours and hours of work, testing and stuff.

And i dont see reason why one would need separate Combine/Merge? Combine/Merge is pretty much like automated (bulk) export/import. Export reads data and stores that into "package" with certain format, then import reads that package and stores it to database as new order. In Combine/Merge data is red from source, and added to target as new data.

See if exocad does (bulk) export/import: export all orders from all standalone stations and import them to one.

Bulk export/import may have some limitations and not all orders might not be exportable (eg. cases that are produced elsewhere might be locked). And there is always some limitations to you export/import orders between (major) versions: always redesign and check orders you imported before manufacturing etc etc.

I have merged 2 different databases but the problem is a lot of "same naming table values,ids,etc "that are conflicting between the SQLs..so you have to sacrifice a big amount of cases combining all of them to a single one

 

[with_teeth]

I'm dealing with the same exact scenario as you right now. Trying to see if my support person can combine the 3 different SQL's into one, we're hosting our cad-data with dropbox. Waiting on a response from support and went here to see if anyone else had tried... I may just give up with that idea
I see two options:
-Using one new SQL after all the projects are uploaded into one CAD-Data folder and "starting fresh" in a way
-Setting each workstation up as its own "lab" in dental db. That way they are accessible to each other through the cad-data folder, but the numbering in th DB is the same

I'm not sure which one is going to work the best. Right now I am attempting the second one and seeing how it goes. It will be worth the trouble in the end