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.
We started working on populating many databases in the select databases blade. We will publish the number of databases we support as soon as we finish few benchmark tests.
If you have been thinking that the only possible way to enjoy your iOS devices is by jailbreaking it, then you are totally wrong. Here, we introduce to you, iOSEmus app using which you can get many apps that are not available on the Apple app store. Because of its great security policies, iOS users have only a limited number of apps compared to others. Also, many of them are paid apps. But not all of us are able to afford them.
Nikhil Patel [MSFT] commented
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
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.
-- create new login
CREATE LOGIN [DmsTestUser] WITH PASSWORD=N'fakepassword$1', DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[us_english], CHECK_EXPIRATION=OFF, CHECK_POLICY=ON
-- deny view access to all databases
deny view any database to [DmsTestUser]
-- grant minimum permissions required for access and backup
grant VIEW SERVER STATE to [DmsTestUser]
grant CONTROL SERVER to [DmsTestUser]
-- 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];
-- 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
drop login DmsTestUser