Confusion regarding database migration
Hello,
Our ServiceDesk Plus (on-premises) installation is currently in the process of dying. Features break permanently each passning month, database entries get corrupted, backups fail for unknown reasons. Installing new service packs only made it worse, we suspended our regular maintenance windows last summer (all the posts here about serious bugs they introduced recently makes it seem like a good decision).
We contacted our national ServiceDesk Plus distributor, and they recommended a full conversion/migration from Microsoft SQL to PostgreSQL, to rule out (and hopefully resolve) eventual database issues. So far so good, but when you start looking up guides/documentation, there's lacking or contradictory information in different places:
No mention of the MSSQL -> PGSQL migration path at all.
Just instructions for the MYSQL -> MSSQL / PGSQL and MSSQL -> MSSQL paths.
Vague instructions, are they only valid for PGSQL -> MSSQL, or do they apply for MSSQL -> PGSQL as well? Uses the backUpDataOld.bat script, is this information still current? Backup generates an .ezip archive (but requires a .data file), we tried extracting the archive and restoring all the .data-files within individually, this failed in our test environment. Also tried backUpData.bat, this failed with the error "Problem while taking backUp"?
This seems like the most convenient option, and it covers our MSSQL -> PGSQL migration path. However, we cannot find any references or mentions of this tool anywhere whatsoever (not here on PitStop, nor anywhere else on the Internet). Do we even dare try using this, is it some kind of long-forgotten abandonware?
So my question is:
How do we even proceed with this database conversion/migration?
Currently running:
ServiceDesk Plus 14.3 Build 14304, with (remote) Microsoft SQL Server 2014 (Build 12.0.6444.4 - SP3 CU4 GDR).