Solved

Conversion ADO to FireDAC

Posted on 2014-11-28
7
1,490 Views
Last Modified: 2015-01-23
Hi,

With the new Delphi XE7 I would like to investigate if moving from ADO to FireDAC is a wise discission.
I'm using currently a MS SQL Server 2008 R2 SP2 database.

Does anybody have any experience with this merger?
Will this increase performance and stability (which might make it worth the effort)?
Is there some automation possible for existing project with lots of ADO-components?

Thanks!
0
Comment
Question by:Delphiwizard
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
7 Comments
 
LVL 27

Expert Comment

by:Sinisa Vuk
ID: 40472577
Think - a speed is on FireDac side, but memory management not. With some little modification - ado can be a little faster:
http://edn.embarcadero.com/article/27790
Mida conversion tool can convert Ado to FireDac. But in basics - this is all the same. You can build some little test tools for speed comparison and see by yourself what is best for you. If you need memory table - then use FireDac - but for older projects - I would go with ado on.
Here is what other say about migration.
0
 

Author Comment

by:Delphiwizard
ID: 40473219
As I read the article, it looks like FireDAC 's speeds partly comes from the fact that it loads only 50 records at a time (based om OnDemand-setting). I've implemented such mechanism with ADO too, by fetching only f.e. TOP (50) records.

Memory table I already have from DevExpress.  Or does FireDAC support some different type of memory management?
0
 
LVL 37

Assisted Solution

by:Geert Gruwez
Geert Gruwez earned 500 total points
ID: 40522603
fwiw, i had to halt my move to firedac.
It doesn't handle some russian letters. accents get lost

I got this sync setup between an oracle db and active directory and it misses out on some unicode letters
i started a discussion with embarcadero in september and still waiting on their response.
https://forums.codegear.com/message.jspa?messageID=667722#667722

this was XE6. not sure if the problem is fixed in XE7. haven't tried it yet.

i'm guessing they are trying to implement the next generation of unidac of devart or working together

currently no problem with odac of devart
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 

Author Comment

by:Delphiwizard
ID: 40533018
I've asked Embarcadero as well, but they don't seem to have much experience in migration from ADO to FireDAC.
0
 
LVL 37

Assisted Solution

by:Geert Gruwez
Geert Gruwez earned 500 total points
ID: 40533076
they should stop working on new versions like damn race horses and fix the bugs
there is more versions than there is solved bugs at the moment

Delphi 7 was a flagship, and they'll never come anywhere close to such a good version in the next decades.
Since then it's been going downhill with quality.
There were some very nice features included, but what's the use of those if they "work as designed, with lots of and lots of bugs" ?
0
 

Author Comment

by:Delphiwizard
ID: 40535473
Hi Geert I completely agree.
They seem to be fixated on creating new stuff, but spend less time on making the product bug-free. Some bugs are there in version after version.
0
 
LVL 37

Accepted Solution

by:
Geert Gruwez earned 500 total points
ID: 40536356
I tried it and stepped away from it.
> moving from ADO to FireDAC is a wise discission.

no ... it's a dangerous decision
unless you want your clients or colleagues breathing down your neck
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When table data gets too large to manage or queries take too long to execute the solution is often to buy bigger hardware or assign more CPUs and memory resources to the machine to solve the problem. However, the best, cheapest and most effective so…
A Stored Procedure in Microsoft SQL Server is a powerful feature that it can be used to execute the Data Manipulation Language (DML) or Data Definition Language (DDL). Depending on business requirements, a single Stored Procedure can return differe…
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
This is a high-level webinar that covers the history of enterprise open source database use. It addresses both the advantages companies see in using open source database technologies, as well as the fears and reservations they might have. In this…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question