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('LicenseType')  it comes back disabled. But we purchased 55 licenses last year that I know I inputted somewhere?

What am I doing wrong?

Thank you!

cas_threeAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sammySeltzerCommented:
Try to locate the license by looking for  "sqlslic.cpl" file in SQL server folder(C:\Program Files\Microsoft SQL Server\80\Tools\Binn), Right Click-> Open with Control Panel. this will show you the licensing type used"

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)."


cas_threeAuthor Commented:
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?
sammySeltzerCommented:
You can try this too, although you may have tried it.

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition'),SERVERPROPERTY ('LicenseType'), SERVERPROPERTY('NumLicenses')

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

cas_threeAuthor Commented:
It keeps saying DISABLED for LicenseType.
Ryan McCauleyEnterprise Analytics ManagerCommented:
Starting with SQL 2005, licensing is no longer tracked by the installer or the local machine - it's all soft, and it's up to you to track it (SQL 2000 was the last version to ask you what kind of license you had purchased), which can prove problematic on corporate networks where you'd like to remotely tally up licenses on each server. Since the installer doesn't ask you your license type, it's not stored anywhere on the machine.

As a result, it's by design that SELECT ServerProperty('LicenseType') always returns "DISABLED" for SQL 2005+, which is what you're seeing. If you entered this license count somewhere, you didn't enter it into the SQL Server installer.

There is a way to manually add the license type and count to the SQL Server's registry so that this command does return some data, but it's something you have to do by hand, and the details are given here:

http://blogs.msdn.com/b/sqlblog/archive/2006/11/10/tracking-license-information-in-sql-2005.aspx

cas_threeAuthor Commented:
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!
Ryan McCauleyEnterprise Analytics ManagerCommented:
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).
cas_threeAuthor Commented:
Thank you!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.