Information
- Products: Sparkrock 2016
- Summary: Rebuilding Sparkrock 2016 QA environment with PROD data
Details
This process is used when copying company data is not feasible or fails. Rebuilding a Sparkrock 2016 QA environment with Production data will ensure you can test changes in an safe environment with fresh data.
Resolution
- Start gathering some information from the existing QA environment. This will be needed later. Connect to NAV-QA and take a screenshot of EWA Setup page. Take notes of the data under "Intranet WEB address", "SMTP Sender Name", and "EWA Email link shortcuts". Example below
- Create a SQL Server backup of NAV Prod environment. SQL Server NAV Database is usually called NAV_PROD
- Stop the NAV services for NAV_QA
- Rename NAV_QA database to NAV_QA_OLD (or simply delete this database)
- Restore the NAV_PROD backup take in step #2 as NAV_QA in SQL server.
- Ensure the SQL credentials connect to the new NAV_QA database.
- Start the NAV_QA service.
- Restore the EWA setup configuration fields gathered in step #1: "Intranet WEB address", "SMTP Sender Name", and "EWA Email link shortcuts" . If for some reason this information is lost, Sparkrock Support can assist filling these
- Finalize this process renaming the main company in QA as PROD_COPY_MMM_YYYY (where MMM and YYYY are month and year). This can be done under the Companies page.
Impact / Risks
This process is risky as the NAV_PROD has production data. Please just follow it if you are familiar administrating NAV and databases.
Workaround
Not Applicable
Related Information
In newer releases of Sparkrock 2016 (CU39), this process can be done at the application layer, just exporting a company from Prod into QA. Follow this link for that process Refreshing a Test Environment with a Company from Production
Update History
The following are the dates and actions pertinent to the history of this issue.
Date | Details | Link |
Dec 31, 2022 | The first version of this Knowledge Base article was created. |
|
Attachment
Not Applicable
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article