Comments
Sort by recent activity
After some exchange of email wich Michelle Taylor.
It appears that SQL Compare doesn’t compare permissions on dbo (or indeed any of the properties of any system objects apart from the built-in roles, which SQL Server doesn’t flag as system objects)
An options to allow this kind of comparison will maybe put in place in futur release. / comments
After some exchange of email wich Michelle Taylor.
It appears that SQL Compare doesn’t compare permissions on dbo (or indeed any of the properties of any system objects apart from the built-in ro...
Yes it's exactly what I did:
'GRANT SELECT ON SCHEMA::dbo TO someRole'
And I only see schema object in the comparison, when the schema exists in one db and not in the other one.
e.g. Schema "Report" exists in DB1 with Select for Role1 and doesn't exist in DB2. SQL compare shows me correctly the difference.
On the other hand, if the schema "Report" exists on both base DB1 and DB2 but with or without different permission set, SQL compare doesn't shows me schema at all.
I'm expecting to see schema at least under the identical objects group.
Here are the options I set for the comparison:
Behaviour: "Force column order" and "Do not use transactions in synchronisation script" are activated.
Ignore: "whitespace", "Fill factor and index padding" and "collations" are activated.
I can also mention that all objects are activated in the filter objects pane. / comments
Yes it's exactly what I did:
'GRANT SELECT ON SCHEMA::dbo TO someRole'
And I only see schema object in the comparison, when the schema exists in one db and not in the other one.
e.g. Schema "Report...