Comments
Sort by recent activity
Firstly, a slightly better workaround - you can specifically filter the DBO schema using the rules and filters panel - hover over the line with the checkbox for Schema and you'll see a little pencil icon appear which will let you specify a particular object name to filter out.
Secondly, SQL Compare probably shouldn't be showing you an unsynchronizable difference in DBO without some kind of warning [image] . (We enabled the display of a range of system objects like dbo in v8 because some people wanted to synchronize the changes that they had made to them.) If you could a few questions to help me get to the bottom of this:
Does the DBO schema have permissions etc set on it, auth changes, or anything else that would set it apart from the normal default dbo schema you get when creating a new database?
Is there anything in the SQL Differences pane (the popup area at the bottom of the screen which comes up when you click on the difference in the main object list view) for the DBO object, on either side?
Is there a DBO.sql file in your script folder, and if so what's in it? (If you can send the entire script folder, ideally along with a backup of the live database, to me at michelle.taylor@red-gate.com that would be even more helpful, but I appreciate that's not always possible.) / comments
Firstly, a slightly better workaround - you can specifically filter the DBO schema using the rules and filters panel - hover over the line with the checkbox for Schema and you'll see a little penci...
It does help a lot - thank you. That's now in our bug tracking system as SC-4507 and hopefully we'll get it sorted out shortly, although unfortunately it probably just missed the deadline for the next point release.
Meanwhile you can work around it by creating a .sql file somewhere in the script folder with the GRANT VIEW DEFINITION lines in it - SQL Compare will pick them up once they're there, it just isn't writing them out properly. / comments
It does help a lot - thank you. That's now in our bug tracking system as SC-4507 and hopefully we'll get it sorted out shortly, although unfortunately it probably just missed the deadline for the n...
I've added a link to this thread to our open feature request for this feature - we haven't had quite enough demand to implement it as yet (and there have been thoughts of having a seperate 'server compare' style program for comparing properties above the database object level and server objects), but the more requests we get, the more likely it is to float to the top of our feature request list [image] . / comments
I've added a link to this thread to our open feature request for this feature - we haven't had quite enough demand to implement it as yet (and there have been thoughts of having a seperate 'server ...
I don't have a way to automate the column drops, I'm afraid, but SQL Compare ought to be doing it for you and I've added this forum post to the bug report for this issue to try and get it fixed for you (although it probably won't be coming out in the next point release, as CLR dependencies tend to be awkward). / comments
I don't have a way to automate the column drops, I'm afraid, but SQL Compare ought to be doing it for you and I've added this forum post to the bug report for this issue to try and get it fixed for...
We try to patch up cases which have been renamed through the GUI - what we've not yet started to change is 'is this object's name fully qualified or not'. Sometimes we do accidentally change that in the course of fixing GUI renames, but mostly we try to preserve it.
I've added a link to this post to the existing feature request for such an option, so it's possible we'll pick it up to implement in future versions. / comments
We try to patch up cases which have been renamed through the GUI - what we've not yet started to change is 'is this object's name fully qualified or not'. Sometimes we do accidentally change that i...
If the stored procedure was originally created on the live database with 'CREATE PROCEDURE ProcName' rather than 'CREATE PROCEDURE dbo.ProcName' then it will end up scripted out as 'CREATE PROCEDURE ProcName'.
We've attempted to apply solutions to this a few times, but we're rather wary of actually editing people's stored procedures (which is what fixing this would basically be doing) because we don't want to assume that people didn't mean to create them like that... / comments
If the stored procedure was originally created on the live database with 'CREATE PROCEDURE ProcName' rather than 'CREATE PROCEDURE dbo.ProcName' then it will end up scripted out as 'CREATE PROCEDUR...
This is not because you are using the trial version - the trial should be a fully working version with all features enabled.
I know that some mapping changes aren't picked up by the 'project has changed' code in SDC 7 (because we've fixed the behaviour for SDC 8 ), so could it be that you created the project but didn't save it after the mapping changes were completed?
Does this happen whenever you save and reload a project with mappings / can you provide more information on exactly what steps you take when you see this problem and which version of Data Compare you've got? I've tried a couple of simple mapping changes and they seem to be saving into projects for me (and prompting me to save on exit). / comments
This is not because you are using the trial version - the trial should be a fully working version with all features enabled.
I know that some mapping changes aren't picked up by the 'project has ch...
Sounds like a bug. Does it still happen if you take a snapshot of the database on each side, and compare those? We'd like to look into it and the easiest way to do so is if you can send us some snapshots (or backups we can use to recreate the databases, if it only happens on live databases) that reproduce the problem.
Obviously we understand this isn't always possible - even just the CREATE statement for the view might help us understand what's going on. If you want the issue to be properly tracked you should send further information to support@red-gate.com, or you can send it to me directly at michelle.taylor@red-gate.com if you'd prefer. / comments
Sounds like a bug. Does it still happen if you take a snapshot of the database on each side, and compare those? We'd like to look into it and the easiest way to do so is if you can send us some sna...
That's because there isn't an option - backup before sync isn't available from the command line.
Would you like it to be, and how would you want to use it if it was? We've always assumed that if you're using the command line you could just call something else to execute a backup command before calling Data Compare, and so didn't think it was worth putting the feature into the command line... / comments
That's because there isn't an option - backup before sync isn't available from the command line.
Would you like it to be, and how would you want to use it if it was? We've always assumed that if yo...
Thanks for bringing this to our attention - we'd actually noticed this internally, but just didn't quite get around to fixing it for the early access release. / comments
Thanks for bringing this to our attention - we'd actually noticed this internally, but just didn't quite get around to fixing it for the early access release.