This is hopefully not something you have to do often and even more so for a production environment!<\/p>\n
Firstly if you don’t have any applications installed yet or don’t worry about re-installing everything then rather go ahead and do a fresh install. Secondly, if you can recreate the sql server with exactly the same name – that should be safest option because you don’t need to make any changes to the BizTalk front end servers. Lastly, you can try the ‘restore’ vb scripts that is located in the ‘C:\\Program Files\\Microsoft BizTalk Server 2006\\Schema\\Restore’ directory of the BizTalk server(s).<\/p>\n
To use these scripts you have to perform the following steps (after making proper backups of the ‘whole’ environment)<\/p>\n
1. Stop all host instances plus SSO services.<\/p>\n
2. Edit the sample xml file and replace all the placeholder names ‘SourceServer’ and ‘DestinationServer’ plus uncomment the sections you need and save the file.<\/p>\n
3. Run the 2 scripts ‘UpdateDatabase.vbs’ (once) and ‘UpdateRegistry.vbs’ (on each BizTalk server).<\/p>\n
4. Start SSO service (master first)<\/p>\n
5. Start BizTalk hosts<\/p>\n
6. If it worked go buy yourself a drink… else start praying…<\/p>\n","protected":false},"excerpt":{"rendered":"
This is hopefully not something you have to do often and even more so for a production environment! Firstly if you don’t have any applications installed yet or don’t worry about re-installing everything then rather go ahead and do a …<\/p>\n