Comments
Sort by recent activity
I think I know what is going on here.
That is the premable that occurs when you save with UTF with Preample.
We had some trouble with the encoding types and .NET2, that stopped you setting the encoding type when saving scripts. I think we have them all sorted now, so in the final release you will be able set the encoding type to just UTF which should get rid of this.
Just out of interest, if you go into Tools>Application Options can you tell me what the Encoding option is set to in the Saving SQL Scripts section?
Ta,
Jonathan / comments
I think I know what is going on here.
That is the premable that occurs when you save with UTF with Preample.
We had some trouble with the encoding types and .NET2, that stopped you setting the enco...
Ken,
Did you have the SQL Compare add WITH ENCRYPTION option enabled? You can find it in the Project Configuation Dialog > Options Tab > More Options > Behavior section.
Having said that the default you have pasted in should not be encryptable so that is very very strange. Can you post what you were changing the default too? As this might be SQL Compare saying that it cannot read the default, though I have not seen this before.
If you have the two test case database that exhibits this behaviour can you forward me on the schema if you are able to?
Regards,
Jonathan / comments
Ken,
Did you have the SQL Compare add WITH ENCRYPTION option enabled? You can find it in the Project Configuation Dialog > Options Tab > More Options > Behavior section.
Having said that the defaul...
I have PMed you about this.
Regards,
Jonathan / comments
I have PMed you about this.
Regards,
Jonathan
Hi dwainew,
If this is the same problem that we have been seeing recently we think we have a fix for this, but to confirm this we are going to need a SQL Profiler trace. If you could start a trace on the server which contains the database that is causing the error, then run the comparison in SQL Compare, stopping the trace after the error occurred.
If you can then email me the trace file (jonathan [dot] watts [at] red [dash] gate [dot] com) I will see if this is the same issue that we have a fix for.
Regards,
Jonathan / comments
Hi dwainew,
If this is the same problem that we have been seeing recently we think we have a fix for this, but to confirm this we are going to need a SQL Profiler trace. If you could start a trace...
If you just want a script summary you can copy the script summary (I think it is a right click option) and save that.
However, if you are looking for anything more detailed we suggest that you use the snapshot or save to script functionality to save baselines of your databases before you synchronise them. This way you can go back an compare them afterwards.
Regards,
Jonathan / comments
If you just want a script summary you can copy the script summary (I think it is a right click option) and save that.
However, if you are looking for anything more detailed we suggest that you use ...
Hi there,
Unfortunately this is not possible at the moment. It is a very interesting idea and one we may look into doing this in the future.
Regards,
Jonathan / comments
Hi there,
Unfortunately this is not possible at the moment. It is a very interesting idea and one we may look into doing this in the future.
Regards,
Jonathan
Hi there,
For various reasons we had to change these controls v6, unfortunately we had not included the error messages for the beta.
I have just been checking and they have been put back into our latest internal build so will be back in the final release.
Thanks,
Jonathan / comments
Hi there,
For various reasons we had to change these controls v6, unfortunately we had not included the error messages for the beta.
I have just been checking and they have been put back into our l...
Hi there,
Thanks for your feedback, these are all good ideas, I will add them to the system and we will see what we can do.
Regards,
Jonathan / comments
Hi there,
Thanks for your feedback, these are all good ideas, I will add them to the system and we will see what we can do.
Regards,
Jonathan
Radovan,
Unchecking the "Auto save synchronisation SQL scripts" option in Tools > Application Options dialog should give you part of what you are after.
Regards,
Jonathan / comments
Radovan,
Unchecking the "Auto save synchronisation SQL scripts" option in Tools > Application Options dialog should give you part of what you are after.
Regards,
Jonathan
Radovan,
As I said this was only half a fix. We may consider adding an option for this in the future, but at the moment we are not going to mark this a high priority.
Sorry,
Jonathan / comments
Radovan,
As I said this was only half a fix. We may consider adding an option for this in the future, but at the moment we are not going to mark this a high priority.
Sorry,
Jonathan