Settings and activity
4 results found
-
215 votes
An error occurred while saving the comment An error occurred while saving the comment 
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.
An error occurred while saving the comment 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.
-
Auto checkout from TFS on modify of sql object. and show the object as checked out in SQL Mgt Studio
76 votesSimilar to TFS checkout suggestion, http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/802123-tfs-exclusive-checkout-svn-lock. I guess the difference here is that it is an option to do the checkout automatically.
An error occurred while saving the comment Marty U.
commented
This is a big deal of us as we are working to migrate to SSC. For a product to be focused on source control integration I would hope this would be at the top of the list for Red Gate to deliver.
Marty U.
supported this idea
·
-
131 votesMarty U.
supported this idea
·
-
25 votes
An error occurred while saving the comment Marty U.
commented
From our perspective our teams work out of specific branches of code based on which release version they are working on at the time. If they need to switch branches they must re-link all of their local databases to the new branch. It would be ideal if (similar to VS DB Solutions) if I could automatically link all databases to the same branch if one changes. The goal is to make sure that you are not making changes in DB 1 on Branch A but making changes to DB 2 on Branch B.
Marty U.
supported this idea
·
@Stephen: correction should say " it is NOT a tool that is targeted for existing enterprise environments."