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 |
|
MarkyBoy666
Starting Member
14 Posts |
 Posted - 2006-04-24 : 07:50:51
|
I was wondering if anyone could possibly confirm for me that I understand the comcept of binding tables in DDQ's, as I admit I'm slightly (but not totally) confused.  I have 2 DDQ's, one to transfer data from some columns of my one source file (a csv) into 'table 1', and another DDQ to transfer other columns from the same csv into a separate table, 'table 2'. Now, the first DDQ is OK. However, in the second DDQ, my update query refers to a source csv column (in the query's WHERE clause) that doesn't have a direct corresponding column in table 2. (Table 2 here is my binding table.) In order to 'reference' the source column, I'm having to basically map that source column to a column in the binding 'version' of table 2 (a column that I'm not 'using' in this DDQ), so that I can use it in the Parameters list. In other words, I'm mapping it to a column of a different name that has no real relevance to it, but is redundant for this particular query/transformation. Is this the correct way to do this? i.e. although the binding table used is originally a real destination table, in its inding 'capacity' it's only actually used as a way of mapping and referencing source columns, and in actual fact bears no relevance to any data transformations (i.e. this 'mapping' doesn't actually alter data in the destination column - only my QUERY can does this, in which the destination table itself is used as a real query destination table, rather than as the binding table). I'd be grateful if someone could set my mind at ease and clarify that I've got this right in my head! Many thanks. |
|
|
|
|
|
|
|
Data Driven Query Task - understanding binding