Work with a Visual Studio 2010 Database Project
Can this work if I already have a VS 2010 Database project setup? Meaning can this work and interact with a VS 2010 Database project so that I can continue working on the actual db in SSMS, but the files get saved to the VS2010 Db Project?
AdminStephanie
(Admin, Red Gate)
shared this idea
23 comments
-
AdminDavid Atkinson
(Admin, Red Gate)
commented
We've recently released SQL Connect, which is our source control story in Visual Studio. I'd urge everyone who has voted on this suggestion to give it a go and let us know how you get on. If you feel that you still need database project support, please let us know why! http://www.red-gate.com/products/sql-development/sql-connect
-
Sebastian
commented
Yes this is a MUST!!
-
Stephen Anslow
commented
Thanks, Marty, for taking the time to expand on your comments. Being the only DB-centric developer/accidental DBA and having been bitten by the current VS DB Project required way of working, I was hoping there was a clear this-vs.-that kind of checklist, for want of a better word, that would help bridge the gaps in my experience and enable me to make a more educated decision over either wait for VS-next and embrace it, or ignore its features and attempt to use SQL Connect, a tool, again, one has no experience of. Thanks again.
I hope Red Gate can put together a feature/practice summary/white paper that clearly sets out the comparable features of RG Tools vs. VS-Next w/ SSDT so decision makers have what they need... Doubtless someone at RG must have given considerable thought to come up with SQL Connect and SSC in their current forms, knowing that VS-Next w/ SSDT was rapidly approaching...
-
Marty U.
commented
@Stephen: correction should say " it is NOT a tool that is targeted for existing enterprise environments."
-
Marty U.
commented
@Stephen: we have not looked into or researched the SSDT tools. We have fought through the current iteration of MS DB tools since their first version. We have worked with many individuals from MS, including some of the project managers directly, and the voice/concerns were never heard. We decided to not take our chances with the next version since the original version was released with so many issues and concerns. In all honesty, the current version works and does what it does quite well, but with our experience it is a tool that is targeted for existing enterprise environments. The tool works great if it is a very small database that is created within the tool from the inception. The simplicity and the approach that RG takes to mimic what SQL Server actually does is what is attractive to our teams. RG seems to understand enterprises much more than MS. MS has a tendency to focus on the volume distribution of their products vs value and function. Sorry I couldn't help more with SSDT but for now we are focusing on implementing a tool that doesn't hinder our productivity.
-
Stephen Anslow
commented
@Marty: tapping your 3+ years of knowledge, how would you compare the *upcoming VS release*, including all the SSDT functionality with the SQL Connect/SSC offerings from Red Gate. Which features IYE are incompatible and which are missing from the other? Which are roadblocks to enjoying SSDT? Which hinder RG Project/SSC usage?
I've no interest in the CURRENT version of VS vs. RG, only interested in finally being able to, at the very least, enjoy offline DB modifications with full impact analysis within VS-next.
Thanks in advance for sharing your understanding, provided you have time, naturally. Regular work = top priority.
-
Marty U.
commented
We currently use VS DB Projects on a large dev team in an enterprise environment. We are working towards migrating to SSC and providing a substantial amount of feedback to RG in regards to SQL Connect. For those that are needing RG to work with a DB Proj setup I would like to ask why? If you are currently using the VS DB projects what functionality would you expect the RG tool to provide? The DB projects are already contain very advanced features. Actually the reason we are moving from them is the fact they are too advanced. The projects enforce rules within a solution that are not relative to the real world and the performance overhead is excessive in a large environment. e.g. No cross reference databases without the enormous overhead of partial projects;treating database projects and solutions like an object oriented project. Just curious as it is obvious that a lot of people feel this is needed and and we have been on DB Projects for 3+ years and have a very thorough understanding of that technology.
-
Stephen Anslow
commented
Looking at the SSDT Videos (Juneau) via the connect surveys (https://connect.microsoft.com/BusinessPlatform/Surveys), SQL Connect and SQL Source Control had better get in on" VS2010 as the ONE-STOP-SHOP" that Microsoft is determinedly heading towards making a reality.
I've been a supporter of Red Gate tools for 6+ years and find them indispensable. HOWEVER, SSDT integration into VS2010 is VERY compelling and, as a SQL Source Control user (SVN, not TFS), I absolutely MUST have integration of SSC into VS2010, cohabiting with SSDT in every possible way.
RED GATE NEEDS TO PUBLISH A ROADMAP THAT ASSURES CURRENT AND PROSPECTIVE CUSTOMERS THAT RG TOOLS WILL BE FULLY INTEGRATED INTO VS2010 FOR SQL 2012. At the very least Red Gate needs to publish illustrated technical papers on the features of VS2010 and SSDT and the integration points SUPPORTED and PLANNED, with dates!
Your public needs to hear from you, Red Gate, with FAR more than the scant "Roadmap" bullet points on the main site. (http://www.red-gate.com/our-company/about/news/ ==> Roadmap)
-
AdminDavid Atkinson
(Admin, Red Gate)
commented
@John - we'll definitely notify everyone if/when we do. In the meantime we're keen to get feedback on SQL Connect and whether this would be a useful extension to Visual Studio. I'd encourage all those who have posted to this forum to take a look and provide feedback - the more use engagement, the easier it is for us to justify database project support! http://www.red-gate.com/products/sql-development/sql-connect/
-
John
commented
I would love to have our whole dev team on SQL Source Control, but can't until it supports VS 2010 DB projects. Notify me when it does!
-
AdminDavid Atkinson
(Admin, Red Gate)
commented
@David - Can't you use the schema compare tool in VS to pull changes from your development database to the Database Project? There's no way just yet to sync the files in SQL Source Control with the Database Project files.
-
David Todd
commented
We are using the unit testing capabilities of Visual Studio 2010 Premium. If Red Gate cannot support database projects, is there a way to sync the Source Control folder with the DB project in VS?
-
AdminDavid Atkinson
(Admin, Red Gate)
commented
@David - out of interest, what do you currently use for DB unit testing?
-
David Todd
commented
This is also essential for us as we are also doing DB unit testing. Without this capability we will have to ditch Red Gate and use the compare tools within TFS.
-
Steve Perry
commented
Essential for us since we now have to us VS to unit test most of our database objects.
-
Steve
commented
A must have as far as we are concerned
-
Dan-Exceptional DBA 2008
commented
think this would be a great feature offering.
-
Rod
commented
Important!!
-
Joey Fortuna
commented
To me, this is a no-brainer.Unless you (redgate) are prepared to start building a full-blown competitor to TFS and an rich IDE that can marry DB code and app code, you're creating unnecessary work for engineers that are comfortable with your toolset.
-
John Gagnon
commented
I am currently tasked with getting this to work as well on my own. I am guessing no one else has been able to the marry the two technologies up until this point?
