You probably have read the following pages a couple of times by now: https://azure.microsoft.com/en-us/documentation/articles/sql-database-cloud-migrate/. If you haven't, read them. Those pages contain a lot of background information. To summarize, Microsoft basically provides 3 solutions:
Using Deploy Database to Windows Azure SQL
The first solution lets you use the Deploy Database to Windows Azure SQL functionality of SQL Server Management Studio.
For a 3 table, 1000 records, sample database this method is easy. You click next, next, next and you are there. Our guess is that your database is not this tiny. It is probably at least tens or hundreds of gigabytes, has a couple of hundred tables with millions of records. If you move this database via the Deploy Database to Windows Azure SQL function, it is going to be down for days. You have actually no idea how long it is going to be down. While it is moving, you have no real progress other than the text In progress until the complete process finishes or fails after 3 days.
Another solution that Microsoft provides (since august 2016) is not that easy either. Setting up transactional replication for a one-time move is a pretty complex job.
The bulk copy (BCP) way
A third solution that Microsoft provides describes a good, controllable, process:
- You make a compatible schema of your database. You can use various tools for this.
- You publish this schema to Azure.
- You use the BCP command-line utility to bulk copy all your tables.