SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Ideas on resolving error -- "VS_NEEDSNEWMETADATA".


Ideas on resolving error -- "VS_NEEDSNEWMETADATA".

Author
Message
Mark F-428640
Mark F-428640
Mr or Mrs. 500
Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)

Group: General Forum Members
Points: 586 Visits: 578
Hi I am running a large dtsx package and in a data flow task I am getting the following error in the validation of the OLE DB DESTINATION object. Here is the specific error:

[DTS.Pipeline] Error: "component "My_Data reader destination" (337)" failed validation and returned validation status "VS_NEEDSNEWMETADATA".

Not sure where I should look from here I have looked at my source data and the data types and sizes are compatible with the destination.

I welcome any suggestions.
pduplessis-723389
pduplessis-723389
SSCrazy
SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)

Group: General Forum Members
Points: 2369 Visits: 400
This normally occurs if there has been a change to your schema, not to stress, just double click on your input and output and it should resolve itself
Mark F-428640
Mark F-428640
Mr or Mrs. 500
Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)Mr or Mrs. 500 (586 reputation)

Group: General Forum Members
Points: 586 Visits: 578
Thanks,
Sanjay Rohra
Sanjay Rohra
Say Hey Kid
Say Hey Kid (661 reputation)Say Hey Kid (661 reputation)Say Hey Kid (661 reputation)Say Hey Kid (661 reputation)Say Hey Kid (661 reputation)Say Hey Kid (661 reputation)Say Hey Kid (661 reputation)Say Hey Kid (661 reputation)

Group: General Forum Members
Points: 661 Visits: 307
I was facing the similar issue. In my case, I was creating the SQL query on run time using script task, storing it in a variable. The default value that I had provided to my variable , one of the column names had the first character in Upper case. But in the script task, while designing the query, the same column had the first character in Lower case. On changing the latter to Upper case solved my problem. Quite strange, but it worked for me.

HTH

Sanjay.
rsingh.sql
rsingh.sql
Old Hand
Old Hand (340 reputation)Old Hand (340 reputation)Old Hand (340 reputation)Old Hand (340 reputation)Old Hand (340 reputation)Old Hand (340 reputation)Old Hand (340 reputation)Old Hand (340 reputation)

Group: General Forum Members
Points: 340 Visits: 177
I am getting the same error message, I have an OLE DB source that gets a set of columns from a variable that executes a given stored proc.
The data flow task can be individually executed successfully, but if I run the job or the package, it is giving me the error "Description: "component "OLE DB Source" (1)" failed validation and returned validation status "VS_NEEDSNEWMETADATA" ".

Any advise is appreciated.

Things I have tried:
1: remove OLE DB source and destinations and re create it.
2. remove the entire data flow task itself and recreate it.
SQListic
SQListic
SSC Eights!
SSC Eights! (984 reputation)SSC Eights! (984 reputation)SSC Eights! (984 reputation)SSC Eights! (984 reputation)SSC Eights! (984 reputation)SSC Eights! (984 reputation)SSC Eights! (984 reputation)SSC Eights! (984 reputation)

Group: General Forum Members
Points: 984 Visits: 1115
Help on this please, I am having similar issue.
Phil Parkin
Phil Parkin
SSC-Dedicated
SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)

Group: General Forum Members
Points: 35731 Visits: 20891
SQListic (10/21/2013)
Help on this please, I am having similar issue.


What have you tried?


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
herladygeekedness
herladygeekedness
SSC Eights!
SSC Eights! (910 reputation)SSC Eights! (910 reputation)SSC Eights! (910 reputation)SSC Eights! (910 reputation)SSC Eights! (910 reputation)SSC Eights! (910 reputation)SSC Eights! (910 reputation)SSC Eights! (910 reputation)

Group: General Forum Members
Points: 910 Visits: 813
try setting DelayValidation to True.
l.bissett
l.bissett
Grasshopper
Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)

Group: General Forum Members
Points: 13 Visits: 10
I have a project that has been running fine for a long time. Recently however I had to change the password to my AS400 ODBC connection string. I had a problem doing this so I ended up deleting the connection configuration XML file and creating it again. I think this cause a problem in my package. Now I am getting a metadata error. Is there something else I have to do once I change the connection?
Satu
Satu
SSC Journeyman
SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)

Group: General Forum Members
Points: 85 Visits: 18
I have always managed to get rid of metadata errors simply by running the project in BIDS step by step. When all previous steps have been executed, open the input and output steps, accept any (sensible) notifications on changes needed, and press OK. BIDS will most of the time detect what has changed in data source.
Using a stored procedure as a data source, though, might be a different story altogether.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search