I'm running the current version of the model in SDE without any problems. Early versions had just a few instances where field names were using reserved words in SQL Server, but those have been fixed.
Leon
I'm just now importing from the XML workspace and getting some naming conflicts.
CV Domain : SignCode > SignCode_2
CV Domain : LandForm > LandForm_2
CV Domain : PoleType > PoleType_2
CV Domain : BulbType > BulbType_2
CV Domain > wHydrantManufacturer > wHydrantManufacturer_2
CV Domain > ServiceRequestType > ServiceRequestType_2
CV Domain > SignalType > SignalType_2
CV Domain > SpecialEventAreaType > SpecialEventAreaType_2
CV Domain > Direction > Direction_2
CV Domain > piAlertType > piAlertType_2
CV Domain > VideoFeedType > VideoFeedType_2
CV Domain > EmergencyFacility > EmergencyFacility_2
CV Domain > SpecialEventLineType > SpecialEventLineType_2
CV Domain > SpecialEventPointType > SpecialEventPointType_2
CV Domain > ParkingSpaceLocation > ParkingSpaceLocation_2
Any idea why these would show up in RED on a brand new dump? This is a brand new Local Government Database. I'm very confused.
When I say "just now importing" I mean that I just deleted my original Local Gov DB (empty, no worries) and started a fresh update with the new XML Workspace...
Deleting the Feature Data sets doesn't get rid of the domains from the SDE DB. I have had that same set of warnings come up when I was working with my SDE db and it didn't cause problems.
Georgia
Removed the domains and voila! Thank you so much!