Hi I have just started working with SSIS and already stuck! My environment is: - SQL Server 2005 SP3 - Visual Studio BIDS 2005 - Team Foundation Server (TFS) 2008 SP1 Problem: everytime I execute my package, the file get checked out of TFS! Is there a reason for this? More importantly, how can I tell BIDS to check a package only if I actually want to edit it? ThanksRegards Amir

Not sure. It has always done that, even with Source Safe. But it doesn't change anything and you can alwasy "Undo Check-out" after execution is finished. What if you turned off the option to force check-out when editing?Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

Thanks Todd. That's a very strange "feature". How are you supposed to remember which packages you have actually changed and which ones were checked out by BIDS? Visual Studio doesn't do this (for .NET code). Where is hte option that you are referring to please?Amir

I may have miss-spoke with the setting. Go to Tools >> Options, and look for the Source Control node. Poke around there to see if anything might help, though I just looked and didn't see anything. But FTS options might be different than mine for Source Safe. How do you know? well, you un-check-out right after executing, I guess. Wish I had better answers.Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

This has been driving me bananas all day! I'll tell you what I have resorted to: 1. Get Latest version of solution. 2. Create new integration service project. 3. Add all the packages to my new project. 4. IF I make changes I check the file out of TFS, and overwrite the file in the TFS local folder with the file from my new project (my documents....) 5. Check in Also, be forewarned, TFS will let you check out a file, edit the heck out of it, and then tell you that you did not have the latest version only when you try to check it in. The old sourcesafe used to tell you when you checked out a file that it was not the latest version. STUPID Microsoft. Another irritation, old Sourcesafe used to let you check in files and remove local copies. That way if any were left in your local folder you knew that they had not been added to Sourcesafe. Only way I've found to accomplish the same is to add the folder back into TFS and it will ignore any files you already added. Make sense? Didn't think so. Good Luck!Michael R Milligan

STUPID Microsoft. Department of Reduncancy Department. :-)Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

Todd, Michael Thanks for your replies. I am shocked by this behaviour of BIDS. How do really large teams/projects get around this SSIS issue? I once worked in a department that had a team of 7 data migration people. They weren't using SSIS, but I hate to think what would have happened if they were! In my team there are only two of us and we are already stuck. Two questions: - Would using BIDS 2008 solve this problem or is this an (unbelievable) SSIS design flaw? - Are BIDS 2008 generated SSIS packages compatible with SQL Server 2005 (I am guessing no) Thanks!Amir