|
Home > Archive > BizTalk Server Setup > February 2006 > BTS 2004 slow intall when SQL is antoher machine
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BTS 2004 slow intall when SQL is antoher machine
|
|
| David Hernandez Diez 2006-01-22, 6:05 pm |
| We have a script that install two BTS2004 assemblies with a total of 20
orchestrations, creates ports, binds the ports and then it starts all
the orchestrations.
When using this script in an environment where the BTS2004 and its SQL
is all installed in one machine it takes 5 minutes, but when installing
in another environment where the BTS 2004 is in one machine and the SQL
is in another it takes 2 hours!
Both environments have the same OS (windows server 2003), same pathes
etc ...
I don't think it's a network bottleneck because when calling the
orchestrations and other web services it behaves normally and it works
as fast as the other environment.
Does any one has any clue about what's happening? Or what other things I
can check to find the problem?
--
Thanks in advance,
David Hernández Díez
MCDBA MCSD vs6 & .NET
DCE5 .Net1.1 & DCE2 .NET 2.0
| |
| Yuan Ren[MSFT] 2006-01-23, 7:51 am |
| Hi David,
Thanks for posting!
Based on my understanding, the current problem is that it takes more time
to run the installation script. If I have misunderstood anything, please
let me know.
I have performed the test to deploy the BizTalk assembly to the production
environment which uses the remote database. However, I can not reproduce
the current issue. Since you mentioned the problem is not caused by the
network, I suggest you perform the steps below:
1 Creating a simple assembly and deploying it to find whether the problem
is encounter by the assembly.
2 Change the database to another machine, and perform some test;
3 Using the BizTalk Deployment Wizard to deploy the current project to find
whether it still take more time to do this.
These steps will help me to narrow down the current issue. I appreciate
your understanding!
Regards,
Yuan Ren [MSFT]
Microsoft Online Support
| |
| David Hernandez Diez 2006-02-02, 5:51 pm |
| Hello Yuan,
First of all thanks for your post ...
We have tested the same deployment script in two different environment
and the behavior was the same, both lasted 2 hours ...
The rest of the tests you recommend are still pending. Since we work in
a large enterprise it takes a lot time to test things in those
environments (many people are using those environments so we cannot test
freely :-( ) But they will be done as soon as we can.
In order to make the least amount of tests. Do you consider interesting
to look for something more in particular meanwhile or during the install
(for example activate the sql profiler to see what's going on between
BTS and SQL)?
--
Thanks a lot,
David Hernández Díez
MCDBA MCSD vs6 & .NET
DCE5 .Net1.1 & DCE2 .NET 2.0
Yuan Ren[MSFT] wrote:
> Hi David,
>
> Thanks for posting!
>
> Based on my understanding, the current problem is that it takes more time
> to run the installation script. If I have misunderstood anything, please
> let me know.
>
> I have performed the test to deploy the BizTalk assembly to the production
> environment which uses the remote database. However, I can not reproduce
> the current issue. Since you mentioned the problem is not caused by the
> network, I suggest you perform the steps below:
>
> 1 Creating a simple assembly and deploying it to find whether the problem
> is encounter by the assembly.
> 2 Change the database to another machine, and perform some test;
> 3 Using the BizTalk Deployment Wizard to deploy the current project to find
> whether it still take more time to do this.
>
> These steps will help me to narrow down the current issue. I appreciate
> your understanding!
>
> Regards,
>
> Yuan Ren [MSFT]
> Microsoft Online Support
| |
| Yuan Ren[MSFT] 2006-02-05, 2:47 am |
| Hi David,
Thanks for reply!
The first step in my previous thread is just want to confirm whether the
problem is caused by the project itself or the environment.
Any way, if you have some profiler files which related to the current
issue, please feel you free to send me. The SQL server engineer and I can
deal with it together to find some information. My alias is
v-yren@online.microsoft.com (Remove .online).
I'm looking forward your reply!
Regards,
Yuan Ren [MSFT]
Microsoft Online Support
|
|
|
|
|