I recently changed my PACS Server and I decided to use a stronger and faster DB (I used integrated SQLite before) so I configured MS SQL Server (2019) on Windows Server 2016 and the latest Conquest PACS 1.5.0 b.
I quickly faced some big issues.
Basically, PACS is OK at first but process dgate64.exe start to use more CPU (not so much ,about 5% instead of 0.5% max usually) and more RAM. At some point, memory grows to reach hundreds of Mb or even till 4 Gb and Conquest becomes unusable or simply crash. It got worse and yesterday I had to restart Conquest service about 4 or 5 times.
Looks like a memory leak but after a few days digging logs I couldn't find any explanations or serious leads.
Since yesterday evening, I put an older version of dgate64.exe (1.4.19 d2) and it seems to be stable now, no more RAM eating or abnormal CPU use.
Question 1: I would like to know if some of you are using latest 1.5.0b with MS SQL and if you have some issues too, or if you set specific settings.
I saw there are big additions in 1.5.0, especially multi threaded moves and forwards, don't know if this is related.
Question 2: Other issue but I guess that is not a new one (because before I set the new server, I had one instance per modality, and I decided to move all to a single instance).
Queries give no results if I check more than 1 modality as a filter (eg. DX + MR : 0 results ; no filter 25 results).
I tried the procedure described in the following thread,
without success: no change it works for Horos and Radiant but is not functionnal for MicroDicom, I can't figure out why this is different.
Any help or feedback will be appreciated, clinicians are going to hate me for this change, maybe it is too late