Comments
Sort by recent activity
thanks Jack, that is really helpful [image] / comments
thanks Jack, that is really helpful
I'm thinking about installing VisualSVN server or getting an account on GitHub and learning about that. The two reasons I'm not using TFS with RedGate source control are
1. i was struggling associating the check-ins with a TFS work-item and couldnt get past that commit-hook
2. I believe the folder structure that red gate generates would differ to a visual studio database project.
the second one isnt really an issue, i'm still trying to figure it all out / comments
I'm thinking about installing VisualSVN server or getting an account on GitHub and learning about that. The two reasons I'm not using TFS with RedGate source control are
1. i was struggling assoc...
Thanks for this David. I agree with the sentiments above and that we're essentially using source control in name only. I'm currently using Red Gate sql source control with a working folder which doesn't give me the history but does still benefit me a lot (seeing which objects have changed, reviewing changes etc).
I've only been here a few weeks. I'm definitely going to at least demo Sql Prompt and Sql Source control (when I mentioned it I got a lot of hesitation as they said their method was free, although i do question that).
What dissuaded me from pushing on this was the collective satisfaction amongst the other developers with this process. It may have been a lack of confidence on my part owing to my lack of experience with Visual Studio, one of the reasons why i've thrown the question out to the community to get some input.
In my opinion however, they will never achieve any sort of efficient development pipeline (moving on to CI, automated unit testing etc). It's a difficult one when coming into an established team. / comments
Thanks for this David. I agree with the sentiments above and that we're essentially using source control in name only. I'm currently using Red Gate sql source control with a working folder which ...
i think you could you use the standalone 'sql compare' product for that - on one side choose the database and on the other choose the folder in the source control repository? failing that, the DLM dashboard will detect 'drift' for you...maybe worth having a look at that. / comments
i think you could you use the standalone 'sql compare' product for that - on one side choose the database and on the other choose the folder in the source control repository? failing that, the DLM...
Hi Xanthe - day 1 for me at my new place. pls you could also email me details of the license key so I can toolbelt installed and give a few demos. cheers, ben. / comments
Hi Xanthe - day 1 for me at my new place. pls you could also email me details of the license key so I can toolbelt installed and give a few demos. cheers, ben.
Stable and easily adaptable solutions occur in highly predictable environments. Predictability comes from consistency, a by-product of standardisation and automation. / comments
Stable and easily adaptable solutions occur in highly predictable environments. Predictability comes from consistency, a by-product of standardisation and automation.
this could potentially be a very useful tool for people in my position. we have chronic environment problems that aren't going to be remedied anytime soon. we also have shared development databases (with around 8 devs). Our TFS has temporarily been abandoned because of multiple successful deployments being backed out of production because of unforeseen integration issues that came out of the woodwork at a later date. i'm thinking about using this as the beginning of our devOps journey (one script per object, one folder per feature) with the basic principle of deploying the same artefacts (in this case a folder of scripts) against prod as the ones that were used to deploy to test. we would use it for running multiple scripts against one database as opposed to running against multiple databases at the same time. it would essentially be a very simple script deployment tool but the logging, parsing etc will be very useful. I know that this is far from a modern development pipeline but could be the first step in restoring some control, although we are putting off the inevitable which is to stop dev work and do a complete reset of environments and TFS. I have just noticed it has been added to the toolbelt essentials as well which is a welcome addition. / comments
this could potentially be a very useful tool for people in my position. we have chronic environment problems that aren't going to be remedied anytime soon. we also have shared development databas...
I'm thinking of using Prompt's 'find invalid objects' feature instead of a 'build' on a database project in visual studio - so will keep an eye on this one as well. we've got the ball rolling on purchasing sql prompt licenses for everyone and I think, as a team, we will eventually abandon database projects in VS and go back to SSMS. / comments
I'm thinking of using Prompt's 'find invalid objects' feature instead of a 'build' on a database project in visual studio - so will keep an eye on this one as well. we've got the ball rolling on p...
thanks for highlighting that - I think the hard work on this tool has already been done but the UI needs a bit of a revisit as I would have expected that to be selected by default (and not so hidden away). / comments
thanks for highlighting that - I think the hard work on this tool has already been done but the UI needs a bit of a revisit as I would have expected that to be selected by default (and not so hidde...
this is a good idea. I just had a google for one and got directed here. I've demo'd SQL prompt to people many times and a cheat sheet would be a handy material for them to take away / comments
this is a good idea. I just had a google for one and got directed here. I've demo'd SQL prompt to people many times and a cheat sheet would be a handy material for them to take away