SQL Server Runtime Embedded Licencing

Question

SQL Server Runtime Embedded Licencing

RTaylor2208

SSChampion

Points: 13298
More actions
October 13, 2010 at 8:53 am

#227930

Hi,
Has anyone here had practicle experience with the microsoft SQL Server Runtime Embedded licencing. The article on microsoft.com is pretty vague: http://support.microsoft.com/kb/917400
I'm not sure whether they mean you can't connect to the Databse Engine via anything other than your application or you are just not licenced to.
For example if we install SQL server and it has a database we created within it, can you connect via a 3rd party tool like business objects to do BI or can you only connect using our bespoke application. Would anything other than adequate permissions stop other people adding databases etc.
Any advice would be appreciated.
MCITP SQL 2005, MCSA SQL 2012

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Shawn Melton SSC-Insane Points: 24685 More actions · Answer 1

I believe this explains what it is pretty well:

Description of the SQL Server Runtime license
The SQL Server Runtime license is a license that lets an independent software vendor (ISV) embed the complete SQL Server code into a solution for use only by the ISV application. The customers of the ISV cannot use this SQL Server product to run other applications or to develop new applications, databases, or tables.

This licensing is for application vendors. If they want to use SQL Server as a backend to their application. The application is the only connection made to the SQL Server instance. It is basically dedicated to that one application.

Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton

RTaylor2208 SSChampion Points: 13298 More actions · Answer 2

Thanks for replying, to be fair though that does not answer my questions at all. If the sql server is going to limit connections to a specific application how is that achieved? Will it only support SQL connections with a fixed login and password or through an application role etc.

I have spoken to ms as we are a gold partner and their own sales people could not give me any more info, maybee they were just the wrong person. That's why I am asking if anyone has had any practicle experience with this.

MCITP SQL 2005, MCSA SQL 2012

Shawn Melton SSC-Insane Points: 24685 More actions · Answer 3

~~scratched~~

Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton

Shawn Melton SSC-Insane Points: 24685 More actions · Answer 4

RTaylor2208 (10/13/2010)
Thanks for replying, to be fair though that does not answer my questions at all.

Fair enough.

If the sql server is going to limit connections to a specific application how is that achieved? Will it only support SQL connections with a fixed login and password or through an application role etc.
I have spoken to ms as we are a gold partner and their own sales people could not give me any more info, maybee they were just the wrong person. That's why I am asking if anyone has had any practicle experience with this.

I believe it is as it states on the KB article, "it is a license". You can compare it with Microsoft Dynamics NAV, that software is licensed using this method. I purchase a license for Microsoft Dynamics NAV (which the 4.0 version was a pain to mess with) for a particular number of users, say 50. That software uses SQL Server as the backend database. The number of users I'm licensed for with NAV is the limit of connections I should have to the SQL Server database. I can tell you though I can go beyond that limit, SQL server is not going to stop me. Just like I'm only "allowed" to have a single NAV database in that instance of SQL Server, but I could still add more I'm just not supposed to.

You might check out this link. I like his last comment: "One downside though was the fact that I noticed that not many people actually know how the Runtime License work. I'm sure they will sort it out, and there will be a comprehensive paper in the near future. Until then, you can contact Microsoft or you can use this information."

Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton

RTaylor2208 SSChampion Points: 13298 More actions · Answer 5

Thanks, that makes more sense that it is you are only licenced to a certain number or from a specif source. But it won't actually stop you if you tried to connect outwith the terms of the licence.

MCITP SQL 2005, MCSA SQL 2012