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


Column Names Corrupted


Column Names Corrupted

Author
Message
Joe Faith
Joe Faith
SSC-Enthusiastic
SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)

Group: General Forum Members
Points: 116 Visits: 50
Intermittently we are getting column header names corrupted in the output text file when executing a stored proc from a job in SSIS step. This is 15 yr old process that has only started to fail in a 2008 R2 cluster env.
Note: Actual data is unaffected.
The pseudo proc sql looks something like this:
SELECT 'tableA' as XTABLENAME, count(*) as XCOUNT from schemaA.tableA
SELECT col1
FROM schemaA,tableA
ORDER BY col1

select 'tableB' as XTABLENAME, count(*) as XCOUNT from schemaA.tableB
SELECT col1, col2, col3
FROM schemaA,tableB
ORDER BY col1
...
-------------------end proc----------------------------------------
The job executes
USE msdb
GO
EXEC sp_start_job @job_name = 'xpr_extract'
GO
WAIT FOR DELAY '000:05:00'
-----------------------end job-------------------------------------
--- expected
XTABLENAME XCOUNT
------------- -----------
tableA 1

col1
---------------
123456789012345
XTABLENAME XCOUNT
------------- -----------
tableB 3

col1 col2 col3
--------------- --------------- ----------
123456789012345 000000000000012 0000000001
123456789012345 000000000000012 0000000002
123456789012345 000000000000015 0000000001
---------------------------------end expected----------------------
Columns get corrupted like this; See last table columns:
XTABLENAME XCOUNT
------------- -----------
tableA 1

col1
---------------
123456789012345
XTABLENAME XCOUNT
------------- -----------
tableB 3

col1 _xxx2 x_xxx
--------------- --------------- ----------
123456789012345 000000000000012 0000000001
123456789012345 000000000000012 0000000002
123456789012345 000000000000015 0000000001
Joe Faith
Joe Faith
SSC-Enthusiastic
SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)SSC-Enthusiastic (116 reputation)

Group: General Forum Members
Points: 116 Visits: 50
Could SQL Agent limitations and concurrent re-indexing have bearing on output?
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