Who is this article for?  

  Database administrators responsible for managing the Please Review database.

  Full database access will likely be required.

Customers have been able to move from one database format to the other using a database migration tool. We can't advise on which migration tool may be the best to use. This would be down to the database administrator to sort out.

However, a key requirement is that schema of the new database is created using our database creation script. This ensures that the datatypes of all the fields are the ones that we require.

We would recommend testing after this has completed to be sure that it all works. If you have a test license available, you might like to clone the environment for testing this, as covered here: Please Review: Cloning an Environment

One of the other key things to consider is that the Please Review instance should be stopped when making this actual change to the server. This is because, if not stopped, users may upload additional documents to reviews, make comments or changes, setup new reviews, or delete documents, etc. and if you then used the migrated database, it wouldn't contain those changes, which would put the file system (document files folder) out of sync with the database, which could cause a lot of problems.

Note that when migrating the database from Oracle to SQL Server the schema on SQL Server will be the default dbo one for all the tables as that is what it should have been created with when running the creation script.

Support cannot answer questions regarding any changes of data and how that will impact things, such as if datetimes are truncated. This is beyond the scope of Support and every effort should be made to transfer the data as fully as possible or based on how it would normally be for PR in that format.