Re: SQL Server Royalty

From: Richard Waymire [MSFT] (rwaymi_at_online.microsoft.com)
Date: 07/30/04 

Date: Fri, 30 Jul 2004 10:35:19 -0700

Something sounds VERY fishy. They have to pay for the software they use, as
would the customer, but this "royalty premium"... 

-- 
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Farhan Choudhry" <anonymous@discussions.microsoft.com> wrote in message 
news:714f01c4762a$b71c0f70$a601280a@phx.gbl...
>I am really confused, this sounds like unethical business
> practice. iCode Everest, AvantiSystems, AccPac,
> GlobalShop, the list is long, resellers of these elegant
> softwares claim 'they have to pay royalties to Microsoft
> to work on its database. I never heard of this, I am
> getting this reason since last 6 months in our search for
> consolidated ERP/CRM system. I would appreciate if anyone
> has information on this. This practice is very wide
> spread, end-users like us always face it.
>
> If I buy their ERP/CRM Systems and choose SQL Server as
> database, their resellers would charge me 5-10,000
> Canadian Dollars 'Premium'. IBM DB2 Universal is free,
> Pervasive SQL is cheap. I would have to transfer all the
> in house applications using SQL Server to other databases
> or run two different servers running two database
> platforms.
>
>>-----Original Message-----
>>What ERP vendor said that?
>>
>>-- 
>>Richard Waymire, MCSE, MCDBA
>>
>>This posting is provided "AS IS" with no warranties, and
> confers no rights.
>>"Farhan Choudhry" <anonymous@discussions.microsoft.com>
> wrote in message
>>news:6b9701c475a4$adf9c490$a401280a@phx.gbl...
>>>I don't know where to ask this question, I am hoping
>>> someone will clarify this for me. We are evaluating
>>> several ERP systems, but when it comes to choosing the
>>> database. All the software vendors say that they have to
>>> pay approx. 10% Royalty to Microsoft to develop their
>>> applications on SQL Server. All these vendors charge the
>>> customers this 'premium' if customers want to use their
>>> existing SQL Server or buy new one. Is that true, a
> myth?
>>> If its true, isn't Microsoft concerned about losing
>>> customers? I will stop using SQL Server because the ERP
>>> vendors are going to charge a premium of 5000 to 10,000
>>> dollars on it.
>>
>>
>>.
>>

Relevant Pages

  • Re: Assume SQL Server Rights for apps, any cons?
    ... Since your customer is the sysadmin on his SQL Server box, ... >administrates the underlying SQL Server 2000 database by himself. ... >wants that my software assumes the user rights automatically from the SQL ... >My application offers a GUI to manage customers. ...
    (microsoft.public.dotnet.framework)
  • Re: Access table to sql server table.
    ... m> database in sql server. ... m> I want to copy only tables of access dataase to sql server's m> database. ... daSource = new SqlDataAdapter("SELECT * FROM Customers", ... DataSet dsDelta = dsSource.GetChanges; if // Update the destination with the delta DataSet. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Protect and invirible Database from each other
    ... > My problem is that, after customers connect to the SQL Server, they can ... Although database names are visible, I would not expect users to be able to ... SQL Server MVP ... > I'd ask many SQL Experts but they said that if I used SQL Enterprise ...
    (microsoft.public.sqlserver.security)
  • huge tempdb database
    ... We sell a product that uses SQL Server as a backend. ... A small number of our customers using the earlier version of the product ... Even if we stop and restart SQL Server, the database will remain this size ...
    (microsoft.public.sqlserver.server)
  • Re: SharePoint Services
    ... I'm under the impression that the data tables can be uploaded to a SharePoint location, and that read / edit permissions could be enabled for different users??? ... It was common for customers to have accounts in more than one store / town ... ... However if you do not have share point services setup, nor do you have the expertise and training and resource personnel to run and set up those servers + SharePoint, **if** you users NOW have some type of connection to you network, then then I think the easiest and least amount of effort would be to simply put the backend database on SQL server and and link your front ends to that back end user. ... So, if these people are outside of your corporate network now, then expertise and ability to set up secure connections to allow them to come into your corporate network and pull data from sql server is VERY seriuos issue. ...
    (comp.databases.ms-access)