[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.
Download the Visual Studio 2019 preview here: https://docs.microsoft.com/azure/sql-data-warehouse/sql-data-warehouse-install-visual-studio
SSDT is now generally available!
Please view and share below:
Thank you everyone who helped provide feedback!
Please make sure you include schema compare and data compare. Data compare is helpful when migrating from SQL Server to SQL DW.
Geoff Coles commented
I've posted a comment on RedGate's site to develop SQL compare compatibility for APS / SQL Datawarehouse - do vote for the feature on this link https://redgate.uservoice.com/forums/141379-sql-compare/suggestions/18689506-add-sql-compare-support-for-sql-server-analytic-pl
Nick Haslam commented
Would be great to get an update on this, as we are looking to roll out Azure DW, and manual version control of the schema is not ideal.
Chris Thompson commented
err, so this has now been REMOVED from the roadmap, or just pushed back?
Subrata Dey commented
We are also waiting for this feature to enable. Please let us know , if there is any update?
Martin Cholewka commented
We too have recently run into this issue when undertaking our new Data Warehouse build on APS. This issue is compounded by the fact that Database Projects work on the SMP part of the APS architecture but not on MPP, making it a confusing decision whether to drop Visual Studio for deployments all together. As a result we are having to invest a significant amount of time in developing our own deployment tool. A solution to this issue in the near term would be much appreciated!
Simon W. commented
Please Include APS as well cause I'm waiting for this for more than 3 years now for this feature
Is the preview started yet? Can we join?
Colin Craig commented
We're also very disappointed with PDW. It almost seems like Microsoft are retiring this product as Azure seems to get all the love.
No PDW database project means manual version control, manual script preparation, no continuous integration.
No SSMS means everything is has to be scripted apart from a few basic functions.
APS costs a huge amount to install and the Asia Pacific support has been incredibly hit and miss (more miss). Due to the massive restrictions of PDW, we would have been far better off to create a farm of SQL 2016 servers which we can maintain ourselves using a full product suite and have access to replication, compression, linked servers, TSQL not DSQL etc.
DO NOT BUY PDW! You'll regret it.
Dave Mulanaphy commented
This is a major disappointment. Not being able to align our development process to the standard SSDT Projects feature is a huge gap. SQL DW is a much tougher choice to consider migrating our datamarts to without the existing toolsets (SSSMS, SSDT Projects) working. A huge selling point for moving to APS/SQL DW from our Oracle databases is the consistent dev/build/deploy. I agree with another of the comments that the manual maintenance of code and the inability to do a schema compare from another project or database to the project is drastically needed. This really needs to get into your next DEV cycle
Arthur Nicholson commented
Disappointing that this is being postponed. I find it difficult to recommend ADW to our larger customers without a decent, supported ALM process which we would be able to provide with VS project support. This is a big one for us (and obviously big for a lot of people with it being one of the top voted requests). Keeping my fingers crossed it will reappear in the roadmap very soon
So, it's gone from planning and ETA by end of year, to maybe support at some time in the future and moved back to under review?
Tough going for Azure early adopters it would seem. We chose SQL DW because of the promise of this feature for future enhancements. Starting to seem like that was a mistake - not a very good feeling.
Ben Martens commented
In regular SQL Azure databases, we use the Schema Compare functionality in the database projects to make sure that our git repository matches what is deployed to the database. This lets us do easy code reviews of changes and make sure that we're always in sync. Because we lack that feature with ADW, we get ourselves into more messes where changes are accidentally overwritten or bugs are introduced because git doesn't match what is deployed. It takes a lot more discipline and as we all know, when a process relies on discipline, it's bound to fail from time to time.
I would love to have this support!
Nagendra Ghimire commented
We'd love to have this support.
Geoff Coles commented
I'm also wondering if there are any updates. We really need compatibility with database projects in visual studio. Is there a release date available for this feature?
Any updates on this? It's nearly the end of the year :)
Peter Gadsby commented
I would love to be able to automate deployment from TFS (cloud version) is there any timeline as to when this will be implemented?
Ralph Kemperdick commented
Supporting PDW as well should be considered as well to make the targeting of the code a straight forward experience.