Activity overview
Latest activity by sab39
Is that reply intended to another thread? This bug isn't about needing space, at all. It's about the wrong constraints getting operated on in this scenario - the constraints get dropped/added from how the database USED to be before the schema changes, but those constraints either don't exist any more or are different. So the resulting database ends up wrong.
In the absence of any replies I worked around the problem by digging out the correct constraints in source control and replacing the relevant sections within the generated script by hand to drop/add the correct constraints, but it'd be nice to know that a future version of sqlcompare would render that unnecessary. / comments
Is that reply intended to another thread? This bug isn't about needing space, at all. It's about the wrong constraints getting operated on in this scenario - the constraints get dropped/added from ...
I can't speak for the original poster, but we have the same issue.
The reason for it in our case is that our codebase is only responsible for a subset of the database, which we identify by a common prefix used in the filter rules. The rest is under the control of a third party vendor. The inclusion of dependencies ignores the filter rules and pulls a bunch of items into source control that aren't supposed to be under source control at all. / comments
I can't speak for the original poster, but we have the same issue.
The reason for it in our case is that our codebase is only responsible for a subset of the database, which we identify by a common...
Bug with /include:StaticData when constraints change
I'm using the SQL Automation Pack which appears to include the SQL Compare command line tool 11.0.0.184.
My command line is doing a comparison between an SQL source control repository and a databas...
Evan Moss wrote:
Hello,
To be honest, I'm surprised they put that version in the automation pack (it's still in beta), but 11.0.0.184 does contain the bug fix, so it should work fine.
Thanks,
Evan
This appears to not be the case: I've just had the first case of trying to deploy using a script generated by that version that was supposed to include a migration script, and it seems not to have done so.
Can you offer any suggestions or an ETA for when a new version with the fix will be available? / comments
Evan Moss wrote:
Hello,
To be honest, I'm surprised they put that version in the automation pack (it's still in beta), but 11.0.0.184 does contain the bug fix, so it should work fine.
Thanks,
Ev...
Thanks for your help!
I managed to figure it out with trial and error and googling. I avoided the 10.7 bug by sheer luck of the fact that the Automation Pack apparently contains a v11 beta [image] / comments
Thanks for your help!
I managed to figure it out with trial and error and googling. I avoided the 10.7 bug by sheer luck of the fact that the Automation Pack apparently contains a v11 beta
Thanks for the quick response!
I'm afraid I'm a little confused by the versioning of your various products. I'm using the command line version of SQL Compare from a brand new download of the SQL Automation Pack and it claims its version number is v11.0.0.184. Does that mean I'm using a v11 beta version or is the versioning of the automation pack somehow out of sync with the standalone version?
Or, to ask a simpler version of the question - does this version from the Automation Pack have the bug discussed in this post, or not?
Thanks again! / comments
Thanks for the quick response!
I'm afraid I'm a little confused by the versioning of your various products. I'm using the command line version of SQL Compare from a brand new download of the SQL Au...
Evan Moss wrote:
Hi Craig,
I've logged this as a bug (reference SC-7142) and will let you know what I hear about it. It's looking like this will likely be fixed in 11.0 at this point.
This bug is likely to bite me too. Can you confirm whether it's fixed in current v11 betas or whether I should try an earlier v10.x version? If I use an earlier v10 version, will it have any issues with databases coming from the current latest version of SQL Source Control? / comments
Evan Moss wrote:
Hi Craig,
I've logged this as a bug (reference SC-7142) and will let you know what I hear about it. It's looking like this will likely be fixed in 11.0 at this point.
This b...
Script from source control with migration scripts?
Is there a way to use the command line to generate an SQL script that takes into account migration scripts in source control, or does this require the beta V2 migration system?
I'd like to be able ...