How can we improve Microsoft Azure SQL Data Warehouse ?

[In preview] Database project from Visual Studio to support Azure SQL Data Warehouse

Database project from Visual Studio is useful to manage DDLs, schema compare between the project and database, etc. Please create a project template dedicated for DW or support DW development from Database Project.

895 votes
Sign in
Sign in with: Microsoft
Signed in as (Sign out)

We’ll send you updates on this idea

Aaron Kim shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Microsoft
Signed in as (Sign out)
  • Vicky0210 commented  ·   ·  Flag as inappropriate

    Is there a blog where we can share feedback/issues for preview? I know there is an email address provided to report issues/feedback but it would be good to share this with others and learn from each other.

  • Anonymous commented  ·   ·  Flag as inappropriate

    It is absolutely vital that Azure SQL Data Warehouse projects are supported from Visual Studio. The entire CD/CI approach must be considered and the Azure SQL Data Warehouse belongs to that as well.

  • Philip Clubb commented  ·   ·  Flag as inappropriate

    Looking forward to trying out the Preview @SQL DW Team! Signed up via the form and ready to give this a shot on our current ADW instances.

  • hgummako commented  ·   ·  Flag as inappropriate

    Good to know it started.. Can you please share timeline when this will be expected to complete ?

  • Harry Leboeuf commented  ·   ·  Flag as inappropriate

    2,5 years to get a start for something so crucial, lets hope we see COMPLETED a bit faster. But, ... great news.

  • Pawel Potasinski commented  ·   ·  Flag as inappropriate

    Definitely a huge blocker for customers to think seriously about developing for SQLDW in real life. If not delivered in a timely fashion will leave SQLDW as a permanent "showcase service" instead of a valuable MPP PaaS solution for the biggest deployments.

  • Philip Clubb commented  ·   ·  Flag as inappropriate

    Almost a critical missing feature IMO, especially when trying to utilize only 1 flavor (and instance) of source control across database applications. As we're attempting to migrate our entire infrastructure to Azure, this is another gap in full end-to-end data management and hinder our ability to scale at the pace we are expecting.

  • Sambathraj commented  ·   ·  Flag as inappropriate

    I want to echo others feedback. This is a roadblock for SQL data warehouse adoption and needs to be addressed quickly. Currently, it is very painful for deployments and managing the Source code without the SSDT database project for DW.

  • Ted Dallas commented  ·   ·  Flag as inappropriate

    Our organization's DW database objects in TFS are in chaos. Basically it is a roll your own deployment strategy plus version control folder trees whose standards vary from team to team to team. Please get this working soon. We are about to ditch TFS entirely and go to Jenkins. We are not a small customer (inside the fortune 20).

  • Aditya commented  ·   ·  Flag as inappropriate

    We have implemented APS DW. Source control is a half baked solution for us as the SMP box supports this where as the APS side doesn't. We are forced to manually store all the files and incremental deployment is a painful exercise. I see that APS/ SQL DW support for source control is in the roadmap. Any timelines as this is urgently needed by our team.

  • ponchohg commented  ·   ·  Flag as inappropriate

    Hello - This is a must for our team to use Azure DW solutions. Managing the code/deployments is truly a pain without this.

  • Anonymous commented  ·   ·  Flag as inappropriate

    This is a big blocker to use Azure SQL DW at the moment. Unable to use Version control, deployments and CI/CD without this.

  • Anonymous commented  ·   ·  Flag as inappropriate

    @Anonymous, the link makes it clear that VS projects for Azure SQL Data Warehouse are not currently supported.

    @Microsoft, it beggars belief that this has been missing for SO long. Was it not obvious from the beginning that this was a vital component for anyone wanting to use Azure SQL in an enterprise (or even small workgroup) environment?

Feedback and Knowledge Base