Settings and activity
93 results found
-
112 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Can I paraphrase what I think you're asking for? You have multiple changes, that you want to commit individually with their own comments, but because the commit process is slow on your hosted repository, you want a way of associated different comments on individual items in your commit list and then to commit them all in one go (albeit as individual changesets)?
-
6 votes
An error occurred while saving the comment Can I ask why you would like this capability?
-
10 votes
An error occurred while saving the comment @Anonymous - is there a reason why the existing Filter feature doesn't fit your requirements?
An error occurred while saving the comment Have you tried using the "Edit Filter Rules" option to achieve this? Filter rules get saved with the source controlled database and therefore apply to all developers linked to that repository.
-
6 votes
An error occurred while saving the comment Thanks for the feedback. Which bits in particular did you want to hide? We're trying to not be intrusive. In fact, we've only got one top level menu (SQL Prompt) whereas we used to have two (SQL Refactor).
-
1 vote
An error occurred while saving the comment That doesn't sound right. Please email support@red-gate.com , as they will be able to advise you on how to troubleshoot this issue.
-
12 votes
An error occurred while saving the comment Yes, I agree that this would be the ideal situation. We definitely hope to get there eventually.
An error occurred while saving the comment It's hard to say when we'll be able to do this. It's definitely a very nice idea that marries together two of our tools, so it ticks a big box for us. However, work would need to be done by the SQL Prompt team to expose this feature as a service to the SQL Source Control product, which would need to consume the service and expose this as an option somewhere. This would need an options dialog to be designed. I can't make any commitment as to when this might appear. In the meantime it might be worth highlighting the Find Invalid Objects feature to your developers and strongly advising them to run this as often as they can!
An error occurred while saving the comment If difficulty was the only barrier then we'd have a lot more features in the tools! It comes down to prioritization. There are so many good ideas and limited development resource. We haven't yet implemented a UI for the existing set of options (as you get in SQL Compare, for example) in SQL Source Control yet, so it's likely that this will take precedence over new features. I know it's frustrating, but if it's any consolation it's equally frustrating for us as well!
An error occurred while saving the comment That's a good point. It probably needs client-side support in TFS. I can't see this being on the near-term roadmap for SQL Source Control. One option you have is to use SQL Connect, as this is a Visual Studio plug-in. Another option is to encourage your developers to run 'Find Invalid Objects' in SQL Prompt before committing their changes. I would agree that it would be a great pre-check-in feature to detect these problems automatically.
An error occurred while saving the comment You can use the SQL Compare command line to achieve this. First create a new DB in your CI environment and then: sqlcompare.exe /scripts1:<DatabaseScriptsFolder> /server2:<CIServer> /db2:<RedGateCIDB> /sync . We have some resources linked from www.red-gate.com/ci which may be helpful.
An error occurred while saving the comment Some CI tools have a feature that allows you to check that the build works before the commit is accepted. TeamBuild has 'gated checkins'. TeamCity has pre-tested commits. See http://www.jetbrains.com/teamcity/features/delayed_commit.html . In theory if you have a CI build step that tries to build your database from scratch, it should pick up most cases of invalid objects. Is this something you have tried?
-
4 votes
An error occurred while saving the comment Because of a poor decision we made many moons ago, DML triggers are not regarded as their own object in SQL Compare, and are therefore not affected by the Filter rules. This is something we hope to remedy later this year. The only suggestion I have for you in the meantime is for you to use the Ignore DML Triggers option in SQL Compare, although this will ignore all your DML triggers, which may not be desired behavior.
-
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 @Marc - could you explain what problems you hope to avoid with this functionality?
-
1 vote
An error occurred while saving the comment If you use SQL Compare to apply changes from a particular revision, you can always uncheck any objects you don't want to push to your target database. The drawback is that your target database will be inconsistently versioned, set to a hybrid of multiple revisions. This might make it hard for you to manage changes in the longer term. With data changes, I can't see why you can't selectively take records using SQL Data Compare.
-
1 vote
An error occurred while saving the comment I don't understand what you mean by "all the users right got screwed". In what way?
-
207 votes
An error occurred while saving the comment Would you expect there to be some sort of branch chooser option on the commit screen? (eg a file system folder browser)
-
16 votes
An error occurred while saving the comment @Wesley - I'm not sure I understand how a partial success could occur. If the script fails due to something in the migration script, the whole deployment script will roll back as everything is contained in the high level transaction. Would you be able to describe an example of where this goes wrong?
-
1 vote
An error occurred while saving the comment @David - no it doesn't, but it's something we're considering. I see you've also raised this issue in our separate SQL Connect forum: http://redgate.uservoice.com/forums/140800-sql-connect-for-visual-studio-/suggestions/2486444-does-sql-connect-work-with-a-database-project-db?ref=title
-
10 votes
An error occurred while saving the comment Thanks for the request. I assume you can currently use Tortoise to achieve this? Or doesn't this provide all the information you need?
-
25 votes
An error occurred while saving the comment We will be storing the repository path as an extended property in the database. Once we have this, it should be fairly straightforward for us to at the very least default the fields when the user chooses to link. Would that be enough? We're not sure that auto-linking is the right thing to do as you might end up with staging and production databases linked, which isn't good practice.
-
7 votes
An error occurred while saving the comment @Alex - Can I ask why you need multiple filters?
-
6 votes
We currently don’t have an option to pause polling in the tool, but you can confiugre an XML file. Please contact support@red-gate.com for details. This file would need to be set for each user.
You could also add a “Column Filter” in SQL Profiler’s Trace Properties’ Events Selection where “Application Name” is “Not like” “Red Gate%.” That should filter out the polling in your trace.
I hope this helps!
An error occurred while saving the comment There's more detail on how to do this here: http://www.red-gate.com/MessageBoard/viewtopic.php?t=12837
Ideally this should be a project-level option, but please try this in the meantime. -
2 votes
An error occurred while saving the comment Thanks for the request. Can I ask why you will find this information useful?
-
2 votes
An error occurred while saving the comment @Simon - what's the main reason it is an issue for you? The performance or loss of selections? (for reference, this has been logged internally as SOC-3093)
An error occurred while saving the comment Which source control system are you using, and which version of SQL Source Control do you have? We've added a feature for the SVN support that simply prompts you for a comment if you haven't put one in and the server rejects the commit the first time.
This is definitely something we're considering, especially as these tools are used more and more for build processes such as continuous integration. Out of interest, could you describe briefly how your build process works?