Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Ravi0435
Starting Member
47 Posts |
 Posted - 2010-03-11 : 14:47:12
|
| Hi:After we develop the SSIS packages, builid them and run them...when they are ready we move them ( Just the .dtsx file) to Version Control tool from where they are pulled to move to the production, in producion they run fine ...but if some other developer wants to work on the SAME package later and extracts it from Version Control tool, he is unable to see the SQL query insided the OLEDB Source ( inside the dataflow task - if there is a query instead of table to table mapping). What is the solution for this....how wil the next developer understand what query was inside the OLEDB source task ? I think they run fine because they are built successfully and are kind of compiled and stay in the background of the package.1. Ho to figure out the source query with the above process.2. If different process needs to be followed for checking in to the Version Contol, please explain how.Any suggestion would be appreciated.Thanks,RaviNothing much that i can do..!! |
|
|
Ravi0435
Starting Member
47 Posts |
Posted - 2010-03-12 : 11:32:09
|
| I found something ......inside the Dataflow Task ....for the version controled package when you double click the OLEDB datasource the Sql command box wil be empty - that was the concern ......but itstead of double clicking to see whats the SQL Query ... right click the OLEDB source....and see the properties....in the properties pane....you will see SqlCommand and you can find the SQL there.Thanks,RaviNothing much that i can do..!! |
 |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-03-12 : 11:44:40
|
Thank you for coming back and posting the solution
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
|
|
|
SSIS Packages Version Control