SQL2000 System objects not compared

don

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 showing up in various servers and db's. In the specific exampe the Prod db's is different than the test server db's so know something happened. Searched some different server db's and the create dates are all different. One of the many created I searched for was "dt_checkinobject_u" which took me to this link. Not sure if this is the correct answer in this case so want to be more sure.

http://forums.microsoft.com/TechNet/Sho ... &SiteID=17
These are created when you connect using some Visual Tools of Microsoft, this is the list of procedures which will be created during the process:

dt_addtosourcecontrol
dt_addtosourcecontrol_u
dt_adduserobject
dt_adduserobject_vcs
dt_checkinobject
dt_checkinobject_u
dt_checkoutobject
dt_checkoutobject_u
dt_displayoaerror
dt_displayoaerror_u
dt_droppropertiesbyid
dt_dropuserobjectbyid
dt_generateansiname
dt_getobjwithprop
dt_getobjwithprop_u
dt_getpropertiesbyid
dt_getpropertiesbyid_u
dt_getpropertiesbyid_vcs
dt_getpropertiesbyid_vcs_u
dt_isundersourcecontrol
dt_isundersourcecontrol_u
dt_removefromsourcecontrol
dt_setpropertybyid
dt_setpropertybyid_u
dt_validateloginparams
dt_validateloginparams_u
dt_vcsenabled
dt_verstamp006
dt_verstamp007
dt_whocheckedout
dt_whocheckedout_u
dtproperties

Thanks,
Don

don

--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

Brian Donahue

Hi Don,

SQL Compare can only compare user objects, and filters out any object type of system. Since an online database configuration does not allow ad-hoc updates to system catalogues, this is a very sensible thing to do.

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.

Brian Donahue

That's exactly right. Someone probably used Visual Source Safe to add the database into source control. That will create all of these stored procedures. There are some other ones (such as dtproperties) that are created when you construct your first database diagram.