2

As far as I know the key points to migrate an existing database to SQL Azure are:

  1. Tables has to contain a clustered index. This is mandatory.
  2. Schema and data migration should be done through data sync, bulk copy, or the SQL Azure migration wizard, but not with the restore option in SSMS.
  3. The .NET code should handle the transient conditions related with SQL Azure.
  4. The creation of logins is in the master database.
  5. Some TSQL features may be not supported.

And I think that's all, am I right? Am I missing any other consideration before starting a migration?

Kind regards.

3 Answers 3

2

Update 2015-08-06

Additional considerations:

  • Basic tier allows 2 GB
  • Standard tier allows 250 GB
  • Premium tier allow 500 GB

The following features are NOT supported:

Sign up to request clarification or add additional context in comments.

Comments

2

I'd add in bandwidth considerations (for initial population and on-going bandwidth). This has cost and performance considerations.

Another potential consideration is any long running processes or large transactions that could be subject to SQL Azure's rather cryptic throttling techniques.

Comments

2

Another key area to point out are SQL Jobs. Since SQL Agent is not running, SQL Jobs are not supported.

One way to migrate these jobs are to refactor so that a worker role can kick off these tasks. The content of the job might be moved into a stored procedure to reduce re-architecture. The worker role could then be designed to wake up and run at the appropriate time and kick off the stored procedure.

1 Comment

This article describes how Azure Automation can be used as an alternative solution for running SQL Jobs: azure.microsoft.com/blog/2014/06/26/…

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.