How can we help you today? How can we help you today?
Dominick Reed
Hiya, It sounds like you need to setup a second project. So instead of editing the current project, swap to a clone of the project where you've previously swapped the datasource to a snapshot. Dom / comments
Hiya, It sounds like you need to setup a second project. So instead of editing the current project, swap to a clone of the project where you've previously swapped the datasource to a snapshot. Dom
0 votes
Hiya, Thes are some of the last things that make it into the help file. We'd been waiting on some icons to arrive and as such, not all screenshots could be taken. [image] Dom / comments
Hiya, Thes are some of the last things that make it into the help file. We'd been waiting on some icons to arrive and as such, not all screenshots could be taken. Dom
0 votes
Hi there. I'll try and take as many of your points as I can. [image] There are a few reasons we went down the route of the grouping bars in the top results grid. When we met with people and when we tested the product, we observed that the first thing most users would do (in version 3 or 4) would be to group via the difference type. Then they'd follow this by getting rid of the identical objects so that they only had the difference types that they were interested in displayed. The functionality of being able to hide all of a difference type, can inadvertently cause other problems, specifically when filtering. We found that new users found it very hard to know whether a filter would exclude the object from synchronization or if it would just hide it from view. We wanted to make projects more useful, such that they would remember a lot more of their settings between sessions. The side effect of this is that if you had excluded a difference type, and subsequently a difference of this type was detected, the user wouldn't know about it. Keeping the grouping bars there, means that you can never inadvertently miss a difference that you weren't expecting. This is highly useful when a lot of our users run through SQL Compare pretty much on autopilot. The grouping bars therefore allow you to get a good overview of your differences without any scrolling - which then informs your decision over what to investigate. So we felt that it was much more important that you'd always be able to know the extent of your differences without the risk that a difference would go unnoticed because of how you had left the project previously. Having said all of that, we'll certainly look to include the ability to not have the grouping bars shown, but this won't make it into the initial release of version 5. Regarding filters, this is a route we've been forced to take because of the huge increase in the number of object types that SQL Server 2005 has introduced. Having these along a toolbar would mean that we'd be forced to show the icon only, and when you have so many, finding the specific one you want becomes a painful tool tip search. It's far quicker to be able to read the object type in a text list and get a clear indication whether it is on or off - even if you've had to open a panel to achieve this. The headers you mention in the difference pane, e.g. extended properties, columns etc. have always been there, but they were very easy to overlook and so their functionality was lost. They are useful though, in much the same way as the main grouping bars in the top pane, so we just made them more visible. We've changed the behaviour of the copy actions button. In all the performance tests that we've conducted, we've been faster. If there are specific instances where you know of a competitor's product outperforming us, we'd be interested in being able to replicate it. Regarding Data Compare: We've worked hard to ensure that the product (like SQL Compare) has a strong and consistent use of symmetry. In Data Compare, the middle three columns are there to help give a spacial feel as to where the data resides. If it's in the middle column, it's in both, but it differs, if it's on the left, then it's in the left hand database only, same goes for the right. This does mean that with the combination of the interactive help, tool tips and icons, we've been able to see user's understand this concept very quickly. It's clearly different from version 4, but it's much easier for new users to get to grips with. Application options have been standardised between Compare and Data Compare. You can clone projects that you have previously set up with specific options, so once you have a set of options you like, clone a project instead of creating a new one and you'll keep all of your options. I hope that in part has explained some of our reasoning and thank you for your comments - you've made a lot of valid points. I'll make sure they get fed back into development. [image] Dom / comments
Hi there. I'll try and take as many of your points as I can. There are a few reasons we went down the route of the grouping bars in the top results grid. When we met with people and when we tested...
0 votes