April 16, 2014 at 3:10 pm
Can you add it to your post as an attachment instead of embedded into the post? All I can see is a place holder and I've used 2 different computers and 2 different browsers.
April 16, 2014 at 3:12 pm
Error msg say " The data type for input column "Copy of XML_f52e2b61-18a1"(330)" is DT_NTEXT.
When I change encoding to unicode and the data type DT_NTEXT to that this is what I'm getting. I am making the change in connection manager.
none?PLastName?PFirstName?
????????????????????????????????????
April 16, 2014 at 3:14 pm
attach is a screen shot
April 16, 2014 at 3:16 pm
kbnyny (4/16/2014)
Error msg say " The data type for input column "Copy of XML_f52e2b61-18a1"(330)" is DT_NTEXT.When I change encoding to unicode and the data type DT_NTEXT to that this is what I'm getting. I am making the change in connection manager.
none?PLastName?PFirstName?
????????????????????????????????????
The error is probably a bit longer that just that.
Check the error window to find the full error.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 16, 2014 at 3:25 pm
kbnyny (4/16/2014)
Error msg say " The data type for input column "Copy of XML_f52e2b61-18a1"(330)" is DT_NTEXT.When I change encoding to unicode and the data type DT_NTEXT to that this is what I'm getting. I am making the change in connection manager.
Did you refresh the flat file destination metadata after making the change in the connection manager?
April 16, 2014 at 3:41 pm
yes I refresh the flat file destination metadata
April 17, 2014 at 12:21 am
kbnyny (4/16/2014)
yes I refresh the flat file destination metadata
Did you look for the full error?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 17, 2014 at 4:47 am
I am trying to replicate this in my environment, using my own tables. Can you post the set up of the flat file connection manager (General and Advanced tabs)?
You can obfuscate the names, just make sure the data types, column properties, and all the formatting information are the same.
Are you saving to a file that ends in ".xml" or does it end in ".txt" or ".csv"? (Your screen shot has 2 flat file connection managers, I want to make sure which one the flat file destination is using).
And do you absolutely need the BINARY BASE64 definition in your XML? That's very specific to making your XML results return a base 64 binary format. That is probably the source of the datatype change errors. Does your code retrieve binary, varbinary, or image datatypes from the database?
April 17, 2014 at 5:15 am
Hmm. I'm not able to replicate the strange character pattern on my flat file. It comes out as all binary. And when changing datatypes in the connection manager, I appear to have no issue.
It originally saved as DT_IMAGE instead of DT_NTEXT and still the package ran fine. I flipped to DT_NTEXT, updated the flat file destination, no issues. Which is the opposite of what you're working with, but I was still able to change the datatype.
What datatype are you trying to change from DT_NTEXT to?
April 17, 2014 at 7:34 am
There is no error msg. The package runs just not getting the output that I'm suppose to get. I am getting funny looking characters.
April 17, 2014 at 7:38 am
I was changing the datatype to see if I get a different output when I run the package. Currently when I run it with DT_NTEXT and that is the only datatype I am able to run the package in. If I try and change the datatype to anything other than DT_NTEXT I get the RED X.
April 17, 2014 at 7:44 am
kbnyny (4/17/2014)
I was changing the datatype to see if I get a different output when I run the package. Currently when I run it with DT_NTEXT and that is the only datatype I am able to run the package in. If I try and change the datatype to anything other than DT_NTEXT I get the RED X.
A red X means an error. The question is: "which error"?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 17, 2014 at 8:25 am
Brandie here is a screen shot that you requested.
April 17, 2014 at 8:26 am
Brandie when I took out he Binary Base64 I still get the same funny character on the XML output file.
April 17, 2014 at 8:50 am
kbnyny (4/17/2014)
Brandie when I took out he Binary Base64 I still get the same funny character on the XML output file.
Can you give us a DDL for the table and some sample data to insert?
As Koen said, if you're getting a red X, then you're getting an error. You should be able to go to View -> Error List in the BIDS menu to pop up the Error window. That's the text we need. There is always information there if you have a red X or yellow Warning. We need everything listed in that window.
Viewing 15 posts - 16 through 30 (of 31 total)
You must be logged in to reply to this topic. Login to reply