01. Ensure your new SQL Instance has the correct collation method Latin1_General_CI_AS. 02. Backup DWH and ASC ( Data Warehouses and Analysis Services Cubes ) 03. Ensure the Sage 200 main core software is up and running and able to be accessed and processed. 04. Create a new DWH and ASC with exact same name as old DWH and ASC 05. Restore the backups taken in point 02. over the top of the newly-created temporary DWHs and ASCs. 06. If you are running Latest Status cubes, you need not do this and you can create a new DWH from scratch which will be based on all information to-date of your Sage 200 core database. 07. If your programmer has written your own Cubes in Analysis Services , or if your reports are attached to "As At Cubes" that require the restoring of ASC and DWH, then
you will not be able to rely on the "start again principle" of Latest Status cubes. The 5 "As At Cubes" are the following :- Aged Debt
Aged Credit
Stock Levels
Sales Order Book
Project Budget vs Actuals (Hybrid Cube Actuals data is Latest Status, Budget is As At ) You will need to know if any amended or self-made reports are using any of the 5 "As At Cubes.”
You can check which of your Reports relate to which Cube by opening the Report in Excel and checking the Connections button on the Sage BI Toolbar.
|