Hi Team,
With the recent release of Pulse 7 and it’s optimization of OpenSearch, one of our clients is looking into migrating their data from SQL back into OpenSearch.
Do we have any steps on how to achieve this? I believe to have Pulse start using OpenSearch for storage again we’d need to just undo the configurations in the Pulse.cfg file and restart, but is there any way to import the data from SQL to OpenSearch?
Thank you,
Nikita
Hi @nmaydanyuk,
What kind of SQL data are being referred to here? Like external data that is not for Pulse consumption?
cc: @ecarmona
Cheers,
Paul
Hi @plim!
I mean after a customer has configured Pulse to migrate the data to SQL through the Pulse.cfg settings, how do they reconfigure it back to use H2/Openshift and migrate the data back?
Thank you,
Nikita
Hi @nmaydanyuk,
Though it is theoretically possible to go back to H2 after moving to MSSQL - we do not recommend it and is not officially supported. There is no steps published at the moment for that.
Cheers,
Paul
Hi Paul,
That’s interesting, it seems quite simple and Pulse has something built in to migrate the data over to SQL, but not back? We should maybe mention that this is not reversible in the documentation then, would be an important warning to give.
But also if you just remove the SQL connection settings from the Pulse.cfg file and restart Pulse, would Pulse not migrate back to the native DB? Or at least go back to using it even if it doesn’t migrate the data back?
This is the article for reference: Pulse Database Migration into MS SQL Server
Thanks,
Nikita
Hi @nmaydanyuk,
That’s interesting, it seems quite simple and Pulse has something built in to migrate the data over to SQL, but not back?
We appreciate the feedback, however not everything is always simple as it seems. These things needs to be analayzed, assess for impact, to be tested properly and then there things to consider after. There are a lot of factors involve than just migrating data like database size for example. Memory consideration is also a factor. There is also a number of advantages of a more robust MSSQL vs H2 especially for larger dataset and scalability.
We should maybe mention that this is not reversible in the documentation then, would be an important warning to give.
Noted, with thanks! cc: @Vincent ,
But also if you just remove the SQL connection settings from the Pulse.cfg file and restart Pulse, would Pulse not migrate back to the native DB?
No.
Or at least go back to using it even if it doesn’t migrate the data back?
Yes it will go back to using H2 without migrating data back. Going back to your first question for clarity,
Cheers,
Paul