I believe your question goes beyond the Pulse as product itself and rather , I suggest to follow Amazon’s procedure, this has its variants by database, but according to Amazon’s documentation [1] and [2] is completely possible.
Now, once the database is on SQL Server RDS[1] the only thing to do from the Pulse side is to configure the SQL server connection in the Pulse.cfg.
For non default Pulse databases, I believe yes - one would be reliant on the client DBA.
(for the default H2 database one can access it via the browser with the right user credentials)
Can you maybe give some more detail on what the client wants to target?
E.g. does the client want to remove data prior to a specific point in time?
Or maybe target specific entities/years etc.?
Also ran into the same issue with an on-prem SQL Server migration to Amazon RDS. Per AWS documentation, the recommended approach is using the native backup and restore functionality, but Pulse does not work after migrating the database to RDS. Pulse throws all sorts of connection errors and cannot insert into the database, even though we’ve triple checked the connection settings in the pulse.cfg. I suspect it has something to do specifically with RDS and how the backup and restore functionality works because doing so locally works just fine.
Our client is not as concerned with the historical pulse data so much as they are with the configurations like users/groups, alerts, etc., so we have proposed using the import/export method to selectively restore the tables that house Pulse configurations. We’re hoping this will method will work since we’re fresh out of ideas
Hi, Is there an option to transfer back Pulse data (users/groups), configurations to default H2 database from SQL Server ? We are in the same situation where we are trying to consolidate RDS SQL Server instances in AWS and found out that restoring the tables to new db is causing all kind of connection issues. We tried restoring selective tables that has configuration details, but ran into referential integrity issues.
No, there isn’t an easy way to go back to H2 but you could use SQL Server or SQL Server Express. We recommend the full SQL Server but some customers have used the Express version which is free but has limitations.