Does anyone know the database size limits on the Kpacs server software?
I have been using Efilm, but have run into the 4gb max database size imposed by SQL express.
I have around 6 million raw dicom files, massing about 450 gb of space.
I am looking for some sort of server software to use for a PACs to store these files, something that can grow bigger, and can be queried, etc.
I would use the conquest conquest server with mysql oder mssql2005 as databease. That would solve your probs.
I guess, the database of k-pacs is less than 4 GB.
I too suggest Conquest. It works (worked...) flawlessly with 1.4 * 10^6 images, 750 Gb of size. However, if you have to rebuild your database, e.g. if you switch to a larger disk, this becomes a tedious task. The "regen" or "re-initialize" feature of Version 1.4.12 alpha slows down to approx 2 images in 3 seconds after approx 800 000 images and continues to slow down. If you don't have time to wait for weeks for the rebuilt of the db and stop the regen, you are left with a working database, but an incomplete and painfully slow one.
So actually the only fesible approach appears to be to copy smaller chunks of the files (in the range of 50-100 000 images) to other pcs, import them there into other conquest db, and send them from there via dicom to the main db. This is a task for days :(. I don't know if there actually is available a streamlined integration of conquest with mysql and a pref file/ini-file appropriate for larger db, but two years ago (the time when we started our 'provisorial' conquest-PACS) there wasn't any.
I would be interested in any suggestions.
Kind regards
Since the K-PACS database is still text file based you have the limitations of your underlaying file system. But we do not recommend to have more than 20000 studies since db operations will become very slow.
Hi,
the rebuild function of conquest should be much faster on newer releases.
Marcel
Don’t have an account yet? Register yourself now and be a part of our community!