Carrie Miles
asked on
Licensing on SQL Server 2008
I'm trying to check our SQL Server 2008 licenses, since folks are having problems connecting to a database in there.
When I run SELECT SERVERPROPERTY('LicenseTyp
What am I doing wrong?
Thank you!
When I run SELECT SERVERPROPERTY('LicenseTyp
What am I doing wrong?
Thank you!
ASKER
I already read that and I don't have the MSDN copy of SQL Server 2008.
I don't have that file either, the sqlslic.cpl.
Any other suggestions?
I don't have that file either, the sqlslic.cpl.
Any other suggestions?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It keeps saying DISABLED for LicenseType.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So why even by SQL licensing if it's not tracking in the software?
I have a web application that connects to a SQL 2008 DB, some users experience problems, sporadically, which I thought could be due to licensing issues.
But after reading this, licensing cannot be issue since the web app really is not using a "license" to connect to it, is that correct?
Thank you!
I have a web application that connects to a SQL 2008 DB, some users experience problems, sporadically, which I thought could be due to licensing issues.
But after reading this, licensing cannot be issue since the web app really is not using a "license" to connect to it, is that correct?
Thank you!
To your second point, there's no way the license you bought could be the cause of any kind of connection problems, because the installed copy of SQL Server is agnostic about the license type - it will let any number of people connect to the server, regardless of CALs or Processor count, and will utilize the full resources of the host server.
To your first, you buy licenses first because it's honest and expensive software to develop, but also because if you get audited, it's way, way more expensive to not own them! There are stiff fines associated with an audit that finds that you're out of compliance. There's no local enforcement (other than a non-activating license key) because the enforcement effort they'd have to make isn't worth the PITA it would cause paying customers, and they believe their customer base would pay for the software. Installing without paying may be tempting, but it's not worth it in the long run, and I've seen companies get seriously burned by installing the software without licensing it - like, hundreds of thousands of dollars burned, and you end up having to pay for licenses in the end anyway (plus a whole lot more).
To your first, you buy licenses first because it's honest and expensive software to develop, but also because if you get audited, it's way, way more expensive to not own them! There are stiff fines associated with an audit that finds that you're out of compliance. There's no local enforcement (other than a non-activating license key) because the enforcement effort they'd have to make isn't worth the PITA it would cause paying customers, and they believe their customer base would pay for the software. Installing without paying may be tempting, but it's not worth it in the long run, and I've seen companies get seriously burned by installing the software without licensing it - like, hundreds of thousands of dollars burned, and you end up having to pay for licenses in the end anyway (plus a whole lot more).
ASKER
Thank you!
If that is disabled as well, then it usually means you are using an MSDN copy of SQL Server (so, not a production license - MSDN licenses are meant for development and testing)."