Activity overview
Latest activity by don
Agree it is not normal practice. The root question is why were these "System" "Type" stored procedures created? Appears to be a set of Visual Source Safe created objects but could be wrong about this. Speculate that SQL-DMO was used as the MSDN agreement includes some neat SQL-DMO tools. Might create a nightly sql job to go look for them every night. Does not seem to be a serious enough issue to add a trigger or audit table at this time. Short term after testing may create a script to delete them. / comments
Agree it is not normal practice. The root question is why were these "System" "Type" stored procedures created? Appears to be a set of Visual Source Safe created objects but could be wrong about ...
--Changes since November 1, 2006--
Use dbname
select base_schema_ver AS ObjectVersionNumber, * from sysobjects
where crdate >= '2006-11-01 00:00:00.000'
order by crdate DESC / comments
--Changes since November 1, 2006--
Use dbname
select base_schema_ver AS ObjectVersionNumber, * from sysobjects
where crdate >= '2006-11-01 00:00:00.000'
order by crdate DESC
SQL2000 System objects not compared
Hi:
Is there a way to include system owned objects in SQL Compare 5.2.032. Ran a compare and only user owned objects compared in SQL Server 2000. Have an issue where some new stored procs are sho...