Hi Venkat, Are you looking to move just the database itself, or are you looking to build a replica of a current environment? If you are looking to build a replica of a current environment, you can follow these steps:
Steps to Replicate Prod to QA – For SDM 12.9 - Using SQL Backup and SQL Restore
PART 1 – GATHER FILES/DATA FROM PROD SYSTEM
1. Do a SQL Backup of the MDB – save as .bak file (usually a normal SQL backup)
2. Make a copy of the “$NX_ROOT$\site\mods” directory – zip it up if possible.
3. Make a copy of the “$NX_ROOT$\site\attachments” directory and zip it up if possible
4. Copy above files to the QA SYSTEM – but don’t put them in place yet, just copy them to a stand-by directory on that machine.
PART 2 – PREPARE THE QA SYSTEM & REPLICATE PROD ENVIRONMENT
If your QA system has been previously used, and has some differences in the mods (customizations) from production, then you should follow these steps first:
1. rename the \site\mods directory to “old_mods”
2. rename the \site\attachments directory to “old_attachments”
3. delete the existing QA MDB
4. run the 12.9 MDB installer to create a vanilla MDB on the DB server
5. run pdm_configure on the QA server and select “Load Default Data” – this will create a vanilla SDM install
Follow these steps to Replicate Prod to QA:
NOTE: You may skip steps 1-3 if you already have a running QA system. In that scenario, start with step 4.
1. Install SQL in MIXED MODE Authentication
2. Run a pdm_configure checking off the box to “load the default data” – against the newly installed SQL database (this will create a default MDB)
3. After pdm_configure is complete – make sure you can log into service desk, and then STOP service desk services.
4. Do the SQL Restore of your PROD mdb onto the newly installed SQL on this QA System
5. Next, either you, or your DBA needs to run the stored procedure to fix the orphaned user(s) (ServiceDesk in this case) on the restored MDB in SQL:
a. SHOULD BE SOMETHING LIKE THIS: sp_change_users_login 'AUTO_FIX','ServiceDesk'
6. Using SQL, update the usp_servers table to set the host names properly for the new environment
7. Run a pdm_configure – here you will get a warning stating that the database has been previously configured by xxxxx-server –you will say YES/OK to continue – this will then change the servername values in the dlgsrv table to be the correct servername for the QA application server.
8. When pdm_configure completes, start Web Screen Painter (also called WSP) and log in
9. Go to Tools > Schema Designer
10. Click on any table on the tree on the left, and put an “X” (or any value) in the description field on the right (we refer to this as a “dummy update” in schema designer)
11. In the schema designer window, go to File > Save
12. Close the Schema Designer window
13. In the main Web Screen Painter window, click File > Save and Publish
14. Click OK on the dialog boxes
15. Exit out of WSP and close all WSP windows and browser windows
16. Run: pdm_halt -w (this stops all SD Services)
17. Run: pdm_publish (this will merge the schema and load the correct schema files)
18. Restore the $NX_ROOT$\site\mods directory (the one you backed up from the prod system earlier)
19. Copy over the $NX_ROOT$\site\attachments (the whole directory that you copied from prod) into the site directory – overwriting the attachments folder that is already there on the QA SYSTEM (if you didn’t rename it earlier)
20. Run another pdm_configure – BUT DO NOT SELECT TO LOAD DEFAULT DATA – MAKE SURE THE CHECK BOX FOR THIS IS NOT CHECKED!!!
21. After configuration is complete – start service desk services if not started, and do a complete test of all Service Desk functionality.
Hope this helps,
Jon I.