Re: Which version of D2005 do I need?

From: Lauchlan M (LMackinnon_at_NOSPAMHotmail.com)
Date: 10/22/04 

Date: Fri, 22 Oct 2004 10:08:48 +1000

> 2005 Pro will be fine for ASP.NET and desktop databases including MSDE (or
> it's name in next release MSSQL Express Edition), Interbase, and MySQL.
But
> for database "server" connectivity such as Microsoft SQL Server, DB2,
> Oracle, Interbase, and others you'll need the Enterprise Edition.
>
> the Enterprise Edition also adds:
> - Web Deployment Manager
> - Starteam Standard Edition
> - RAD for ADO.NET
> o DataHub and DataSync for EZ multi-vendor dataset aggregation
> o RemoteServer and RemoteConnection EZ multi-tier ADO.NET remoting
> development
> - Janeva Features for J2EE and Corba connectivity w/Developer Lic.
> - IntraWeb Application Mode for .NET and Win32
> - Royalty Free Midas/Datasnap deployment lic

I haven't checked this out yet, because both Delphi 2005, and RemObjects SDK
and Data Abstract server for .net, have not been released yet, but I think
one would be able to get the RAD database connectivity for Oracle, SQL
Server etc through RemObjects SDK with Data Abstract for .NET, and use the
datasets from that with ASP.NET projects in Delphi 2005. Using RO/DA for
.NET would of course also cover RAD remoting, web services, etc as well and
obviate any need or desire for Datasnap. If he's using ASP.NET then maybe
Intraweb is not of much interest to him, and he may already have a different
source control program he uses.

So he could get the bulk of the benefits you list for Delphi 2005 Enteprise
by using Delphi 2005 plus RemObjects / Data Abstract for .NET. Another
benefit is he could use RO/DA for .net in VS.NET as well, with the latest MS
updates and versions, before Borland have time to implement the new .net
frameworks/versions/features in Delphi for .net.

Also, he might be interested in databases such as NexusDB or FireBird with
ADO.NET providers. He may not need SQL Server or Oracle.

ie, with Delphi 2005, like for Delphi 6 and Delphi 7, Delphi 2005 pro +
third party components is again functionally and pricewise a viable and
interesting alternative to Delphi 2005 Enterprise.

That's not to say he may not prefer Delphi 2005 Enterprise, but he has
definite choices as to where he spends his money, depending on what his
priorities and experiences are.

Lauchlan M

Relevant Pages

  • Re: Which version of D2005 do I need?
    ... > it's name in next release MSSQL Express Edition), Interbase, and MySQL. ... > Oracle, Interbase, and others you'll need the Enterprise Edition. ...
    (borland.public.delphi.non-technical)
  • Re: Licensing rules for Data Guard
    ... am I right that that it is not available as an option for Standard ... and is available only in Enterprise Edition? ... If I read correctly, the log shipping technique, which is well documented on multiple sites, involves shipping archived, rather than active, re-do logs and therefore is certain to be minutes, rather than the max 5 seconds, out-of-phase that we need. ... dependent upon your ability to negotiate with your Oracle sales rep. ...
    (comp.databases.oracle.server)
  • Re: Delphi bugs and "moving" to Visual Studio debate
    ... mention to them that Delphi is named Delphi because it was to ... development environment for Oracle, ... item 3 (database) is the primary factor for decisions. ... > clients don't even know about any bugs etc in IDE's before they decide ...
    (borland.public.delphi.non-technical)
  • Re: Reaction to Q2 Warning
    ... it doesn't have to run on anything but client machines connecting to an Oracle server. ... AFIAK, Sun doesn't sell a database so Delphi is pretty much useless for Sun. IMO, an acquisition by Sun has the highest likelihood of killing Delphi. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi bugs and "moving" to Visual Studio debate
    ... Even the origins of the name Delphi ... " The strategic decision to make database tools and connectivity a central ... Gary kept coming back to the codename "Oracle", ... connectivity to Oracle servers. ...
    (borland.public.delphi.non-technical)