November 1, 2012 at 12:28 pm
Hello, everyone....
I am about ready to install a new SQL Server to support a SharePoint installation, and need to acquire a SQL 2008 R2 license. We're just about ready to purchase a 2008 R2 Enterprise license, but I was wondering if anyone out there has any experience changing a license key on an existing SQL Server. Let me explain a little deeper....
My company is pretty much all client-based (meaning clients usually purchase their own licenses, that we then use), but also need to support our own infrastructure. The SQL Servers I manage are all owned by the client, with their own licenses. Now, this new install with be mainly for internal use and it has been explained that my company will own the licenses. Now, to get the project moving, I need to do the install before the license is purchased. I was planning on just using one of the licenses from my client until ours come in.
After trying to figure out the answer on Microsoft's site, I haven't seen anything definitive. It looks as though there is no way to remove a current license key and enter a new one for an active installation. I did see somewhere that it doesn't matter which key is installed with the server, as long as the number of installations matches up with the number of keys purchased. If this is true, then I really have nothing to worry about, so long as we get the new keys purchased.
So, I guess the question is, do I need to worry about entering the new keys (reinstall?), or am I good as long as we have a sufficient number of keys on hand?
thanks in advance....
Pete
November 1, 2012 at 2:58 pm
pveilleux (11/1/2012)
Hello, everyone....I am about ready to install a new SQL Server to support a SharePoint installation, and need to acquire a SQL 2008 R2 license. We're just about ready to purchase a 2008 R2 Enterprise license, but I was wondering if anyone out there has any experience changing a license key on an existing SQL Server. Let me explain a little deeper....
My company is pretty much all client-based (meaning clients usually purchase their own licenses, that we then use), but also need to support our own infrastructure. The SQL Servers I manage are all owned by the client, with their own licenses. Now, this new install with be mainly for internal use and it has been explained that my company will own the licenses. Now, to get the project moving, I need to do the install before the license is purchased. I was planning on just using one of the licenses from my client until ours come in.
After trying to figure out the answer on Microsoft's site, I haven't seen anything definitive. It looks as though there is no way to remove a current license key and enter a new one for an active installation. I did see somewhere that it doesn't matter which key is installed with the server, as long as the number of installations matches up with the number of keys purchased. If this is true, then I really have nothing to worry about, so long as we get the new keys purchased.
So, I guess the question is, do I need to worry about entering the new keys (reinstall?), or am I good as long as we have a sufficient number of keys on hand?
thanks in advance....
Pete
personally i would not use one of your clients keys unless you can get them to approve it in writing. you could use this to light a fire under purchasing or have some one give you the keys to the treasure chest and take the action to buy sql server your self and not rely on a different department if that is how your company uses things.
For performance Issues see how we like them posted here: How to Post Performance Problems - Gail Shaw[/url]
Need to Split some strings? Jeff Moden's DelimitedSplit8K[/url]
Jeff Moden's Cross tab and Pivots Part 1[/url]
Jeff Moden's Cross tab and Pivots Part 2[/url]
November 1, 2012 at 4:01 pm
I agree with Jeremy. I found a link that I'm sure you already checked http://social.msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/ea662c9c-660f-45d4-b272-9a896a5213e0. In that link someone mentions running an upgrade to just change the product key. Good luck!
November 1, 2012 at 4:11 pm
you could also go with an evaluation copy. that would give you 180 days to license the server. however if you go that route i would not go into production with out getting the license. would hate to hit the 180 day mark and every one goes "what happened to our server." it would let you get a jump start on the server build though.
thought of that after a discussion i had with a coworker.
here is the link for enterprise eval http://www.microsoft.com/en-us/download/details.aspx?id=1279
For performance Issues see how we like them posted here: How to Post Performance Problems - Gail Shaw[/url]
Need to Split some strings? Jeff Moden's DelimitedSplit8K[/url]
Jeff Moden's Cross tab and Pivots Part 1[/url]
Jeff Moden's Cross tab and Pivots Part 2[/url]
November 1, 2012 at 8:21 pm
capnhector (11/1/2012)
you could also go with an evaluation copy. that would give you 180 days to license the server. however if you go that route i would not go into production with out getting the license. would hate to hit the 180 day mark and every one goes "what happened to our server." it would let you get a jump start on the server build though.thought of that after a discussion i had with a coworker.
here is the link for enterprise eval http://www.microsoft.com/en-us/download/details.aspx?id=1279
Of course, it's a quick way to nearly guarantee funding. "Look! Production dies in another 10 days unless you cough up some bucks because it's an evaluation copy!" 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply