Comments
Sort by recent activity
Hi Oleg,
We'll see what we can do and hopefully we'll get this into the release build.
:-)
Dom / comments
Hi Oleg,
We'll see what we can do and hopefully we'll get this into the release build.
:-)
Dom
This is something that we did think hard about, but after sitting though a lot of usability sessions and seeing the problems docking panels cause, we opted for the simple approach.
By not having extra docking functionality and resizable column widths, we've been able to ensure that the user is less likely to get in a muddle or spend valuable time continually tweaking what they've adjusted. Sometimes less functionality is better.
Given your monitor resolution, I could see how it might just be viable for you, but our research indicated that wide-screen isn't that widespread yet. We'd be adding functionality that the majority of our users couldn't take advantage of, and would most likely just cause them more problems.
Hope that helps explain why we took this route !
:-)
Dom / comments
This is something that we did think hard about, but after sitting though a lot of usability sessions and seeing the problems docking panels cause, we opted for the simple approach.
By not having e...
Hi Thomas
You're right, the SQL difference pane only docks to the bottom or floats - we actually stripped out a lot of the original docking functionality...
We left in the ability to float the pane so that those with 2 monitors could take advantage of their extra screen. This can be really handy, especially with Data Compare.
Regarding docking to the side, when we tried this, even with a widescreen format resolution, becasue of the predominant horizontal bias of the grids and the filter panel, we didn't feel there was any additional space advantage.
Hope that kind of makes sense !
:-)
Dom / comments
Hi Thomas
You're right, the SQL difference pane only docks to the bottom or floats - we actually stripped out a lot of the original docking functionality...
We left in the ability to float the pane...
It's meant mostly as a way to try and spot something you didn't expect would be happening. For example, you might look down the list and see that it's dropping a user, and maybe you didn't think it should be doing that.
It's probably also worth noting that the text here is likely to change to make it a bit more readable as it's currently pretty hard to scan.
:-)
Dom / comments
It's meant mostly as a way to try and spot something you didn't expect would be happening. For example, you might look down the list and see that it's dropping a user, and maybe you didn't think i...
The action plan is intended to be a way to summarize what actions need to be performed to synchronize the databases. It is in the order in which the actions will be performed, so you can review the steps it'll take.
It's not grouping all actions together, as these may occur at different times to different objects during the synchonization.
:-)
Dom / comments
The action plan is intended to be a way to summarize what actions need to be performed to synchronize the databases. It is in the order in which the actions will be performed, so you can review th...
The top grid displays the results of the comparison at an object level. The bottom grid displays the detailed differences for the selected object.
Multiple selection in the top grid, is to allow you to include or exclude objects from synchronization more easily. For example, if I multi select four tables and then hit the spacebar, the "include" checkbox will be toggled for all 4 of them.
The bottom pane is really just a way to review the differences for one object only.
You can see a similar behaviour in something like Microsoft Outlook. If you click on a single email, another pane will show you the contents of the email. If I select multiple emails, it'll still only show me the contents of one - the last one I clicked. Allowing multiple selection in the email pane is just a means of being able to apply some kind of group action.
Hope that's helped !
:-)
Dom / comments
The top grid displays the results of the comparison at an object level. The bottom grid displays the detailed differences for the selected object.
Multiple selection in the top grid, is to allow y...
We're due to review interactive help tomorrow so I'll make sur your comments are heard.
Not all things made it into the beta unfortunately, and right clicks in every place we'd like them are one such casualty !!
:-)
Dom / comments
We're due to review interactive help tomorrow so I'll make sur your comments are heard.
Not all things made it into the beta unfortunately, and right clicks in every place we'd like them are one su...
:-)
The resource issue doesn't always work like that... what tends to happen is that if you provide the functionality for someone to exhaust their resources, they'll blame the tool. We'd rather not have an application that performs badly when it's put under unreasonable load, as it'll be the only thing that gets reported.
You can of course still do this (by opening multiple instances of the applications), it's just that we prefer not to encourage it by having the design of the UI imply it's good practice.
:-)
Dom / comments
:-)
The resource issue doesn't always work like that... what tends to happen is that if you provide the functionality for someone to exhaust their resources, they'll blame the tool. We'd rather n...
Hi Vanram,
Thanks for the suggestions, I'll see what we can do, although these are unlikely to make it into the initial release.
Your first point is something that we have put into other products that we are working on, but it didn't quite make it into version 5. It's something I really value, so I'll make sure it gets considered for later releases of the bundle tools.
Comparing several databases is still possible if you run several copies of the application. We try not to encourage this because when working with very large databases you can find that a lot of system resources are used. With the new projects, we think that this goes a long way to addressing the needs of working with multiple databases without having to have them all "open" at once.
With regards to integrating them into a single product, we've certainly had this suggested to us before, but we feel that combining the two would make for a much more complicated user interface. We spoke at length to many of our users and we found that a great many who use SQL Compare and Data Compare only use one of them frequently. If we combined them, then the simplicity of the tools could be compromised and they would be paying for functionality that they didn't need.
Hope that helps !
:-)
Dom / comments
Hi Vanram,
Thanks for the suggestions, I'll see what we can do, although these are unlikely to make it into the initial release.
Your first point is something that we have put into other products t...
Hi Vanram,
Just to take each point:
1: Fixed !
2A: Fixed !
2B: We found that users quickly get used to this, and once they have, it helps them move around the UI far quicker.
2C: Whilst we wanted to be very specific for each element you hover over, the downside is that this could cause a slight performance hit. We felt it was more important to have a UI that was highly responsive.
2D: I'll see if this can get fixed for the final release.
2E: This is to allow maximum room to initially explore the results.
Hope that helps !
:-)
Dom / comments
Hi Vanram,
Just to take each point:
1: Fixed !
2A: Fixed !
2B: We found that users quickly get used to this, and once they have, it helps them move around the UI far quicker.
2C: Whilst we wanted...