Sql-server – The problem having different vms with the same sql server Licence key

licensesql server

I was hired in a new company 1 year ago. After doing all important stuff, i'm now hunting for problems and etc.

Using a powershell that can give me the licence key using to install the SQL Server, I could find that we have 5 different vms, using the same SQL Server 2012 with the same licence key.

probably the old people here just used the same EXE and the same KEY to install all sql servers in all vms created because they didn't know about it ( just clicking next next next next)

is there a way to fix this and is it possible to edit to elicence key to use a valid one ( a diferent one for each instance on each vm?

Best Answer

That's not a "License Key" it's an "Activation Key", which simply controls the Edition of SQL Server that is running. Its only relationship to licensing is that it may help you determine what licenses need to be assigned to the server.

Licenses are assigned to servers using external bookkeeping, like in a Software Asset Management Solution or an Excel Spreadsheet.

For instance, SQL Server on Docker Containers and the Visual Studio Subscription Downloads all come with the key already embedded in the installer. Both of these can be used for production deployments by simply assigning the appropriate licenses to the servers without changing the key.

Related Solutions

Sql-server – SQL Server: join two tables with “valid-to” dates

DECLARE @t1 TABLE (T1_key int, T1_Data char(1), T1_ValidUntil datetime)
DECLARE @t2 TABLE (T2_key int, T2_Data char(1), T2_ValidUntil datetime)

INSERT @t1 VALUES (1, 'A', '2000-01-01')
INSERT @t1 VALUES (1, 'B', '2000-06-30')
INSERT @t1 VALUES (2, 'C', '2005-05-31')
INSERT @t1 VALUES (3, 'D', '2004-12-31')
INSERT @t1 VALUES (3, 'E', '2007-04-30')
INSERT @t1 VALUES (3, 'F', '2008-01-31')

INSERT @t2 VALUES (1, 'R', '2002-03-31')
INSERT @t2 VALUES (2, 'S', '2001-06-30')
INSERT @t2 VALUES (2, 'T', '2003-02-28')
INSERT @t2 VALUES (2, 'U', '2005-05-31')
INSERT @t2 VALUES (3, 'V', '2006-09-30')
INSERT @t2 VALUES (3, 'W', '2007-06-30')

SELECT
   T1.*, T2x.*
FROM
   @t1 T1
   CROSS APPLY
   (SELECT TOP 1*
   FROM @t2 
   WHERE T1_key = T2_key AND T2_ValidUntil >= T1_ValidUntil
   ORDER BY T2_ValidUntil
   ) T2x
UNION
SELECT
   T1x.*, T2.*
FROM
   @t2 T2
   CROSS APPLY
   (SELECT TOP 1*
   FROM @t1
   WHERE T1_key = T2_key AND T1_ValidUntil >= T2_ValidUntil
   ORDER BY T1_ValidUntil
   ) T1x

Sql-server – What do I need to sync a local site office SQL Server with the Head Office SQL Server

I ran into a similiar problem for an accounting package. Instead of trying to work out a way to move the SQL data around it proved to be much easier (and more cost effective) to provide a way to remotely access the application.

I opted for a TS 2008 box. This includes a large number of international users with terrible bandwidth compared to the states.

EDIT - As syneticon-dj points out there are still potential issues associated with using TS on a satellite link. You would definitely need to look at the latency of your link for a TS solution to work. Some satellite links provide around 300 millisecond latency, others may be over a second.

Best Answer

Related Solutions

Sql-server – SQL Server: join two tables with “valid-to” dates

Sql-server – What do I need to sync a local site office SQL Server with the Head Office SQL Server

Related Question