|
Name |
abaspecialperms |
|
Code |
ap_spp |
|
Creation Date |
27 april 2010 17:20:12 |
|
Modification Date |
24 september 2012 09:43:22 |
|
Comment |
Objects with special permissions. |
|
This table holds special permissions for objects. That is, permissions entered with the macros $DBPERM and $SERVERPERM. The table also includes assemblies for which EXTERNAL_ACCESS or UNSAFE permission has been specified with the $DLLINCLUDE macro.
On SQL 2000, the datatype is image. (When you upgrade to a later version, you should alter the column to use varbinary(MAX). |
|
|
|
Data |
NOT |
F |
|
|
objname |
|
sysname |
X |
X |
The object. |
|
permno |
|
smallint |
X |
|
Running number. |
|
|
bit |
X |
|
Server-level permission? |
|
|
|
nvarchar(4000) |
X |
|
The required permission. |
|
|
|
varbinary(MAX) |
|
|
The real assembly. |
|
|
|
varbinary(MAX) |
|
|
The safe dummy. |
|
Name |
Columns |
Options |
PK |
|
pk_ap_spp |
objname, permno | clustered |
X |
|
Whether the permission is a server-level permission specified with $SERVERPERM or $DLLINCLUDE, or a database-level permission specified with $DBPERM. |
|
The actual permission. That is, the argument to the macro in question - $DBPERM, $SERVERPERM or $DLLINCLUDE. |
|
If non-NULL, the object is an assembly, and this is the real assembly that requires UNSAFE or EXTERNAL_ACCESS permission. The object is stored in an AbaPerls table intermediately, when the safe version is loaded initially.
On SQL 2000, the datatype is image. (When you upgrade to a later version, you should alter the column to use varbinary(MAX). |
|
The dummy version of the assembly that can be loaded with SAFE permission. (We need to store this assembly, to be sure that we can load it into the master database. The real assembly cannot be loaded into master, since master may not be trustworthy.) |
|
Parent Table |
Foreign Key Columns |
|
objname |
|
|
|