How can we improve Microsoft Azure SQL Data Warehouse ?

Alow multiple SQL DataWarehouse instances to access the same data (.mdf files)

This would allow an enterprise to have a Production Data Warehouse with SLAs in place while allowing a data scientist/Business user/Subject matter expert to do analytic and discovery work without impacting SLAs and without moving data (which usually is pretty large).
At the same time it would allow for metered consumption and chargeback towards the subtenants that are conducting analytic discovery work.
The functionality would be similar to what can already be done today with HDInsight and Azure Blob. Data in Azure blob can be independently accessed by multiple HDInsight clusters.

28 votes
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)

We’ll send you updates on this idea

Bogdan shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

3 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • Frederic Forest commented  ·   ·  Flag as inappropriate

    This is currently the main killer feature from competitor Snowflake (that and near-instant scale up/down).

    This feature allows us to have independant compute instances per project, all taping in the common data warehouse underlying data. It makes a WORLD of difference in DWH management

  • tolga commented  ·   ·  Flag as inappropriate

    this could also be used to allow more concurrent users.
    it could be handled in read only (dirty read) mode

  • Mark Webb commented  ·   ·  Flag as inappropriate

    I think this is a very high priority with a primary objective being to eliminate the rampant data replication of multiple data domains. Also fosters a single "source system of reporting/analytics record" and allows for application of data element naming standards (with business intuitiveness) not currently enforced at the ERP level.

Feedback and Knowledge Base