You have a Microsoft Azure SQL database. The database is hosted in the West US region and uses the Premium service tier. Users of the database are located in Los Angeles, New York, and Singapore. The

Moving the primary Azure SQL database from West US to East Asia would improve performance for Singapore users but would negatively impact users in Los Angeles and New York due to increased network latency, violating the requirement to maintain performance for other users.

Implementing Azure ExpressRoute provides a private, dedicated connection to Azure, reducing general internet latency, but it does not fundamentally change the geographical distance between the users in Singapore and the database in West US, so it would not be as effective as bringing the data closer to the users.

Configuring a readable geo-replica in the East Asia region would create a secondary, read-only copy of the database geographically closer to the Singapore users. This reduces network latency for their report queries, as they would connect to the local replica, significantly improving their report completion times without impacting the performance of users accessing the primary database in West US. Azure SQL Database's active geo-replication feature allows offloading read workloads to secondary replicas, ensuring performance for all user groups.

Configuring pagination for the report changes how data is presented (e.g., loading fewer rows per page) but does not address the underlying network latency or query execution time against the database, which is the root cause of the long completion times for thousands of rows.