July 17, 2009 at 8:43 am
We all know that when we build/have ssis packages on file system, there are two copies of it. One inside your soultion folder and another one inside bin folder of that solution.
Please correct me If I am wrong, the one inside the bin is the latest version(or modified) that was executed succesfully the last time. And, the one inside the solution is the latest one that was saved successfully but not executed.
Now, let's say I want to create jobs and keep my ssis packages in file system rather than sql msdb. And we all know when we create jobs using ssis in file system it asks for the location of .dtsx file. My question is which .dtsx package you want to use? the one inside the bin or the one inside the solution. I know both locations works fine. But, is there a difference or say advantages one over other. Do we have a rule here?........
July 17, 2009 at 9:48 am
I have always used the one in the solution folder and not the bin folder, while they are often the same, the one in the solution folder is the last saved version regardless of whether it was run. Also, to support my position, the one checked in when using a Source Control tool is the project one, and not the bin one..
I just want ot make sure I understand you though, you aren't pointing the job at the location of your project, you were just asking which one you would use for a job?
Can I ask an additional question, why are you deploying to the filesystem and not the package store?
CEWII
July 17, 2009 at 10:19 am
You are right, I am not pointing to project folder. I am just asking which one to used?, Although I have always used one, inside the solution folder, not the one inside the bin. So, then there is no point in having the bin or on more extra copy of packages? Now, this is another discussion.....
To ur question? Why in filesystem not in package storage.?
There is no any sort of storage device or even any form of source control. I know you are thinking?.......I did too......then I learned a lesson from a co-worker, "just flow with traffic" ( just do things that everyone is used to and been doing when ur in a position of not making any decisions).
Also, I am in intial phase of desiging my ssis packages and framework. I recently joined here and they are using linked server to load datafiles (close to 70-80 files). So we decieded to use SSIS packages for load. I don't know (@ least for now) where packages will be?...in file system, sql or ssis storage ? One thing is sure I will have a 60-70 ssis packages and master one that will call all child packages in parallel, may be 4 or 5 at a time. And I am thinking of doing this through table driven. I will keep this topice for later discussion, once i complete all my packages.
Finally, thanks u r alwys a grt help to many out there.......
July 19, 2009 at 9:07 pm
I don't know if I agree with the source control and versioning aspect..
All of our packages are stored in TFS or VSS. Most of them capture the VersionBuild property at runtime and record it. If that changes, there had better be code in source control AND a change control record to match it. You don't lose source control by putting it in the package store AND you now have to back up 2 locations to get all your stuff back instead one one you probably already are, msdb..
CEWII
July 20, 2009 at 9:49 am
Hi All
If i have saved the package in a different folder ( by using save as), the BI Studio points to the package in my personal folder and any changes done will be reflected in that. Now if i accidentally delte it will a copy be available in bin or the Project folder? It there is, will it have all the changes i made?
July 20, 2009 at 9:50 am
forget the above one
i guess i can test it meself txtPost_CommentEmoticon(':-)');
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply