January 5, 2015 at 9:16 am
To me, the whole ssis/variable/data transformation route is hugely over-complicated it. SSIS tasks shouldn't be used to replicate basic SQL functions.
Just use an Execute SQL task and refer to the sql Char() function.
I.E., to get: "555" you would use Char(34) + '555' + Char(34)
January 5, 2015 at 12:04 pm
ipisors (1/5/2015)
To me, the whole ssis/variable/data transformation route is hugely over-complicated it. SSIS tasks shouldn't be used to replicate basic SQL functions.Just use an Execute SQL task and refer to the sql Char() function.
I.E., to get: "555" you would use Char(34) + '555' + Char(34)
Adding quotes to text when exporting to text files is just a setting in the connection manager. No need for extra SQL Tasks.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 5, 2015 at 12:07 pm
I see the former as reinventing the wheel rather than the latter, but I can see reasonable people on either side.
Incidentally, a lot of stuff in SSIS can be used as a crutch as opposed to bringing in the most final/discrete dataset from the initial SQL pull. Same thing can be done with Crystal Reports, but my preference is to get the job done as best as possible in the initial data pull.
There are numerous reasons for this, but one relevant one that comes to mind at this moment is ease of being found by another developer.
I hate going into an application and looking in 16 different places to find out why something is happening, when all 16 of them could have been done in a single place..
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply