Activity overview
Latest activity by peter.peart
SQL Source Control v1.1 Available - View History within SSMS
SQL Source Control 1.1.0.19 28 Sept 2010
===================================================v1.1 Release Highlights:
* Database and object level history in the Object Explorer right-click menu
* Su...
Support for Team Foundation Server Work Items
Since the release of SQL Source Control We have been busy implementing support for Team Foundation Server Work Items. If you do not currently use Work Items a brief description from Microsoft is:
"...
Hi Peter,
I think this is a known bug, SC-2921. If however you can send me some snapshots of the schema so I can see it going on here, I can then update the bug with your schema information too in the hope that it can be fixed in a later edition of the tool. The more information we have the better.
If you want to zip up the schema files and send them to support(at)redgate.com FAO me that would be great.
Pete / comments
Hi Peter,
I think this is a known bug, SC-2921. If however you can send me some snapshots of the schema so I can see it going on here, I can then update the bug with your schema information too in ...
Hi,
Many thanks for your comments. I have added this as a feature request in our systems under reference SC-4568 , and if we get similar feedback from other users we’ll consider it in a future release of the tool.
Pete / comments
Hi,
Many thanks for your comments. I have added this as a feature request in our systems under reference SC-4568 , and if we get similar feedback from other users we’ll consider it in a future re...
Hi Peter,
Does the view also make use of the stored procedure? We have seen this sort of behaviour happen in objects with circular dependencies.
Pete / comments
Hi Peter,
Does the view also make use of the stored procedure? We have seen this sort of behaviour happen in objects with circular dependencies.
Pete
Hi Dan,
I couldn't possibly confirm if it is going to make it into a future release, however I am sure that it will be reviewed.
Pete / comments
Hi Dan,
I couldn't possibly confirm if it is going to make it into a future release, however I am sure that it will be reviewed.
Pete
Hi Dan,
There are a number of options in SQL Compare revolving around ignoring triggers, however they are only able to do this en masse and not for individual triggers on tables.
This is however currently in our systems under feature request SC-2447.
Pete / comments
Hi Dan,
There are a number of options in SQL Compare revolving around ignoring triggers, however they are only able to do this en masse and not for individual triggers on tables.
This is however cu...
Hi,
Many thanks for your reply.
So, just to confirm, if the databases are changed at all you would expect to see the objects selected for the comparison reset to none? I can add a feature request for this, however for thoroughness, what would you expect to happen if you changed the synch direction when comparing the same databases? Would you expect the objects selected to be reset again or not?
Many thanks!
Pete / comments
Hi,
Many thanks for your reply.
So, just to confirm, if the databases are changed at all you would expect to see the objects selected for the comparison reset to none? I can add a feature request f...
Hi Scott,
Is there any chance you can create the same project again in SQL Data Compare 8 and let me know if you experience the same issue?
I have seen cases before where there is an issue with SQL Data Compare 8 reading the old project file, and the way to rectify this has been to recreate the project from scratch in version 8.
Is this something that you are able to do?
Pete / comments
Hi Scott,
Is there any chance you can create the same project again in SQL Data Compare 8 and let me know if you experience the same issue?
I have seen cases before where there is an issue with SQL...
Hi there,
As far as I am aware, SQL Compare remembers the last used selections. For example, if on the last time the tool was used all objects were selected for comparison, all objects will be selected again. If only objects that exist on database A were selected, it would keep the same setting for the next database A.
If however all were unchecked, it would proceed with all objects unchecked.
Would your preferred behaviour be to deselect all objects upon beginning a comparison unless the project has been explicitly saved?
Pete / comments
Hi there,
As far as I am aware, SQL Compare remembers the last used selections. For example, if on the last time the tool was used all objects were selected for comparison, all objects will be sele...