User profile for PhilScrace

Thanks very much for notifying us of this problem. We have reproduced your problem and will provide you with a link to a build which contains the fix. We really appreciate you helping us to improve the Oracle product. Regards Phil Scrace Test Engineer Oracle Deployement Suite / comments

Thanks very much for notifying us of this problem. We have reproduced your problem and will provide you with a link to a build which contains the fix. We really appreciate you helping us to improve...

0 votes

Having played around with this a little more it appears that this is not a bug in the sense that there is a problem with the tool; if one removes the '/reportselectedobjects' switch the report will be populated with ALL changes. To populate the scripts file one must use the '/deploy' switch. If our documentation is unclear or misleading we will definitely change it: http://documentation.red-gate.com/displ ... +interface Please do let me know. / comments

Having played around with this a little more it appears that this is not a bug in the sense that there is a problem with the tool; if one removes the '/reportselectedobjects' switch the report will...

0 votes

Hi there, We're really sorry to hear about this issue. I've not seen this before. Could you send the following details please? 1. The SSMS version and SQL Server version you are using 2. The Source control software you are connected to e.g. tfs, svn etc 3. Elaborate on the changes that you want to undo; which SQL Server objects are you editing? if you cannot say explicitly what the changes are please give us as much indication as you can. We sometimes encounter an issue with the Commit tab not updating correctly which we are currently working on (internal ref: SOC_59) but a hard refresh using the refresh button on the Commit tab normally resolves this as does a restart of SSMS. Thanks for taking the time to notify us of the issue; we'll investigate the issue when we receive more information from you. Phil Scrace Test Engineer SQL Source Control / comments

Hi there, We're really sorry to hear about this issue. I've not seen this before. Could you send the following details please? 1. The SSMS version and SQL Server version you are using 2. The Source...

0 votes

Hello again Surm, The current released version of SQL Source Control does not support Red Blobs unfortunately. We do however have two ways to overcome objects being in conflict from two different users. The latest version has: http://documentation.red-gate.com/displ ... /Conflicts The conflicts toolbar loads whenever a user finds themselves in conflicts situation, this toolbar also now features a 'Merge' button which will load 'Beyond Compare 3' or 'Kdiff' diff tools if either are installed to give you more precise conflict resolution. I'll speak to the Product Managers for the product about your requirement for Red blobs, in the meantime you can vote for this feature here: https://redgate.uservoice.com/forums/39 ... ce-control Thanks again for your interest in the product. Please do contact us again if you need further help with your evaluation. Regards Phil Scrace Test Engineer SQL Source Control / comments

Hello again Surm, The current released version of SQL Source Control does not support Red Blobs unfortunately. We do however have two ways to overcome objects being in conflict from two different u...

0 votes

Hi Phil, Sorry for not replying sooner. Following the release of SQL Lock Beta the SQL Source Control team have been looking at integrating SQL Lock into the SQL Source Control product. I suspect that this will be released around mid-late Q2. Would you be like to speak with the team about this feature or perhaps be involved in an Early Access Program? Regards Phil SQL Lock Product Team / comments

Hi Phil, Sorry for not replying sooner. Following the release of SQL Lock Beta the SQL Source Control team have been looking at integrating SQL Lock into the SQL Source Control product. I suspect t...

0 votes

Thanks a lot for the question Surm! [image] The answer really depends on which Source Control model you have adopted. Sql Source Control supports a. Dedicated model b. Shared model. In a. each user is connected to the source control repository with their own local version of the database and its objects . In b. each user is making changes to the same database. In the dedicated model connected to Tfs the problem you describe would typically be overcome by using TFS object locking which is partly supported in SQL Source Control. Basically the user has to separately log in to Team Explorer and lock the objects through the ui of this Microsoft tool, SQL Source Control will then respect these locks. Once the changes have been made by the user they release the locks through Team Explorer and commit as normal. Currently you cannot lock objects through the SQL Source Control Ui. If you are using the Shared Model then we are proposing that users lock the objects in SQL Server. The SQL Source Control team are currently designing this 'Safeguarding' feature which will allow you to do this through the tool. We have UI designs and some of the 'machinery' which will allow you do this and are currently exploring the direction of this feature. Which option would suit you best? Incidently SQL Source Control basically 'checks-out' the files in exactly the same way for each model. A local copy of the SQL objects are persisted to the users disk and put under the control of SQL Source Control which is using the TFS API under the hood. More details can be found here: http://documentation.red-gate.com/displ ... +overview# Please do come back with any further questions about this or anything else to do with our products. Thanks again for your interest, Surm. Phil Test Engineer, SQL Source Control / comments

Thanks a lot for the question Surm! The answer really depends on which Source Control model you have adopted. Sql Source Control supports a. Dedicated model b. Shared model. In a. each user is con...

0 votes

Hi Surm, We've made some progress this week in that we now have a standalone fully functioning prototype which we will initially be giving away free. It's called 'SQL Lock'. We've opted not to meddle with users security in order to lock objects, for obvious reasons. Was this a concern of yours? Did you have a particular method of locking objects in mind? Regards Phil / comments

Hi Surm, We've made some progress this week in that we now have a standalone fully functioning prototype which we will initially be giving away free. It's called 'SQL Lock'. We've opted not to medd...

0 votes

How can we help you today?

PhilScrace

Comments