Comments
Sort by recent activity
Michael it was a pleasure speaking with you. As I indicated on the call I believe SQL Connect will be the next huge success for Red-Gate. I was very excited when I stumbled upon it as it is the true replacement for the standard MS DB projects in my opinion. I look forward to providing great feedback and will encourage the same with my colleagues. / comments
Michael it was a pleasure speaking with you. As I indicated on the call I believe SQL Connect will be the next huge success for Red-Gate. I was very excited when I stumbled upon it as it is the tru...
David I will make sure to get these things into the user voice pages.
Could you do one last thing for me and point me to a resource or a quick write up of how SQL Connect and SQL Source Control work together?
I understand SQL Connect is still in beta but if we were to work on a long term plan with our current SQL Source Control 3 rollout, how and where does SQL Connect play into that plan.
I have been doing some testing with SQL Source Control 3 and the SQL Connect plugin and can kinda see where each one fits in but I am curious as the direction that Red Gate is going with SQL Connect.
If there is another method or location where these types of communications should occur please let me know. / comments
David I will make sure to get these things into the user voice pages.
Could you do one last thing for me and point me to a resource or a quick write up of how SQL Connect and SQL Source Control wor...
I guess one other thing but I believe this was already posted by someone on the feedback and that is the ability to synchronize a single object, project, or entire solution. / comments
I guess one other thing but I believe this was already posted by someone on the feedback and that is the ability to synchronize a single object, project, or entire solution.
Thanks David. While I was researching and doing some additional testing of SSC I came across SQL Connect preview. To be honest I think this is the turning point for SQL Source Control in a positive way. Once static data scripts, pre and post deployment scripts are incorporated with sql connect it will be the go to product for TFS users with teams of developers working in sql. / comments
Thanks David. While I was researching and doing some additional testing of SSC I came across SQL Connect preview. To be honest I think this is the turning point for SQL Source Control in a positive...
I think the current process with SQL connect works great in regards to check-ins and check-outs. At this point in time I think two key items would be:
1) Ability to execute static data scripts when synchronizing. Should be optional.
2) Ability to perform an actual merge when conflicts arise.
There may be other things but in regards to our teams and development process this is what we would have expected the VS DB projects to be where we can develop in VS or on our local and quickly and easily move things back and forth. The speed and the fact that it mimics how items are scripted from SSMS is ideal. Where things on a table level such as triggers are part of the table script and not a separate object in the solution somewhere is key as well. / comments
I think the current process with SQL connect works great in regards to check-ins and check-outs. At this point in time I think two key items would be:
1) Ability to execute static data scripts when...
I have encountered this exact same thing. I manually edited the file within source control and checked it in and the difference then quit showing up. Not to say that it may not come back once a change is done to the object within the database. / comments
I have encountered this exact same thing. I manually edited the file within source control and checked it in and the difference then quit showing up. Not to say that it may not come back once a cha...
Correct, my concern is of existing testing data not so much the static data as we already replace thaton each Visual Studio deployment operation.
Take a c# programmer for example debugging and testing their code they may have populated their local DB with testing data. However, they need to get latest on the DB so they are certain they are coding against the most recent schema.
We would not want their test data to removed. / comments
Correct, my concern is of existing testing data not so much the static data as we already replace thaton each Visual Studio deployment operation.
Take a c# programmer for example debugging and test...
This is a must for us to be able to move to SSC from Visual Studio. The most appealing aspect of SSC is the performance compared to VS. However, if we have to replace our data each "get latest" operation then I believe the benefit will be negligible and we will stay with VS. / comments
This is a must for us to be able to move to SSC from Visual Studio. The most appealing aspect of SSC is the performance compared to VS. However, if we have to replace our data each "get latest" ope...
Thanks, many times it is the little things that make a big difference. You all do a great job of being involved with the "users" and I believe that is why your products are so successful. / comments
Thanks, many times it is the little things that make a big difference. You all do a great job of being involved with the "users" and I believe that is why your products are so successful.
We are currently evaluating SQL Source Control for a move from Visual Studio DB projects. I would say this is a very important aspect of deploying the source.
We have several databases with some being very large in number of objects and it is very important to our organization that we are working from the exact code that is to be released.
Additionally, if you don't have a mirror image of the source controlled code do you really have the "latest"? / comments
We are currently evaluating SQL Source Control for a move from Visual Studio DB projects. I would say this is a very important aspect of deploying the source.
We have several databases with some be...