Team Working Environment

[ps22571]

Hello,

Can anyone confirm that this is the correct procedure when working in team environment where the EAP is stored on a network SQL Server repository.

The model we have is made up of several packages each of which are under version control.

Firstly, can you tell me the effects this has on the repository as the check out creates an XML file locally which never gets updated; I'm assuming the check
out simply locks everybody else out from using the package in the repository and the local copy is simply there in case I Undo Checkout?

I now want to work offline (out of the office) on the Package  I currently have checked out. What I am currently doing is:


- at work, I transfer the DBMS on the repository to a local EAP file on my machine using the data management

- I work at home doing work on the files I have checked out

- when I get back to work I Check In the packages from my LOCAL version

- I use the Get Package routine in the model in the server Repository

- I then Check Out the package again in the model in the server repository and continue working

Is this the ideal flow? Is there a neater way? To me there is heavy reliance on the user to check in / check out in the order I mentioned. Deviatiing from this flow potentially could have the drastic effect (as I found out) of losing the work done locally.

Any help / comments would be appreciated - I have read the white paper on Team Development but found this a bit too high level.

Thanks