Viewing 15 posts - 11,446 through 11,460 (of 13,876 total)
Chrissy321 (5/2/2011)
May 2, 2011 at 1:30 pm
You'll need a hex editor to see the 'invisible' characters.
May 2, 2011 at 12:01 pm
SSIS Guy (5/2/2011)
Here is one more Tool to document ssis packages
Isn't that the same product as suggested by the previous poster?
May 2, 2011 at 11:57 am
smoo (5/2/2011)
With that in mind, we're using an OLE DB...
May 2, 2011 at 9:38 am
Why do you need SSIS if you can do everything you need in T-SQL?
May 2, 2011 at 9:29 am
the problem is not visible in the csv file.
Are you sure? How did you check? What do you want to do with the bad data?
May 2, 2011 at 8:38 am
A couple of ideas spring to mind:
1) Do not use Select *
2) Put a dummy Select near the top of your routine to try and trick SSIS into thinking it...
April 27, 2011 at 1:36 pm
I think you need to put something between the BEGIN and END - not just a comment.
April 27, 2011 at 8:38 am
jpSQLDude (4/26/2011)
April 26, 2011 at 10:31 am
Sri8143 (4/26/2011)
Yes i did it didnt work ..any other suggestions would be helpful...
This works:
DECLARE @CRTEXT VARCHAR(50)
SET @CRTEXT = 'Text ' + CHAR(13) + CHAR(10) + 'more text'
SELECT @CRTEXT, REPLACE(@CRTEXT, CHAR(13)...
April 26, 2011 at 9:04 am
One of my larger concerns here is the prioritization of the suborder within an ID. Unless that's pre-built into the file, this becomes a painful endeavour of conditional logic, and...
April 26, 2011 at 3:25 am
The first thing I'd do is use a hex editor to assure myself that I know exactly what the characters are which need to be replaced.
Then use REPLACE as part...
April 26, 2011 at 2:10 am
Thanks Craig.
I was basing my recommendation on this article which, now that I look at it, is not quite what is required here.
The sample code in the article creates 3...
April 26, 2011 at 2:05 am
LutzM (4/23/2011)
April 23, 2011 at 11:32 am
JStevenson1 (4/22/2011)
April 23, 2011 at 3:00 am
Viewing 15 posts - 11,446 through 11,460 (of 13,876 total)