While instalilng SQL Server reporting services, I was prompted to choose between two licensing types. I chose "Per Seat" and gave 10 as the number.
Can someone explain to me what this means, and what the number 10 signifies here?
Printable View
While instalilng SQL Server reporting services, I was prompted to choose between two licensing types. I chose "Per Seat" and gave 10 as the number.
Can someone explain to me what this means, and what the number 10 signifies here?
Per Seat means pretty much what it sounds like. As opposed to a Site License, a Per Set License requires that a client access license be purchased for each client connecting to the product, in this case SQL Server. If you have purchased a 10 "per-seat" license, that means you can only have 10 people connected to your SQL Server at anyone given time.Quote:
Originally Posted by mendhak
What happens when the 11th client attempts to connect? Is the connection simply refused?
I believe that depends on how SQL Server is setup. I think you can configure it to only accept a specific number on consequtive connections. Doing so prevents any chance of violating the licensing agreement that you purchased, but, unless so configured, I don't believe it will deny requests beyond what has been legally purchased.Quote:
Originally Posted by mendhak
If you ever got audited, and you had more connections than you had licenses for, you will definately have an issue, so if you only have 10, make sure SQL Server will not accept more than that (or, go buy more licenses or check into moving from a per seat to a site license)
Mucho thanks.
It would be a good idea to verify what I said with your DBA, but I'm pretty sure that is how it works.
I believe the term "per seat" was chosen by MS to make perfectly clear that it's for a machine - a physical location - not a person - as CLIENT ACCESS LICENSE implies.Quote:
Originally Posted by mendhak
So if you have a PC that's used for emergencies it's going to count against the "per seat" arrangement as well.
Usually Site Licensing is more commonly used, isn't it?
Isn't there a processor licensing scheme too - per processor?
I've not heard of a processor license, but it wouldn't surprise me.Quote:
Originally Posted by RobDog888
Site Licensing is more commonly used in large corporations where it is difficult to determine exactly how many people will be accessing a particular piece of software. It is also more expensive, but if you are in a company with a large employee population, it is actually more cost beneficial. Per Seat Licensing is more common in smaller companies where it is reasonably easy to determine how many people will need access to a particular piece of software. Licensing for MS Exchange is often purchased on a per seat basis simply because per seat is cheaper, and you pretty much know how many mailboxes you are going to need. Often, even large corporations will go per seat with Exchange.
Conversely, most companies, regardless of their size, will go the site license route with the MS Office suite of products simply because you are getting three or four different products for the cost of one license spread out over your entire company.
MS SQL server does have a per-processor licence. It's goal is to have the cost be related to the size of the hardware - dual processor, etc.
This link might explain a bit of it...
http://msdn.microsoft.com/library/de...setup_5alh.asp
Thanks for the link and info szlamany. So, site, per seat and processor are the three licensing types. Are there any other types that anyones knows about (pure curiosity question on my part)?Quote:
Originally Posted by szlamany
I think that SITE and PROCESSOR licence are the same thing - so that there are only two options...
One of my school district customers has 1000+ teacher PC's that can connect to the SQL DB - per seat licencing would have been a bit too much in that case!
Ohhhhh...actually when you think about it, that makes sense. I'd just never heard it referred to as a "processor" license before.Quote:
Originally Posted by szlamany
Yes, I think its M$' way to keep companies from saving mony on licensing by not allowing them to consolidate servers with one more
powerful multi-processor server with a single site license vs. several smaller servers with several site licenses.
Great link, szlamananannzslamany. :afrog: