Comments
Sort by recent activity
So to clarify for people following the thread (and Brian can you confirm this is correct?):
The detection process is supposed to check:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\Shell\InstallDir
The place to change the registry setting:
HKEY_CURRENT_USER\Software\Red Gate\SQL Compare 4\ViewerType
1 - means SQL Management Studio
0 - means Query Analyzer
Yes the ability to change on the fly in version 5 beta is nice and does work well. / comments
So to clarify for people following the thread (and Brian can you confirm this is correct?):
The detection process is supposed to check:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90...
Additionally, I just installed SQL 5 Beta on a system with the same setup. Again it tried to launch Query Analyzer - not Management Studio and failed. At least in version 5 Beta, it produced an error, rather than killing the entire synch process.
I also tried installing it on the same system we have been discussing. It too did not detect that SQL 2005 is installed. The registry of the viewer type there (for version 5) is also set to 0.
This emphasizes to me that the detection process is flawed or has a bug. / comments
Additionally, I just installed SQL 5 Beta on a system with the same setup. Again it tried to launch Query Analyzer - not Management Studio and failed. At least in version 5 Beta, it produced an e...
Thank you for the confirmation.
I think the detection method needs to be reviewed.
As I mentioned this is a brand new system that I just installed - on a brand new hard drive that never had anything installed on it before. After windows was installed, SQL Server 2005 was installed first (at least the client tools - not the full server)
Then other software was installed.
Then, one of the last installs were the Red Gate products.
I checked the registry setting just now - it is not blank. It is set to:
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE
As for changing the registry manually, the information provided in the post by T. Kato, is not a complete path to a registry entry.
If a change needs to be made in the registry then the full path should be provided. I know how to find it, but others experienceing this problem may not - especially if they are standard users, not used to making registry changes.
So, as the forums are one of the major forms of support for the Red Gate products, for the benefit of others who run across this thread, I think a Red Gate representative should confirm the complete path to the registry entry as well as the entry and value to set to work around this bug.
I also repsectfully suggest that the detection method should be reviewed. / comments
Thank you for the confirmation.
I think the detection method needs to be reviewed.
As I mentioned this is a brand new system that I just installed - on a brand new hard drive that never had anythin...
It is not strange.
That you think so makes me think you are not very familiar with computers.
I am not going to change any registry settings unless an officail person from Red Gate states that is the solution.
Additionally it is a bug. I think it needs to be addressed.
If you are not from Red Gate, then please do not comment any further as you are making incorrect assumptions. / comments
It is not strange.
That you think so makes me think you are not very familiar with computers.
I am not going to change any registry settings unless an officail person from Red Gate states that is t...
I am sorry but none of those situations apply.
This is a brand new system. SQL Server 2005 was installed first.
Then SQL Compare was installed.
There is no way is should "remember" Query Analyzer since that was never installed on this machine. / comments
I am sorry but none of those situations apply.
This is a brand new system. SQL Server 2005 was installed first.
Then SQL Compare was installed.
There is no way is should "remember" Query Analyzer ...
A few comments...
I have found that SQL Compare, like previous versions does not seem to recognize instances. It lists the server, but you must add in the instance notation.
Additionally, for default instance or multi instance, when it recognizes servers that have SQL server installed on a non-standard port - it lists the server in the drop-down, but you must modify it to include the non-standard port before you click the dropdown for databases. Otherwise it takes some time to time-out before you can add in the port.
I don't know if you can actually do anything for non-standard ports, but it seems strange that it can see that the server is a SQL server (so it must somehow look on other ports?) / comments
A few comments...
I have found that SQL Compare, like previous versions does not seem to recognize instances. It lists the server, but you must add in the instance notation.
Additionally, for defa...
Also,
After I have altereted the entry to my nonstandard port or altereted it to include the instance, the next time I go to create a new project - the drop-down menus of the servers still include the same as before - just the server name and I have to re-enter instances or re-enter non-standrad ports.
It would be nice if it at least rememebered changes to the list that the user entered if it cannot detect that information on its own.
Another idea (at least for the non-standard ports) is what if there was an application option that allowed you to specify the "default" port that should be examined? / comments
Also,
After I have altereted the entry to my nonstandard port or altereted it to include the instance, the next time I go to create a new project - the drop-down menus of the servers still include...
On Feb 17th you said the 4.3 release was a few weeks away. However, I still see only version 4.1 listed on the website.
It has been a few weeks - in fact a month. Is this fixed yet and is there an update on this release? This is a critical bug that is seriously hindering our operations.
Right now we have to manually modify every script which is labor intensive, time consuming, and very error-prone. / comments
On Feb 17th you said the 4.3 release was a few weeks away. However, I still see only version 4.1 listed on the website.
It has been a few weeks - in fact a month. Is this fixed yet and is there a...
Hi,
I see the post 2 weeks ago saying "this will be fixed soon". However, We are having the same problem with version 4.1.0.59. This is a newer version than the product originally reported at the beginning of this thread.
Is there any estimate as to when this issue will be fixed? This is a serious problem for us as we are developing applications on SQL 2005 and need to be able to sync between our development and production servers.
Thanks / comments
Hi,
I see the post 2 weeks ago saying "this will be fixed soon". However, We are having the same problem with version 4.1.0.59. This is a newer version than the product originally reported at th...