>I haven't done this myself, but one idea is to convert the SDT meta data tables to XML before checking them in and then back when checking them out. That way, VSS can very easily see what changes were made. You could even automate this with a little utility that gets a reference to the file objects in the project for the XML files, calls the CheckOut method, does XMLTOCURSOR(), copies the cursor to a table, and then calls the SDT Database Explorer.
>
>Doug

Hi Doug, this could possibly be a great addition to the SDT Explorer. You could have a button to add all tables in the database to sourcesafe. A button to check out a table ignoring data in the table. Then when checking in, if no structural changes were made to the table there would be no conflicts even if data was edited. There could be a button for checking out tables with data i.e. reference tables, and then raising a conflict if any data OR structural changes were made. I hadn’t really thought this through thoroughly, so shoot it down if it is not feasible.

The way we do it now is to keep a word doc in sourcesafe and type up our database changes in it and then manually merge. Not the most productive way of doing things.