Actually just one more question. How about the SQL Server Editions? From a
database point of view i dont need any enterprise edition features like full
text indexing and so on (for my projects functionality) .

Does BTS impose any restrictions or can I just use SQL Server standard
edition  ?

Thanks
Benjy


"BizTalk Benjamin" wrote:

> Hi,
> A quick couple of questions. Some pointers would be appreciated
>
> (1) The licensing guide talks about the number of internal applications th
at
> can be connected to partner and standard editions. I suppose this applies 
to
> web services also? In my system we are getting data loads from dozens of
> suppliers via a webservice and an FTP service, this data is stored in a
> custom database (via an internal webservice) and there is a third party we
b
> service providing some functionality. In such a scenario, are we looking a
t 2
> 'applications' (ie) the third party and the internal web service? If the
> third party decides to provide more functionality with their web services,
> does this increase the number of 'applications'?
>
> (2) How well does Standard Edition perform as compared to the Enterprise
> Edition (ie) are there any inherent performance constraints (other than th
e
> fact that you are not allowed to scale out) ? Our system will be very data
> heavy, not high volume messaging even when we get a 100 suppliers on board
,
> so i could potentially use the standard edition instead of splashing out o
n
> enterprise edition (as we have a limited budget). The guide also seems to 
be
> very strict on the issue of no failover and clustering allowed for partner
> and standard editions, but is it really feasible to deploy a production
> solution without these features? Any thoughts on this?
>
> TIA
> Benjy

[ Post a follow-up to this message ]