Comments
Sort by recent activity
Just to be clear, a SQL Server snapshot is treated as a separate database within SQL Server, but is actually stored as the differences from the snapshotted database from a particular point in time (when the snapshot was created), and overwritten data on the source database is copied into the snapshot as it gets updated - see http://msdn.microsoft.com/en-us/library/ms175158.aspx and http://msdn.microsoft.com/en-us/library/ms187054.aspx .
A SQL Compare snapshot is a binary file containing a serialized version of the whole schema information from a database.
Does that make things a bit clearer? / comments
Just to be clear, a SQL Server snapshot is treated as a separate database within SQL Server, but is actually stored as the differences from the snapshotted database from a particular point in time ...
This is a known issue with the UI, and will be fixed in version 7. This is only an issue with the counter itself; any objects you select with the spacebar will be included in the synchronization. / comments
This is a known issue with the UI, and will be fixed in version 7. This is only an issue with the counter itself; any objects you select with the spacebar will be included in the synchronization.
This option has been added to SQL Compare 8, and is available in the beta.
Simon C / comments
This option has been added to SQL Compare 8, and is available in the beta.
Simon C
I've had a look at the files you sent in, and it seems that the parser doesn't like the brackets around the CAST expressions - if you remove those, the files should parse successfully. This has been added to the relevant bug (SC-3656), and we'll look at fixing this for version 7
Thanks for the bug report / comments
I've had a look at the files you sent in, and it seems that the parser doesn't like the brackets around the CAST expressions - if you remove those, the files should parse successfully. This has bee...
I'm afraid the parser currently doesn't accept this syntax - the problem is the @MADBGUID variable name in the TO SERVICE command, and SQL Compare just ignores any files in the script folder that don't parse correctly. I've filed a bug about this (SC-3786) to be fixed for v7. As a workaround in the meantime, you could replace the @MADBGUID variable with its contents as a quoted string, which the parser in v6.2 will accept.
Thanks for the bug report
Simon / comments
I'm afraid the parser currently doesn't accept this syntax - the problem is the @MADBGUID variable name in the TO SERVICE command, and SQL Compare just ignores any files in the script folder that d...
The SQL Compare 8 beta has an updated synchronization wizard that allows you to specify the filename for the sync script. Please try it out and let us know what you think.
Simon C / comments
The SQL Compare 8 beta has an updated synchronization wizard that allows you to specify the filename for the sync script. Please try it out and let us know what you think.
Simon C
If your assembly targets .NET 3.5, then it should run successfully on windows 7 with .NET 3.5 and 4.5 installed (.NET 3.5 is installed by default on windows 7). SA will maintain the target framework version of the main assembly. / comments
If your assembly targets .NET 3.5, then it should run successfully on windows 7 with .NET 3.5 and 4.5 installed (.NET 3.5 is installed by default on windows 7). SA will maintain the target framewor...
Yes, this is an issue in SA. We probably couldn't support such assemblies as the main assembly, as we need to know what version of mscorlib to read, but we could support them as dependencies by simply defaulting to the mscorlib of the main assembly.
I've added this into the system as SA-1672 / comments
Yes, this is an issue in SA. We probably couldn't support such assemblies as the main assembly, as we need to know what version of mscorlib to read, but we could support them as dependencies by sim...
By default, SA will obfuscate all internal and private members of dlls, and public, internal and private members of exes.
If there's some internal or private members that aren't being obfuscated when they should be, you can turn on trace logging (http://www.red-gate.com/supportcenter/c ... a_Log_File) which logs everything that wasn't obfuscated with a reason why it wasn't. / comments
By default, SA will obfuscate all internal and private members of dlls, and public, internal and private members of exes.
If there's some internal or private members that aren't being obfuscated wh...
If the assembly is a dll, no public members are pruned at all. If the assembly is an exe, all public members are pruned if they are not used elsewhere. This includes public interfaces.
May I ask what prompted this question? / comments
If the assembly is a dll, no public members are pruned at all. If the assembly is an exe, all public members are pruned if they are not used elsewhere. This includes public interfaces.
May I ask wh...