DCM4CHEE Store to Two Databases

[rmarino14]

Hello,

Can dcm4chee be configured to talk to two MSSQL databases?

Thanks

[Luis Silva]

Hi rmarino14

I don't quite understood what is the cenario that you may develop.If you could explain better the cenario more help will come.
In meantime I will let you a link http://forums.dcm4che.org/jiveforums/thread.jspa?messageID=1794
that could help.

[rmarino14]

In this situation I'm not using dcm4chee as a PACS, I use it to store all of the tags of the DICOM header into the database so that I can create reports from it. The reason I want to store to two databases from one dcm4chee instance is to save on SAN space. I don't need the second copy of the DICOM file but access to the data in the database in another environment. I hope I explained this better for you and thanks for replying.

Bob

[Alvaro G. [Andor]]

I'm trying to guess your setup, let me know if I'm correct:

• You have a "real" dcm4chee PACS in production where you store all your images
• That dcm4chee uses MS SQL Server as a database backend
• You want a real time copy of that database to create reports or doing analysis, so you thought of setting dcm4chee to write to two different databases and then use the second one for that matter without disturbing the production performance

If I got it right, what you need is a read only replicated slave server, it's pretty common on database world for doing reports, backups, analysis or enhance performance.

What you do is set one of those secondary/slave servers, you put your master to replicate to it, and you point your report tools to the secondary one, while you are happily receiving the dcm4chee load on the master one without being worried for locking it with huge queries.

I'm not familiar with the MS SQL world, but AFAIK is called "transactional replication" ('transactional' because it resends every sql transaction to the slave servers), and you can try what looks like an easy tutorial, here: http://www.techrepublic.com/blog/howdoi/how-do-i-configure-transactional-replication-between-two-sql-server-2005-systems/123

Important: remember that replication is one way only, and you can only READ on the slave server. If you change or modify the data on the secondary server, you can break the replication.

Have a nice day!

El 12/07/13 15:52, rmarino14 escribió:

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at http://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/groups/opt_out.