Reference Data

[Doug Blake]

I have seen this subject bandied about the forums and not paid much attention to it before, however...

I am using TFS to version control my project which is on a MSSQL Server and it works great. Investigating whats in the reference data has taken my breath away, because there is lots of project specific stuff in there that I didnt know about.

Haha I hear the experts laugh, another one got caught out. So my question is, does anyone have a process that manages the reference data so that people checking in and out model info get the correct reference data for their version?

[qwerty]

I once developed an add-in to regularly save the ref-data on a nightly basis for a customer. That worked fairly ok but sometimes it's hard to keep the model really consistent. Changing the glossary f.e. is something that can clobber all your work when you don't have a real chance to see that something has changed.

q.

[Doug Blake]

I once developed an add-in to regularly save the ref-data on a nightly basis for a customer. That worked fairly ok but sometimes it's hard to keep the model really consistent. Changing the glossary f.e. is something that can clobber all your work when you don't have a real chance to see that something has changed.

q.

I am loath to start on the "add-in" route, but could you send me your solution? Looks like I am going to have to get my hands dirty but I have said this before, these are things that SHOULD BE IN THE TOOL!!!!

[qwerty]

Sorry Dough, but as said it was for a customer. So the rights are his.

However, it was quite simple. For the according tables (t_glossary etc.) I issues a SQL and then dumped the return value to a file. The file was a stand-alone batch that attached to the repository and was triggered via the usual Windoze mechanisms.

q.