It took us a while, but SqlTran v1.0 is now officially released!
We changed the name from SQL Translator to SqlTran, as it’s shorter, catchy - and sqltran.com was available. We will use that domain in the future for SqlTran exclusively. As this product will certainly grow, and database migration is so complex due to the differences between different engines - we will need extensive online help, community etc. However, we have so much work still ahead, that this will wait a bit.
SqlTran 1.0 migrates MySQL 5.1 to SQL Server 2008. All older versions are supported, too, of course.
What SqlTran provides is a comfortable database translation. Basically, point it to the source database, tell it which is your target - and it will do the magic. All your tables, views, procedures, functions, triggers - and of course data - are written in the target. What paid professional expert would do manually in weeks or even months, SqlTran does in a few seconds. Cool, eh?
Take a look and tell me what you think about it: www.spectralcore.com/sqltran/
We have secretly been working on the complete database translator for quite some time now - over a year. While our existing tool, Full Convert, efficiently migrates tables, data, indexes and foreign keys, it can’t handle procedures, triggers, views, UDTs and other database objects. This turned out to be a burning issue for many of our (potential) customers who need to have their database logic translated, as well as data. As SQL is a verbose language with loose syntax (one thing can be written in many very different ways), analyzing code turned out to be hard. There are not so many tools for that on the market, for obvious reasons.
So, where are we now? We have written lexical and semantic parsers for MySQL, SQL Server and Oracle - with Firebird, PostgreSQL and others to follow. I can tell you, these grammars are huge! Our semantic parser is very fast, it parses hundreds of thousands lines of code in a few seconds, and gives us perfect in-memory object representation of the SQL commands. We have covered most of the statements in each SQL dialect, and consciously skipped some exotic statements that probably not many people use. People are signing up on our beta tester list daily, and I am happy that you will soon be able to test our long-term effort.
How does it work? You will be able to hand over just a SQL script file, and we analyze all the code, show you all objects in a nice tree list, and you can browse both the original and the translated code easily. You can also modify the translated code by hand and we won’t touch that object’s translation (unless you choose to revert to default). You can even refresh the source at any time without losing your manual tweaks. You can also connect to the live source database and we will fetch a definition for each object - the rest is pretty much the same as if you were working with a script.
For output, you can either create a database creation SQL file, or you can connect to your live target database server and have everything moved over seamlessly and test the code logic.
Sign up for notifications or beta testing here: www.spectralcore.com/sqltranslator/
I had a terrible experience with VS2008. Although I use a speedy Quad Core CPU, 4 GB of RAM, fast hard drives and a fast graphic card - it took between 5 and 10 seconds to redraw a form in Visual Studio designer. I wasn’t sure if it’s because of the excellent DevExpress components we use for all our .NET products, but it seemed just a bit too much to expect, even from Microsoft.
So, after being fed up with the sluggish VS interface once too much, I googled to see if there is a solution. Guess what? I found it in just a few minutes and am not cursing VS anymore. Because of this issue, at least. 
In short, if your problem is caused by the same thing that slowed me down, just go to Internet Options (either from Control Panel or from IE’s Tools menu) and uncheck the Check for publisher’s certificate revocation* in the Advanced tab, under Security Node section in the tree list.
Read the whole thread here:
http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/bc778e26-9156-4924-a9ca-a57ef8ff6bcc
It’s been more than half a year since our last release.
It took us half a year to perfect Full Convert 5 since the last release back in January. So, what’s big in v5.0? In one sentence - it’s faster, more reliable, uses less memory - and supports databases of unlimited size! That’s right, unlimited
Here’s a breakdown of all major changes:
• Full Convert 5 handles databases and tables of the unlimited size
• Improved speed of conversion
• Improved user interface responsiveness
• Reduced memory consumption
• Installation reduced to less than 50% of the original size
• Microsoft .NET Framework is no longer required to run Full Convert
• Improved Excel support and added support for Excel 2007 files as a target
• SQL Server Compact Edition database maximum size increased to 4GB
• Improved user interface to avoid confusion of new users (for example, trying to open a database file instead of project file will now automatically start the new conversion wizard with the correct database info filled-in)
• Added a visual indicator of the slower parameterized mode used for BLOB data
• Added a fast SQL Server detection
• Added support for multiple double-quotes in CSV text files
• Added ‘Test Filter’ button in Table Settings. Use it to see how many records your custom source table filter selects.
• Many bugfixes, of course
I just ran a quick test to see how does it perform. I was converting to MySQL on a local machine, so there was no network lag. For one thing, it’s nice to see it transfer 27 thousand records per second (something competing products can only dream about), but for me it’s even more interesting to look at the Task Manager. We are transferring data in full speed from a million records table, and Full Convert uses 50MB of RAM!
Neat!
Tags: database conversion, full convert, mysql, releases
Spectral Core finally has a blog. It is long overdue, but finally it is live.
Expect articles related to our core expertise - databases, of course. I’m planning to write a great deal of pretty general informational posts, but also very specific problem-solving techniques.
As we’re handling 16 database formats with our database converter, and 5 with our data sync product, I have a lot to write about.