July 17, 2009 at 7:18 am
From what I have read and how I am reading it each developer working / connecting to SQL Server needs a dev license.
After that it gets a BIT fuzzy.
Say I have 8 devs and 2 full time QA / testers.
So 8 dev licenses for sure and 2 more for the full time testers = 10 dev licenses.
With those licenses I can install 800 instances of SQL Server, provided it is only used by those 10 people and ONLY in a non-production capacity.
Now here is where it gets fuzzy to me:
1. Those two full time testing / QA people, they still need those licenses because they work directly with the code. They can debug it, review it, etc...
Is that right?
2. What about UAT, we have say 100 employees who we will call up and say "OK, it is time for your departments to review the new application changes and sign off on them before we push to production".
Those 100 employees do NOT need dev licenes because they do NOT do testing 100% of the time. We just tap them for UAT sign offs every now and again.
Is that correct or do I not understand the dev license model?
July 17, 2009 at 8:03 am
Maxer (7/17/2009)
From what I have read and how I am reading it each developer working / connecting to SQL Server needs a dev license.After that it gets a BIT fuzzy.
Say I have 8 devs and 2 full time QA / testers.
So 8 dev licenses for sure and 2 more for the full time testers = 10 dev licenses.
With those licenses I can install 800 instances of SQL Server, provided it is only used by those 10 people and ONLY in a non-production capacity.
Now here is where it gets fuzzy to me:
1. Those two full time testing / QA people, they still need those licenses because they work directly with the code. They can debug it, review it, etc...
Is that right?
2. What about UAT, we have say 100 employees who we will call up and say "OK, it is time for your departments to review the new application changes and sign off on them before we push to production".
Those 100 employees do NOT need dev licenes because they do NOT do testing 100% of the time. We just tap them for UAT sign offs every now and again.
Is that correct or do I not understand the dev license model?
My understanding is that anyone who actually creates/modifies/deletes SQL Server objects such as tables, stored procedures, views, etc needs a Developers License. This means, as long as the employees involved in the UAT only use the application in a test environment, and do not modify the database objects (this does not include data stored in the database), then they do not need a Developers License.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply