How can we improve Azure Database Migration Service?

Update Portal to cope with many databases

The client-side script can currently not cope with many databases (500+) and the browser gets unresponsive due to script processing.

6 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Peter Selch Dahl shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Nikhil Patel [MSFT] commented  ·   ·  Flag as inappropriate

        thanks for the feedback. We are working on this scenario. In meantime have you tried used our powershell cmdlets to migrate your DBs. That would help you get unblocked quickly while we get new updates to UI out.

      • Raj Pochiraju commented  ·   ·  Flag as inappropriate

        hello,
        We are aware of this issue and will address in future releases.
        Meanwhile you can use the script below to limit the number of databases that the DMS databases selection blade populate.

        Please let me know if you have any further questions.
        USE [master]
        GO

        -- create new login
        CREATE LOGIN [DmsTestUser] WITH PASSWORD=N'fakepassword$1', DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[us_english], CHECK_EXPIRATION=OFF, CHECK_POLICY=ON
        GO

        -- deny view access to all databases
        deny view any database to [DmsTestUser]
        go

        -- grant minimum permissions required for access and backup
        grant VIEW SERVER STATE to [DmsTestUser]
        go

        grant CONTROL SERVER to [DmsTestUser]
        go

        -- change dbowner for each database you want the user to see
        ALTER AUTHORIZATION ON DATABASE::AdventureWorks2008 TO [DmsTestUser];
        --ALTER AUTHORIZATION ON DATABASE::AnotherDatabase TO [DmsTestUser];
        go

        ----------------------------------
        -- cleanup: When user is logged in y
        ----------------------------------
        /*
        -- re-assign database ownership to [sa] or previous dbowner
        ALTER AUTHORIZATION ON DATABASE::AdventureWorks2008 TO [sa];
        --ALTER AUTHORIZATION ON DATABASE::AnotherDatabase TO [sa];

        -- if user is logged in, it will block drop login
        drop login DmsTestUser

        -- find user's spid and kill it and try drop login again
        sp_who DmsTestUser
        kill {spid}
        drop login DmsTestUser
        */

      Feedback and Knowledge Base