FlySpeed DB Migrate to SQL Server v2.4

Catégorie :

Outils de base de données

Licence :

Partagiciel

Editeur :

Active Database Software

Prix :

75 USD

Taille :

6.9 MB

Mis à jour :

05/03/2009

Evaluation :

(0 Votes)

Plateformes :

Vista Win2000 Windows (Autres) XP

Ce logiciel a déjà été téléchargé 145 fois

FlySpeed DB Migrate to SQL Server enables you to transfer the structure and data (fully or partially) onto another database server, or transfer the data to the structure that already exists. In the latter case, there is an opportunity to run this operation many times to sync data. Because the synchronization is done one way, it's very convenient for recurring "dump" of information, for example, from the web server to the local one. The connection with the source database is done through ADO and ODBC, which is a specialty of FlySpeed DB Migrate and cannot be found in most other products. Support for ADO and ODBC lets admins extract ALL the information about the structure of the source database. Another unique feature is an opportunity to connect to the source MS Access database directly, which speeds up the migration process. In doing this, all images, stored in BLOB-fields as OLE objects, are extracted and put to MS SQL Server correctly. Most competing products fail to do it, and images become unreadable and cannot be recognized at all. Another nice touch in FlySpeed DB Migrate to SQL Server is a possibility to transfer data when there is no connection with the target server. In this case, an SQL script is created to be run later. Migrating a database structure is no easy job. Too often experienced admins decide to move by hand because the tools for automatic migration fail to offer them the required level of control and transparency. With FlySpeed DB Migrate, you gain control you want. The generation of an SQL script that creates the database structure on the target server, is totally controlled by the admin. He can change the structure of the objects using visual tools and make changes by hand. In case errors occur during the execution of the script, the admin can correct an expression that caused an error and continue running the script from where it stopped.