Comments
Sort by recent activity
@Tianjiao_Li I'm not sure how to check the currently available options apart from on the docs page. It doesn't seem to match the UI options as they appear to roll up multiple options behind a single checkbox in some cases. I've attached a screenshot of our current option setup in the UI. Our current set of options in the project file are: ObjectExistenceChecks, DecryptPost2kEncryptedObjects, UseClrUdtToStringForClrMigration, NoDeploymentLogging, DisableSocForLiveDbs, IgnoreChecks, IgnoreDatabaseAndServerName, IgnoreFileGroups, IgnoreNotForReplication, IgnorePermissions, IgnoreQuotedIdentifiersAndAnsiNullSettings, IgnoreStatistics, IgnoreSystemNamedConstraintNames, IgnoreUserProperties, IgnoreWhiteSpace, IgnoreWithElementOrder @Alex B It's filtered to compare everything apart from Asymmertric keys, Roles, Security policies and Users. If you meant what is setup to be ignored by the comparison rather than just filtered out of the results, please see above for the full list! We don't use migration scripts at all, with the "Ignore migration script for database" option ticked in the UI. Does this translate to the DisableSocForLiveDbs option in the project file?We also haven't added any extended properties specifically for SQL Compare. Thanks, Josh / comments
@Tianjiao_Li I'm not sure how to check the currently available options apart from on the docs page. It doesn't seem to match the UI options as they appear to roll up multiple options behind a singl...
Not really, the issue seemed to resolve itself. I think network quality was part of the issue but it could have been one of the many SQL Compare releases that improved it. Trying it again now it took around 2 mins (most of the time stuck on "Reading object text (99%)") to do a comparison to a server in our local network, but that's a lot better than the 20+ mins it took when I raised this initially. / comments
Not really, the issue seemed to resolve itself. I think network quality was part of the issue but it could have been one of the many SQL Compare releases that improved it.Trying it again now it too...
I've raised a support ticket for this, hopefully the outcome can be posted back to this discussion for others who come across this issue. / comments
I've raised a support ticket for this, hopefully the outcome can be posted back to this discussion for others who come across this issue.
Using 13.3.5.6244 currently. Also tried on 13.1.x before upgrading the other day to see if that would fix it! Maybe something to note, but I notice it a lot more with DBs being compared across a network rather than being on my local machine. I could pull one of the networked DBs back to my machine to test this out, unless you might have another theory? / comments
Using 13.3.5.6244 currently. Also tried on 13.1.x before upgrading the other day to see if that would fix it!Maybe something to note, but I notice it a lot more with DBs being compared across a net...
Pulled the exact database back from the networked location, performed the comparison again and it completed in 20 seconds, so I definitely think there is a problem here! When I say networked I mean LAN, not across the internet, so there isn't much network overhead. Any further diagnostics I can gather to help out here? / comments
Pulled the exact database back from the networked location, performed the comparison again and it completed in 20 seconds, so I definitely think there is a problem here! When I say networked I mean...