September 4, 2013 at 7:27 am
Hi,
I've been evaluating SQL Server 2012 for a while now and have started to use it in production. I am concerned that my evaluation install media (MSDN) has escaped into the production environment, but don't know how to check for sure. Is there a property or something to indicate which license key was used to install the instance so I can check where they've all come from?
Thanks
September 4, 2013 at 7:50 am
I'm not sure there's an easy way. I saw someone say if a productID wasn't entered, it's MSDN, but I think that's changed.
Ultimately, I'm not sure it matters. The licensing is decoupled from the installation. If you have enough licenses for what you are running, you should be fine.
September 4, 2013 at 7:53 am
I think you're right. The more I read into this area the more it seems that the actual installation media/licence doesn't matter so long as the safe has enough legit licenses in it.
September 5, 2013 at 7:19 am
An idea, not verified. Check the SQL Server logs. When an instance is starting it logs a lot of information. If it's a time bombed evaluation version perhaps even that is logged.
September 5, 2013 at 8:09 am
MSDN instances aren't time limited. Eval is, and that is reported with logs, @@versions, etc.
I'm not sure MSDN is anything other than linked to a specific product id.
September 5, 2013 at 8:26 am
I've been looking at this for a few days now and I can't find anything to indicate that the MSDN media is in anyway identifiable post install. I believe that the earlier suggestion that "you can't tell" and "so long as you have the licenses it doesn't matter" is probably the correct answer.
September 6, 2013 at 9:58 am
mike.dinnis (9/4/2013)
I think you're right. The more I read into this area the more it seems that the actual installation media/licence doesn't matter so long as the safe has enough legit licenses in it.
The install media won't matter except for Full/OEM differences. The versions on MSDN are full copies exactly the same as you buy in a shop - the licence key will determine whether you can use it for production.
You should be able to check the key applied to the installation against your (and probably your colleagues) keys on your MSDN subscription.
September 8, 2013 at 8:28 pm
The way to think of licensing, especially if you've been through a few audits, is that licensing is paper based. Licensing is not handled by the SQL Dev team, it's a separate department in Microsoft. The upshot being, there is no reliable way of telling what type of licence covers an install, it comes down to reconciling what licences you have with your install base. Microsoft or your licence reseller can help you by providing a list of what licences you have (assuming you are covered by an EA), you can match that up with what you have installed.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply