My problem is that the dt objects appear in some databases as system objects and as user objects in others. Using Redgate's sql compare, I wind up with a report showing differences in these objects when they are present in both databases.
Rather than remove them, how might we get them set to system objects in a DB where they appear as user objects.
When i create database by using installation program made by
Redgate's schema generation in .Net
on my local server Dtproperties table is created. But some other servers we have i see that Dtproperties table is not created. Why it happens ? is t because of some service pack differences? or what is the reason ?
Think you'll also find using visual studio against a database will create all those tables - I have successfully removed them over the years without any problems - some software used with releases and code generation can end up doing all sorts of unncessary operations on these objects. ( mind it does the same thing when databases are replicated too!! )
( I don't actually always remove them - just when they give issues - like the compare ones for instance. )
--===== Return user created tables only. Ignores dtProperties, as well SELECT Name FROM dbo.SysObjects WHERE OBJECTPROPERTY(OBJECT_ID(Name),'IsMSShipped')=0 AND XType = 'U'