Hi,

I just installed BizTalk Standard EDition 2004 on a
Windows 2003 server, with remote SQL Server 2000
databases.
My SQL Server is a server with 4 CPUs.
After the installation, the SQL Server processor control
setting has been changed from 'Use all available
processors' to 'Use 1 processor'.
I know that Standard Edition will accept only 1
processor, but I have JD Edwards connected to the same
SQL Server. For JDE I need to use all available
processors. My BizTalk server is single processor.

Can I change back the setting to 'all processors'?

Thank you,

Doru

[ Post a follow-up to this message ]

That's BizTalk server that will accept only one processor, it has nothing
to do with the SQL Server - which I assume is licensed separately, right?
So, yes, of course your SQL server may be configured to multi-processor
work if it is appropriate version/licensed to do so.

When thinking about BizTalk server, think about transports, pipeline
conversions, and orchestrations running -- these are the ones that will use
a single processor.

Regards,
Eldar

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team
--------------------[vbcol=seagreen] 

[ Post a follow-up to this message ]

Thanks for the answer Eldar!

Doru





>-----Original Message-----
>
>That's BizTalk server that will accept only one
processor, it has nothing
>to do with the SQL Server - which I assume is licensed
separately, right?
>So, yes, of course your SQL server may be configured to
multi-processor
>work if it is appropriate version/licensed to do so.
>
>When thinking about BizTalk server, think about
transports, pipeline
>conversions, and orchestrations running -- these are the
ones that will use
>a single processor.
>
>Regards,
>Eldar
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>EBusiness Server Team
>-------------------- 
V5.50.4910.0300[vbcol=seagreen] 
microsoft.public.biztalk.server:9651[vbcol=seagreen] 
control[vbcol=seagreen] 
same[vbcol=seagreen] 
>
>.
>

[ Post a follow-up to this message ]