Lost SQL Server Changes

This is probably not productive, but I've just encountered one strange problem after the other with Integration services, to the point that I'm afraid struggling any more with it is going to hurt my productivity.

It is now 2:00 . I've been trying to build a simple package since 10:00 AM



It really is a shame because it seems to have alot of promise.



I'm using execute SQL task to call stored procedures ins a sequence. I like to drag the boxes in such a way around so that the pakage is more readable. Crash! Work gone.



So I restart VS Develop. Try it again. I'm calling a stored procedure and the taks fails. Apparently has to do with truncating from a table linked by a foreign key. So I change the stored proc to handle the problem. Run it. runs fine. Go back to Inegration services. Run the corresponding task. Fails. Same message.Go back to stored procedure. Notice changes I mad diodn't get saved. Funny how did that happen?. I make the changes again. Run the procedure. Runs fine. Go back to IS run task. same message. What the??



I look at the strored procedure again. my changes are gone again. Light bulb goes on. Hey, Integration services has taking it upon itself to reverse all the changes I made to stored procedures it references. 2 hours gone.

And its still reversing my changes after a reboot. So I drop the package figuring its corrupt and start all over again, meticulously rearranging all the boxes to the way I had them before, keeping my fingers crossed all the while, that it really can't be that everythime I make a change to a stored procedure referenced by an execute SQL Task, I have to drop the package and build it again.



And I'm working under a tight deadline.



Just wanted to give you guys some insight into customer experience with the tool. I don't mean to sound irritable, buts its just I've run into 1 too many ropdadblocks with this thing and I am really missing DTS.