SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Need a way of estimating the number of users accessing SQL


Need a way of estimating the number of users accessing SQL

Author
Message
Rod
Rod
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2876 Visits: 2068
Currently we're using SQL Server 2005. We're looking to upgrade to SQL Server 2012, but the biggest issue is the licensing cost and how to estimate it. As I understand it, you can purchase CALS or license by core. Licensing by cores is, I believe much more expensive than we need, because we don't have that many users. At most I estimate we could have as many as 50 simultaneous users, but likely that will be smaller than that. The machine we're going to be putting this onto (actually, a VM) is a 4 core machine, so licensing cores is way more expensive, than licensing by users/devices, given our scenario.

However, that still gets me back to asking how many users do we have using the system at once? How can I estimate that with our current SQL Server 2005 database?

Kindest Regards,Rod
Connect with me on LinkedIn.
Michael Valentine Jones
Michael Valentine Jones
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 5984 Visits: 11771
SQL server CALs are not for concurrent users.

You need a CAL for each user or client that accesses SQL Server either directly or indirectly via a middle tier application.
Rod
Rod
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2876 Visits: 2068
Michael Valentine Jones (6/5/2013)
SQL server CALs are not for concurrent users.

You need a CAL for each user or client that accesses SQL Server either directly or indirectly via a middle tier application.



Michael, do you mean we have to have a CAL for each and every user that may access it, even if no one is accessing the database at all?

Kindest Regards,Rod
Connect with me on LinkedIn.
Michael Valentine Jones
Michael Valentine Jones
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 5984 Visits: 11771
Rod at work (6/5/2013)
Michael Valentine Jones (6/5/2013)
SQL server CALs are not for concurrent users.

You need a CAL for each user or client that accesses SQL Server either directly or indirectly via a middle tier application.



Michael, do you mean we have to have a CAL for each and every user that may access it, even if no one is accessing the database at all?


You need a CAL for each user who accesses a SQL Server. If someone connects once per week to look at a single report, they need a CAL.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search