Comments
Sort by recent activity
Is the problem that entire tables aren't mapping to each other by default (i.e. you don't get anything in the Tables and Views tab by default), or that the columns aren't mapping by default / a default comparison key isn't found? / comments
Is the problem that entire tables aren't mapping to each other by default (i.e. you don't get anything in the Tables and Views tab by default), or that the columns aren't mapping by default / a def...
That sounds like it can't find a default comparison key for your tables. Do they each have a unique index / primary key? If the tables have no indexes or only have nonunique indexes, Data Compare just leaves them unmapped because we don't want to just guess a comparison key and get it wrong (nonunique comparison keys can cause confusing behaviour, so we don't want to use something that SQL Server doesn't tell us is unique). / comments
That sounds like it can't find a default comparison key for your tables. Do they each have a unique index / primary key? If the tables have no indexes or only have nonunique indexes, Data Compare j...
Hi there,
You should be able to create a SQL Data Generator project against any database which has the same structure as the database under test. Save the project and then specify it by file name in the VSTS interface.
DLMA will use the project file settings, substituting in the database name when it names the temporary database. / comments
Hi there,
You should be able to create a SQL Data Generator project against any database which has the same structure as the database under test. Save the project and then specify it by file name i...
The names of the files don't matter - what are the names of the actual stored procedures (the string just after the CREATE PROCEDURE or CREATE PROC)?
Is this a script folder that you've just saved from a live database with SQL Compare, or a script folder you've made in some other way? / comments
The names of the files don't matter - what are the names of the actual stored procedures (the string just after the CREATE PROCEDURE or CREATE PROC)?
Is this a script folder that you've just saved ...
Are the actual stored procedure names just appended with a number (e.g. CREATE PROC sp_GetBillingInfo, CREATE PROC sp_GetBillingInfo1 etc) or are they named as 'numbered stored procedures' (e.g. CREATE PROC sp_GetBillingInfo;1, CREATE PROC sp_GetBillingInfo;2 etc) or in fact all named the same thing inside the files?
The filenames don't matter to SQL Compare, just the contents of the files. / comments
Are the actual stored procedure names just appended with a number (e.g. CREATE PROC sp_GetBillingInfo, CREATE PROC sp_GetBillingInfo1 etc) or are they named as 'numbered stored procedures' (e.g. CR...
It sounds like the problem some people have found with the new object decryption functionality. Try turning off the option 'Decrypt encrypted objects on 2005 and 2008 databases' and see if that fixes the problem.
If that does turn out to be your problem, email support@red-gate.com and they'll keep you up to date with the fix progress for this bug. / comments
It sounds like the problem some people have found with the new object decryption functionality. Try turning off the option 'Decrypt encrypted objects on 2005 and 2008 databases' and see if that fix...
You want to specify options with the /options switch - the default option set contains the option to enable decryption of encrypted objects.
You can just specify /options:None or if you want the rest of the default options that's /options:IgnoreFillFactor,IgnoreWhiteSpace,IncludeDependencies,IgnoreFileGroups,IgnoreUserProperties,IgnoreWithElementOrder,IgnoreDatabaseName / comments
You want to specify options with the /options switch - the default option set contains the option to enable decryption of encrypted objects.
You can just specify /options:None or if you want the re...
I haven't come across this problem before - could you provide me with a little more information?
1) Where does the script folder come from? Is it saved directly from the live database (and if so with what version of Compare), or has it been edited by hand / generated by some other tool?
2) Does the script file for the troublesome object actually contain the string '[sys].[nvarchar(max)]' or is the script parser changing the line containing this type in any way? / comments
I haven't come across this problem before - could you provide me with a little more information?
1) Where does the script folder come from? Is it saved directly from the live database (and if so wi...
Not in the current version - the easiest way to do this currently is to do the comparison, then type 'u' in the 'Find' box and deselect all of the tables beginning with u that come up.
The next version will be able to filter by this kind of thing and save rules like this with your project (from the Filter sidebar which currently can only filter out whole object types). However, we treat a table and all its triggers as a seperate object, so you still won't be able to filter out individual triggers.
Does this answer your questions? / comments
Not in the current version - the easiest way to do this currently is to do the comparison, then type 'u' in the 'Find' box and deselect all of the tables beginning with u that come up.
The next ver...
I'm afraid that SQL Compare doesn't support extended stored procedures (and as they're deprecated in favour of CLR, is unlikely to do so in future). / comments
I'm afraid that SQL Compare doesn't support extended stored procedures (and as they're deprecated in favour of CLR, is unlikely to do so in future).