Yes. Please contact us at firstname.lastname@example.org with the current licensee name and the new licensee-name, as well as any other administrative changes – contact email(s), invoice/payment details, etc.
If the new entity is physically distinct and will have a different set of users / PCs, you should uninstall Mercury from those machines.
Yes. In most cases Mercury doesn’t care about your server(s), but this can be an issue if you are using Mercury with a production platform that segregates servers and data access – for example, Microsoft Dynamics 365 Business Central in the cloud.
If you physically change your D365 BC server, please contact us at email@example.com so that we can update your BC server’s URL and web-service address in our records.
In general, you don’t need multiple licenses; your subscription allows you to use Mercury with all production data platforms in your enterprise.
However, there are circumstances that might require multiple licenses/subscription; these typically involve unusual security requirements or otherwise segregated data access.
For example, if you are using Mercury with Microsoft Dynamics 365 Business Central in the cloud, that architecture limits us to a single server (as many companies as you wish, but one server). If you add a new server (with its own D365 BC URL), you must obtain additional subscription licenses, even if the same user will be accessing both servers.
If you’re unsure about your circumstances, please contact us at firstname.lastname@example.org.
A server installation creates a Mercury database for you in the secure cloud. It houses report definitions and other meta-data; no production data is kept here. You only need to do this once.
As part of this database setup you’ll be asked for the company which will be associated with your Mercury license.
When your database has been successfully created, you’ll be provided with an encrypted “connection string” that will be used when you install the Mercury client on your PC(s).
The encrypted database connection-string that tells Mercury how to communicate with your reports database. This connection-string is generated as part of your database setup (see the “Server Installation Requirements” question.
If you wish to run Crystal reports from within Mercury, then you also need
(*) Transferring stored procedures: this will be straightforward for your IT people. They're the ones who created the stored procedures in the first place, and they'll know how to move them to a different server. Mercury knows the stored procedure used by each report. You can use Tools > Admin Tools > Reports to see details about each report, or you can run a Mercury report!