locked
SQL Migration to Cloud RRS feed

  • Question

  • Hi Team,

    We are planning to migrate all our on Premises SQL 2008 Db to Azure.

    Right now we are doing POC, from sql server 2008 to Sql Server 2008.

    After migration how to validate all Table,Stored procedures, jobs, function and so on that nothing is missed. Is there any T-SQL scripts to validate all these things. With out running DBCC commands.

    As per my knowledge i prepared check list. (This is just standalone server no HA/DR)

    1. Check corruption issues by executing DBCC commands
    2. Missing Indexes (Run the Missing Index T-SQL)
    4. Validating Table Count and Row Count in each and every database by using T-SQL
    5. Fixing orphaned users.
    6. Validate Linked server access.
    7. Validate Databasemail Configuration.
    8. Validate all Maintenenace Plans
    9. Validate all SQL jobs functionality. (How to validate?)



    • Edited by VijayKSQL Wednesday, June 21, 2017 7:32 PM add
    Wednesday, June 21, 2017 7:09 PM

Answers

  • They should be vetted on premises. You should have identical behavior on Azure.

    You will need to test with small data sets to ensure you get the same results.

    • Marked as answer by VijayKSQL Wednesday, June 21, 2017 11:55 PM
    Wednesday, June 21, 2017 8:36 PM

All replies

  • You can use the schema compare features of SQL Data tools for this.
    Wednesday, June 21, 2017 7:32 PM
  • Thank you Hilary.

    Apart from above 9 steps+Schema Compare what are additional points i need to add?

    Wednesday, June 21, 2017 7:49 PM
  • Other than point 3 being missing that looks good and there being 8 points.

    You will not find any missing indexes on Azure until you run a workload for a while. If you are talking about running the missing indexes dmv on your on premises server and then evaluating the index recommendations and applying them on Azure, that might work.

    Wednesday, June 21, 2017 7:54 PM
  • Thank you Very much John.

    And how to validate SQL Server jobs funcationalty before putting into production?

    Wednesday, June 21, 2017 8:23 PM
  • They should be vetted on premises. You should have identical behavior on Azure.

    You will need to test with small data sets to ensure you get the same results.

    • Marked as answer by VijayKSQL Wednesday, June 21, 2017 11:55 PM
    Wednesday, June 21, 2017 8:36 PM