Comments
Sort by recent activity
Yes! It works in 8.0. Many thanks. / comments
Yes! It works in 8.0. Many thanks.
This thread has gone dormant but I hope the problem is or has been addressed. I'm hoping Michelle Taylor or someone else from Red-Gate will give us an update. / comments
This thread has gone dormant but I hope the problem is or has been addressed. I'm hoping Michelle Taylor or someone else from Red-Gate will give us an update.
Using SQL Compare 7 comparing a test database with permissions granted to roles by both the 'dbo' schema and one named 'TestSchema_1', the role permissions were compared and synchronized for 'TestSchema_1' but were ignored for schema 'dbo'.
My understanding of SQL Server 2005 is that 'dbo' should be treated in this instance just like any other schema and that these permissions should synchronize.
I look forward to early news on this matter. / comments
Using SQL Compare 7 comparing a test database with permissions granted to roles by both the 'dbo' schema and one named 'TestSchema_1', the role permissions were compared and synchronized for 'TestS...
I'm getting emails for this thread so that's all the notice I need. Thanks for your prompt response. / comments
I'm getting emails for this thread so that's all the notice I need. Thanks for your prompt response.
Also, this topic is now a SQL Compare 7 issue and should probably be moved there. / comments
Also, this topic is now a SQL Compare 7 issue and should probably be moved there.
The securable object I am using is a schema. A database role has been assigned permissions on all objects belonging to a schema.
For example, a new database role is created called partialdatawriter, and the dbo schema properties dialog has been used to grant select and update permission (for all objects in the dbo schema) for this role.
These permissions are not compared or synchronized. / comments
The securable object I am using is a schema. A database role has been assigned permissions on all objects belonging to a schema.
For example, a new database role is created called partialdatawriter...
Brian:
Do you have any new info on this topic? It's an incredibly useful feature, if it worked.
Andrew / comments
Brian:
Do you have any new info on this topic? It's an incredibly useful feature, if it worked.
Andrew
Yes, that solves it. Thx! / comments
Yes, that solves it. Thx!
I would prefer they NOT be the same. In many instances, the documentation (and even the column name) at opposite ends of an FK relationship are quite different.
But there would be value in showing the opposing column name and documentation while editing an FK column, making it easier to refer to the other and allowing cut and paste (which would cover Janie's suggestion too).
Andrew Culver / comments
I would prefer they NOT be the same. In many instances, the documentation (and even the column name) at opposite ends of an FK relationship are quite different.
But there would be value in showing ...