Dynamic Properties Task
-
I have 59 file paths i am reading from a table called dts_config. It works great. The same dts package when moved to different server dont populate all the filepath unless i go in manually and execute the Dynamic Task, Once i execute it it will pick up all the new parameter from the dts_config table.
I added the dynamic task at the end does this makes a differnce?
I do have on success work flow for Dynamic Properties Task to execute the next task?
My Assumption is that the 'Dynamic Properties Task' is not getting executed in the begining of the DTS package
Any suggestion, tips are greatly appreciate, THANKS
-
Yes, it matters where you put it. I generally put it first.
My blog: SQL Soldier[/url]
SQL Server Best Practices: SQL Server Best Practices
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring[/url]
Microsoft Certified Master: SQL Server, Data Platform MVP
Database Engineer at BlueMountain Capital Management[/url] -
You can put the DP task where you want depending on what you want but the "mission" of the Dynamic Properties task is to be able to change at the run time properties of connections like datasource, catalog, etc. Usually you need this at the beginning of the dts package so that you "tell" it what datasource (server) and catalog (database) to use. I don't see any reason to put Dynamic Porperties at the end when doesn't really matter how you change those properties as long as they will never be used.
Don't just give the hungry man a fish, teach him how to catch it as well.
the sqlist
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply