Convert SQL Azure to dBase

Full Convert is designed for ease of use and reliability to make sure you get your job done as quickly and as simply as possible.

SQL Azure is also known as Azure, Microsoft Azure, SQL Server Azure

Making migration easy for you

Full Convert is a fully self-tuning software. Your migration will work as expected without you needing to adjust anything.

Data types are different in dBase compared to SQL Azure. We automatically adjust them as we copy the tables so you don't have to worry about it. You can adjust the mapping rules if you wish to change the following defaults:

  • bigint numeric(20)
  • binary varbinary(10) (if version is 3)
  • binary varbinary(4) (if version is vfp)
  • bit logical(1)
  • datetime date(8) (if version is 3)
  • datetime2 date(8) (if version is 3)
  • datetime2 datetime(8) (if version is vfp)
  • datetimeoffset date(8) (if version is 3)
  • datetimeoffset datetime(8) (if version is vfp)
  • decimal numeric
  • float double(8)
  • geography text(10)
  • geometry text(10)
  • hierarchyid char(254)
  • image varbinary(10) (if version is 3)
  • image varbinary(4) (if version is vfp)
  • int integer
  • money numeric(19,4)
  • nchar char
  • ntext text(10) (if version is 3)
  • ntext text(4) (if version is vfp)
  • nvarchar char
  • nvarchar(max) text(10) (if version is 3)
  • nvarchar(max) text(4) (if version is vfp)
  • smalldatetime date(8) (if version is 3)
  • smalldatetime datetime(8) (if version is vfp)
  • smallint integer(4)
  • smallmoney numeric(19,4)
  • smallmoney numeric(19,4)
  • time char(5) (if version is 3)
  • time datetime(8) (if version is vfp)
  • timestamp varbinary(10) (if version is 3)
  • timestamp varbinary(4) (if version is vfp)
  • tinyint integer(4)
  • uniqueidentifier char(36)
  • varbinary(max) varbinary(10) (if version is 3)
  • varbinary(max) varbinary(4) (if version is vfp)
  • varchar char
  • varchar(max) text(10) (if version is 3)
  • varchar(max) text(4) (if version is vfp)
  • xml text(10) (if version is 3)
  • xml text(4) (if version is vfp)

Full Convert migration in 4 easy steps

1.
SQL Azure connection

SQL Azure

We will choose SQL Azure from the list of available source database engines, as SQL Azure is just a special version of SQL Server.

To connect to SQL Azure, you will need to use your server URL in the Server field, and the rest is standard (username, password, database name). Just make sure to connect using SQL Server authentication instead of Windows authentication.

2.

dBase

We will choose dBase and FoxPro (DBF) from the list of available database formats. Both dBase and FoxPro use DBF file format for their database table files.

Just type-in the folder containing your dBase database tables, or click the ellipsis button on the right and Full Convert will display Browse for Folder dialog.

dBase connection
3.

Start the conversion

All source tables are selected for conversion by default. In case you only need some tables, simply deselect the ones you don't need - or deselect all, then select just the tables you do need. Click the Copy your database button to get started.

4.

Conversion

Conversion is highly-optimized to run as fast as possible, yet provides top-notch reliability. Huge tables are converted in small chunks at a time, preserving memory and ensuring that your computer stays fast and responsive.

Data copying from source to target
Target database browser

Data is now in the target database

Use our built-in database browser to examine the copied data. Of course, you can also examine the conversion in detail and see in-depth information for each table.

Ready to dive in?
Run Full Convert today.

We offer unconditional 60 day money-back guarantee.
You will be helped directly by people who created this technology.

Similar migrations