November 17, 2003 at 9:06 am
Does anybody know the difference between these two sqldmo flags?
SQLDMOScript_DatabasePermissions Generate Transact-SQL database privilege defining script. Database permissions grant or deny statement execution rights.
SQLDMOScript_ObjectPermissions Include Transact-SQL privilege defining statements when scripting database objects.
Brian Lockwood
LockwoodTech Software - value added SQL tools
Brian Lockwood
President
ApexSQL - SQL Developer Essentials
November 18, 2003 at 6:46 am
I dont. I see that you can use the SQLDMOScript_Permissions flag to get both, but BOL sure doesnt make much of a distinction. My hunch would be that one would return create table type access, the other grant/deny type stuff on objects. Not tested yet.
Andy
November 18, 2003 at 7:31 am
thx for reply. we'll check it ourselves and let you know if we find out anythings
Brian Lockwood
LockwoodTech Software - value added SQL tools
Brian Lockwood
President
ApexSQL - SQL Developer Essentials
November 18, 2003 at 7:52 am
from one of my developers:
"Those flags handle different rights sets.
SQLDMOScript_DatabasePermissions:
Rights for creating objects: CREATE/DROP/ALTER statements
and BACKUP/RESTORE
SQLDMOScript_ObjectPermissions
Rights for data access: SELECT/UPDATE/DELETE/INSERT/EXEC statements
It is only my supposition because this is not discovered by documentations."
Brian Lockwood
LockwoodTech Software - value added SQL tools
Brian Lockwood
President
ApexSQL - SQL Developer Essentials
November 19, 2003 at 5:30 am
November 20, 2003 at 2:20 pm
it get's better ....
"The result of testing these flags is strange. So, Script-method of Table-object gives identical results with separated SQLDMOScript_ObjectPermissions
and SQLDMOScript_DatabasePermissions - the true sets of rights. But Script-method of StoredProcedure-objects gives permissions only with SQLDMOScript_ObjectPermissions
and nothing with SQLDMOScript_DatabasePermissions.
Script-method of Database-object ignores fully both SQLDMOScript_ObjectPermissions and SQLDMOScript_DatabasePermissions
and doesn't show any rights that can be viewed in EM (last pad in properties of a database)."
Brian Lockwood
LockwoodTech Software - value added SQL tools
Brian Lockwood
President
ApexSQL - SQL Developer Essentials
November 21, 2003 at 9:07 am
"Yes, that strange perception of these flags by SQLDMO forces us to use always both flags together or combined flag SQLDMOScript_Permissions."
one more reason why we're ripping SQLDMO out of our apps....
Brian Lockwood
LockwoodTech Software - value added SQL tools
Brian Lockwood
President
ApexSQL - SQL Developer Essentials
November 21, 2003 at 11:19 am
Thats interesting. So you're going to go against system tables directly? What about for Yukon? I've used DMO with decent success, but definitely not for anything that had to be as robust as a commercial product.
Andy
November 21, 2003 at 11:29 am
sqldmo is ok to start out with but performance is terrible - we use it for ancilliary tasks only now - but even for this it is no good. our comparison algorithm cuts against system tables directly a long time ago
we have documented a few other issues with sqldmo as well and over time have replaced certain parts of it that were unreliable - now we're pretty much ready to chuck the whole thing.
the only enterprise level solution is to roll up your sleeves and do the "wet work" yourself against system tables. we've basically replicated sqldmo but our solutions produces correct results and is much faster. we just need to roll it out to all products.
Yukon? - YuKidding?
Brian Lockwood
LockwoodTech Software - value added SQL tools
Brian Lockwood
President
ApexSQL - SQL Developer Essentials
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply