June 25, 2014 at 5:51 pm
I am unclear about whether we have to purchase 1 CAL for every named user (named meaning a person who will log in to a website developed in .NET with SQL Server backend)? That would be > 1000 CALs. The ONLY thing these .NET named users would do is update their contact info and view reports stored in directories on the windows server (security controlled via .NET)?
We are a small shop so the per processor price ( 4 processors on the externally facing server) would be prohibitive I think. We have to go with standard not enterprise because of cost.
I have searched for the answer but there's a lot of confusion about it out there. Is it true that SQL Server 2014 only offers per processor as opposed to SQL server 2012 which allows CALs or per processor? That's why we want to go with Sql Server 2012 if that's so.
Thanks in advance for your insights.
June 26, 2014 at 2:38 pm
pharmkittie (6/25/2014)
I am unclear about whether we have to purchase 1 CAL for every named user (named meaning a person who will log in to a website developed in .NET with SQL Server backend)? That would be > 1000 CALs. The ONLY thing these .NET named users would do is update their contact info and view reports stored in directories on the windows server (security controlled via .NET)?We are a small shop so the per processor price ( 4 processors on the externally facing server) would be prohibitive I think. We have to go with standard not enterprise because of cost.
I have searched for the answer but there's a lot of confusion about it out there. Is it true that SQL Server 2014 only offers per processor as opposed to SQL server 2012 which allows CALs or per processor? That's why we want to go with Sql Server 2012 if that's so.
Thanks in advance for your insights.
Read the following document, starting on page 17 of the PDF file:
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
June 27, 2014 at 8:14 am
Thanks Steve. I appreciate the help. I called Microsoft before I got your reply. The person I spoke to said that we could buy SQL Server 2014, downgrade to 2012 if we wanted to. I think we may go with 2014 after all. This is a new installation for this small company. As I have an external server that will have hundreds, possibly eventually thousands of named users via the web he advised a per core license. For the internal server that will have 10-15 users he suggested the CALs model.
June 27, 2014 at 8:29 am
pharmkittie (6/27/2014)
Thanks Steve. I appreciate the help. I called Microsoft before I got your reply. The person I spoke to said that we could buy SQL Server 2104, downgrade to 2012 if we wanted to. I think we may go with 2014 after all. This is a new installation for this small company. As I have an external server that will have hundreds, possibly eventually thousands of named users via the web he advised a per core license. For the internal server that will have 10-15 he suggested the CALs model.
That sounds exactly like what I got out of that document. In prior versions to 2012, the licensing wasn't quite as clear cut, and led to lots of confusion, and I knew that licensing had changed with 2012, and had heard from a number of folks that it was a lot easier to figure out. That's why I grabbed the link the moment I found the right page in that document.
Thanks for the update.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply