RE: [Axapta-Knowledge-Village] SQL License

[Varden Morris]

Hi Marlon
 
I know that it would make perfect sense to pay for the number of clients connecting
to the SQL server in a 2-tier setting although you have connection pooling with 2-tier. I am not sure what happens where license are concern when you are using 3-tier. The fact is that the client does not connect directly to the SQL server when using 3-tier. Only one user connects to the SQL server in a 3-tier setting and that user can create several connections to the server. One of the reasons why 3-tier is considered to be secure when compared to 2-tier is that in a 3-tier setting you can remove all DSN from the client to prevent the client from connecting to the SQL server since the object server does the connection.
 
I am not trying to convince you to go with per seat license because you have a large number of clients and even if you get a reduction in the number of required license by using 3-tier it may still work out cheaper to go with the processor license.
 
Varden Morris
 
J. Wray & Nephew Ltd. - Group I.S.
234 Spanish Town Road
Kingston 11, Jamaica, W.I.
 
Phone:  (876) - 923 - 6141 Ext. 2400, 2412Fax:      (876) - 923 - 5372 
Cell:      (876) - 3833566Email:   [EMAIL PROTECTED]
            [EMAIL PROTECTED]   
James Flavell <[EMAIL PROTECTED]> wrote:


Hi Varden,
 
Are you sure the pooling is in line with MS license terms of per seat?  I tried the pooling appraoch long ago but was told in no uncertain terms that it was the very end client count that I should be covering regardless of any connection pooling etc.  Further more I was told it was on a named end client and not concurrent so basically had to list out every PC that would be used to connect, hence per seat I believe is of no use if you do any kind of web portal where you have no idea of the actual number of named clients you will get.
 
Not sure whether what I learnt quite sometime ago has changed but I think the per seat is for 'small' companies where it can be listed the physical PCs that will/might connect.
Anyone to comment?
 
Thanks
James
 

-----Original Message-----From: Varden Morris [mailto:[EMAIL PROTECTED]Sent: 18 November 2004 04:21To: [EMAIL PROTECTED]Subject: RE: [Axapta-Knowledge-Village] SQL License

Hi Marlon
 
When you are using an object sever with Axapta it reduces the number of client license needed. Since it is 3-tier the client does not connect directly to the SQL server but does so via the object server. The client connects to the object server which then connects to the SQL server. Since the object server uses the same user to login for all users on the SQL server it does not create a new connection for each user. It does connection pooling which means that several users use one connection to the SQL server thus reducing the number of connection license requied. I am not sure about the number SQL uses in the pooling but I did a rough check and found 61 connections to SQL when 81 users login to Axapta. This means a 25% reduction in the number of required connections.
 
Varden Morris
 
J. Wray & Nephew Ltd. - Group I.S.
234 Spanish Town Road
Kingston 11, Jamaica, W.I.
 
Phone:  (876) - 923 - 6141 Ext. 2400, 2412Fax:      (876) - 923 - 5372 
Cell:      (876) - 3833566Email:   [EMAIL PROTECTED]
            [EMAIL PROTECTED]   
James Flavell <[EMAIL PROTECTED]> wrote:
Hi Marlon,I think you will for sure be better off with the per processor ... I thinkwhen you do the calculation its around 50+ users and per seat becomes thesame price as per processor (of course depending on how many processors youhave in your box ....).  Sorry it has been sometime since I did the pricingof seat vs processor but I think it was around the 50 seat mark that asingle processor license became advisableJames-----Original Message-----From: Marlon Quial [mailto:[EMAIL PROTECTED]Sent: 17 November 2004 11:37To: [EMAIL PROTECTED]Subject: [Axapta-Knowledge-Village] SQL LicenseTo All,I just like to reconfirm the total no. of SQL license I need if I have a3-tier (AOS) environment with 200 thin client users.On top of this, around 100 users will
 be  using ESS.Does this mean that I need 300 SQL per seat license?Or is it better to have a per processor license?Any advise.Thanks.Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. Yahoo! Groups Sponsor      ADVERTISEMENT<http://us.ard.yahoo.com/SIG=129ivffh2/M=298184.5584357.6650215.3001176/D=groups/S=1705001380:HM/EXP=1100745319/A=2426685/R=0/SIG=11eslo8dq/*http://www.netflix.com/Default?mqso=60185401> click here      <http://us.adserver.yahoo.com/l?M=298184.5584357.6650215.3001176/D=groups/S=:HM/A=2426685/rand=401025879>        
 _____  Yahoo! Groups Links*      To visit your group on the web, go to:http://groups.yahoo.com/group/Axapta-Knowledge-Village/<http://groups.yahoo.com/group/Axapta-Knowledge-Village/>   *      To unsubscribe from this group, send an email to:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]ribe>   *      Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service<http://docs.yahoo.com/info/terms/> . Sharing the knowledge on Axapta. > ATTACHMENT part 2 application/ms-tnef
 name=winmail.dat


Do you Yahoo!?Meet the all-new My Yahoo! - Try it today! Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. 
		Do you Yahoo!? 
Discover all that’s new in My Yahoo!


Sharing the knowledge on Axapta.








Yahoo! Groups Sponsor


  ADVERTISEMENT 












Yahoo! Groups Links

To visit your group on the web, go to:http://groups.yahoo.com/group/Axapta-Knowledge-Village/ 
To unsubscribe from this group, send an email to:[EMAIL PROTECTED] 
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.