OTHER PROCEDURES
|
sp_bcp: Create unix script to bcp in/out database |
|
sp_date: Who can remember all the date styles? |
|
sp_iostat: Loops n times showing active processes only |
|
sp_grep: Search for patern |
|
sp_isactive: Shows info about a single active process |
|
sp_lsLists specific objects |
|
sp_ quickstatsQuick dump of server summary information |
|
sp_whoactive: Show info about who is active |
The following is a list of errors generated by the auditing procedures
31001 User +name+ Is Locked
31002 Login +name+ Is Expired
31003 User +name+ Has Null Password
31003 User +name+ Has Null/Short Password
31003 User +name+ Has Short (<=4 character) Password
31004 User +name+ Has +dbname+ Database As Default
31005 Allow Updates is Set
31006 ERROR: Num Open Devices Parameter Set Too Low
31007 ERROR: Num Open Databases Parameter Set Too Low
31008 Allow Updates is Set
31009 User +name+ Has Pasword=Id
31010 Allow Updates is Set
31011 Tempdb is only +@tempdb)+MB
31012 User sa is trusted from +srvname
31013 Database +name+ Created For Load
31014 Database +name+ Suspect
31015 Database +name+ Offline
31016 Database +name+ Offline until recovery completes
31017 Database +name+ Is Being Recovered
31018 Database +name+ Has Suspect Pages
31019 Database +name+ Is Being Upgraded
31020 Database +name+ -> No Log Device and No TL on Chkpt
31021 ERROR: MIRROR BROKEN: +name
31022 ERROR: CHECK MIRRORING: +name
31025 x.name+ Config Has Been Reset To +c.value2+ (default=+c.defvalue)
31030 ERROR: Login +name+ Has an invalid default db (dbname)
31031 Device +rtrim(dev.name)+ Is Mapped But Unused (no segments). Size (MB) = usg.size/512.
31032 ERROR: Sybsystemprocs should be > 60 MB (@c)
31033 ERROR: tempdb should be >= 100 MB (@c)
31034 Database +name+ Is not auto-shrink
31035 Database +name+ Has No Torn Page Detection
31036 Database +name+ Is Unusable
31037 User +name+ Has Stupid Password
31038 user +u.name+ can use db but lacks login
31040 File +name+ Is Not Autogrowth
31101 User +user_name(uid)+ Owns Objects
32000 Login +m.name+ is aliased to +u.name
32007 suid + a.suid+ lacks login and is aliased to +u.name
32008 user +u.name+ can use db but lacks login suid=suid
32009 database +db_name()+ has not been tran dumped in
32010 Object +name+ Has No Comments
32010 count(*)+ Objects Have No Comments
32011 Comments for id + id + have no object
32013 v.name + Permission granted to + u.name
32014 Table +object_name(id)+ Index + name + is suspect
32016 Object: +object_name(s1.id)+ Has Statistics From +s1.moddate 0)+ and +s2.moddate 0)
32017 Object: +object_name(s1.id)+ Has OLD Statistics From +s1.moddate 0)
32018 name + permissions granted to public on +object_name(id) from sysprotects master.dbo.spt_values c
32019 db_name()+ has +@dat+MB data and + @log+MB log
32100 Login + m.name + is aliased to + u.name
32101 User +user_name(uid)+ Has + count(*)+ Objects
32101 User +user_name(uid)+ Owns Objects
32102 Object +name+ exists in the db and in sybsystemprocs - This is a possible Trojan Horse
32102 Object +name+ in master - Possible Trojan Horse
32102 Object +o.name+ Exists in master and the database - Possible Trojan Horse
32102 Object +o.name+ Possible Trojan Horse (Exists in master)
32103 Object +object_name(id)+ has access to syslogins
32104 No Groups Exist In Database +db_name()
32105 User +n1.name+ is a member of group public
32106 Group Public +rtrim(v.name)+ access to + count(*) + objects
32106 Group Public access to object +o.name+ type=+o.type
32110 DB Collation +collation+ != Server Collation + serverproperty(collation)