Licenses Question

[MSR63]

I inherited this network and am trying to confirm licenses are up to par.

I have a database server running SQL 2000 which is legal and good to go. I also notice SQL running on two other servers - one on a server that has Veritas and another on a developer server.

My question is -- and I am unfamiliar with SQL,
I guess SQL instance needs to run on the veritas server for the backup application and perhaps on the developer server for antoehr application -- do these instances need separate individual licenses or because it's not a full install of SQL it is ok?

Thanks

 

[gmmastros]

Run this on all your servers....

[tt][blue]Select ServerProperty('Edition')[/blue]

The return values should fall in to this list:

'Desktop Engine'
'Developer Edition'
'Enterprise Edition'
'Enterprise Evaluation Edition'
'Personal Edition'
'Standard Edition'

If it returns 'Desktop Engine', then you don't need a license for that instance.

-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[MSR63]

Sweet!!

Thank you George and have a great Christmas!!

 

[SQLBill]

Plus, the one for Veritas was probably installed as part of the Veritas install - so it is covered by the Veritas license. At least that is normally the case when a third-party app installs SQL Server.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875

 

[MSR63]

George

I ran sqlcmd -L on my database server and came up with a list of servers that have SQL installed on it however when I attempted to run [tt]Select ServerProperty('Edition')
in the Query Analyzer the command ran ok but the execution came back with an error - Could not find stored procedure 'tt'

Am I running this in the correct location?

 

[gmmastros]

Yeah. Sorry about that. the [ignore][tt][/ignore] is actually TGML code, used for this forum to alter the appearance of text within a post. You should remove that part when running the query.

[tt][blue]Select ServerProperty('Edition')[/blue][/tt]

Without the formatting, it would look like this...

Select ServerProperty('Edition')

I usually change the appearance of code so this it stands out and is more obvious that it is code.



-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[MSR63]

That worked thanks!!

Looks like I have SQL 2000 Standard on my DB server
Plus SQL 2005 Developer Edition which I just loaded (side by side)

DB Server - Standard 2000, Developer 2005
BU Server - Veritas covers license (as SQLBill suggested)
Monitor Server - WhatsUpGold covers
Developer server - SQL Developer 2000

I'd like to install Developer 2005 on that last server - it's not a production server. Would that still be legal then?

Thanks again all!

 

[gmmastros]

I don't think it would be legal to install SQL Server 2005 (Developer Edition) on that last server unless you purchased a license for it. Developer is pretty cheap though ($50 - $100).

You could download and install SQL Express 2005 to install on that machine without having to purchase additional licenses.

-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[mrdenny]

You have to purchase a developer license for each server which you install the Developer Editon on.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[MDXer]

you need to license the Dev editions like everyone has said unless you have an MSDN subscription. MSDN covers the dev editions but again it is dependent upon how your MSDN is licensed or the number of MSDN subscriptions you have.

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck