02-02-06 10: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 fin
d
> 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
[ Post a follow-up to this message ]
|