Features new in v5.0
Full Convert now handles databases of UNLIMITED SIZE. Piece of cake.
Our new conversion engine excels in many things. You might find just this one indispensable.
Say you have a 200GB database, with some of the tables 5 or more GB in size. Loading all that into memory is a no-no.
So we made it possible to query the database for just a small portion of the data we need to process at a time, then repeatiing that while we progress through your source data - and we do it blazingly fast.
The algorithm in early stage was present in Full Convert 4, but it placed the burden on the database server which started to choke after we went further from the beginning of the table.
Our new conversion engine is fast and light. You won't even know
we are doing anything special. You won't even need to turn any special option on to handle huge data - just sit and enjoy watching all these database records fly...
Completely rewritten conversion engine
We tossed a part of the Full Convert out. Hugely popular .NET engine is good for many things, but it's a bit slow for what we are doing here, and it adds a lot of baggage.
By writing natively whole application in Win32 API
calls, we got this:
1) Installer size is half of v4 size (was around 20MB, not counting the download of .NET files when needed)
2) No more need to have Microsoft .NET framework installed
3) Faster conversion
4) Less memory used
5) Snappier user interface
6) Less chance of something going wrong - which means more satisfied users
Many smaller-scale features
Support for Excel 2007
You can now choose whether you wish Excel 97 or Excel 2007 format for each project separately.
Extra hand to newbie users
We found out that many users attempt to load their database file into Full Convert by using Open Project button. Now, this is technically something nobody should do, but why not help? So, when you attempt to load your DBF file as our project, we will nicely say - Hey, that's not really a project, but let's assume you want to do something useful with that file - and then we open a New Conversion wizard and fill-in everything so you can convert that.
Extra speed and nicety to CSV export
Our text target engine was pretty straightforward - open a source table, run it through our conversion engine and then write that to the file. That turned our slightly lacking when huge tables were used - as loading table basically twice in RAM caused plenty of OutOfMemory surprises. So we took advantage of our improved conversion engine, while also avoiding extra RAM consumption on write. In short, your as large as you wish table is now streamed to disk at full speed while we keep it from consuming precious memory.
By the way, if you are converting from CSV file and have nested double quotes in it, that's properly parsed now. In case you were wondering about that.
Local SQL Server instances detection
Although we made a nice tip (right on a proper spot in connection dialog) saying 'Please use .\SQLEXPRESS for server field when you have SQL Server Express installed', surprisingly significant number of users kept ignoring that and sending us connection error bug reports. So we now just pre-fill the corect value depending on the SQL Server instance you have installed.
Auto-creation of MySQL databases
To keep round-trips from MySQL management tools to Full Convert and vice-versa to minimum - if you try to connect to non-existing target MySQL database, we will ask in a polite way - and create it for you right away.
Testing Table Setting Filter
When writing your custom condition to filter the source table records in our powerful Table Settings dialog, click the Test Filter button. It will tell you the number of records satisfying your criteria. Just a small sign of affection from our side.
See complete version history
See all features
