- This topic has 3 replies, 1 voice, and was last updated 8 years, 4 months ago by
.
-
Posts
-
-
In my dev machine SQL Express is intalled for biztalk 2006, but performance getting worse, the SQL service used 100% resourse but dropped to normal if Biztalk Host instance is stopped. And no Agent service in SQL express version.
So that i decided to install SQL Server 2005 on the same machine, copy the database from the express to 2005, and make Biztalk 2006 Server point to the new SQL Server. My question is how to achive this, can this be done only by changing Biztalk configuration or have to reinstall the Biztalk 2006?
Thanks for any advice….
-
We tried installing SQL Server 2005 on the same machine and reconfigured Biztalk to point to it, but found out all Applications are lost, then we copied management db from Express to 2005, got an error saying it needs reference to Express SQL Server\RuleEngine Db.
I'm gonna to restore everything back and exports MSI, and rebuilt a biztalk dev machine, to see if i can import the MSI onto the new server.
Is there anyone tried similar thing and succeeded?
-
I’ve never tied to do this. If it’s not a production server, I’d just Unconfigure BizTalk and reconfigure it to use the new SQL. That way all the accounts will be created for you with the correct permissions.
Then you need to reinstall you applications.
You might want to look in the SDK if there is anything on moving to a new SQL. Again, not something I’d even try to do if there was any other way…
-
-
The best way to look at this is as a deployment issue.
If it IS production, then you should assume you are going to deploy to a NEW server and build it according to your new specs. Then Deploy all of your applications. The means you first need to have deployment packages and even scripts to make life easy. Its a good process to go through anyway to be sure future maintenance will work the way you expect.
If, However, this is a Dev environment then you can look at this as an opportunity to do the right thing since it appears as if you're outgrowing the same-server environment. I would suggest SQL Server and BizTalk should be on separate machines, but you can also split them up on something as small as a laptop using Virtual PC, Virtual Server, or everyone's favorite VM Ware (Workstation or Server).
I'm running an "enterprise" with a Domain Controller, SQL Server, BizTalk 2 server Cluster, and Oracle and MOSS servers as needed. You can run what you need when you need it and test different configurations and scenarios without the time and effort to re-build a new box…especially when you don't have room, budget or you happen to be on the road.
BizTron.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.