December 13, 2011 at 5:30 am
Create a table, flat file, whatever you want.
Put error handling on the component that you want to monitor. Create a destination for your table, flat file whatever. Draw a red line from your component to the destination.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
December 13, 2011 at 5:44 am
Koen Verbeeck (12/13/2011)
Create a table, flat file, whatever you want.Put error handling on the component that you want to monitor. Create a destination for your table, flat file whatever. Draw a red line from your component to the destination.
i am not making you clear..its my mistake...sorry about that
my need is...i create a dynamic package on my machine and i am going to execute the package onto the client machine with their data's....if i get error, the error details must be inside the logging (i create a separate .csv files for that)...so i am able to get columns and tables...but not able to get which exact rows getting wrong...
i hope you understand me now...:ermm:
Thanks,
Charmer
December 13, 2011 at 5:53 am
Read this article, it has pictures, maybe that helps.
http://msdn.microsoft.com/en-us/library/ms141679.aspx
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
December 13, 2011 at 6:05 am
Koen Verbeeck (12/13/2011)
Read this article, it has pictures, maybe that helps.
i understood that you fell sick of me...that's why you mentioned like "it has pictures"...sorry buddy...i have been telling you that i don't want inside the data flow...like redirecting error rows to a flat file or something......any way..thank you so much for your patience and your timely help...i'l be only having the UI onto the client machine..so how am i supposed to redirect errors...? i can't...
Thanks,
Charmer
December 13, 2011 at 6:20 am
Charmer (12/13/2011)
Koen Verbeeck (12/13/2011)
Read this article, it has pictures, maybe that helps.i understood that you fell sick of me...that's why you mentioned like "it has pictures"...sorry buddy...i have been telling you that i don't want inside the data flow...like redirecting error rows to a flat file or something......any way..thank you so much for your patience and your timely help...i'l be only having the UI onto the client machine..so how am i supposed to redirect errors...? i can't...
What do you mean with you will only be having the UI at the client?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
December 13, 2011 at 6:24 am
Koen Verbeeck (12/13/2011)
Charmer (12/13/2011)
Koen Verbeeck (12/13/2011)
Read this article, it has pictures, maybe that helps.i understood that you fell sick of me...that's why you mentioned like "it has pictures"...sorry buddy...i have been telling you that i don't want inside the data flow...like redirecting error rows to a flat file or something......any way..thank you so much for your patience and your timely help...i'l be only having the UI onto the client machine..so how am i supposed to redirect errors...? i can't...
What do you mean with you will only be having the UI at the client?
sorry , i mean the package utility.....
Thanks,
Charmer
December 13, 2011 at 6:26 am
But you will be developing the package itself, right?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
December 13, 2011 at 6:36 am
Koen Verbeeck (12/13/2011)
But you will be developing the package itself, right?
then we need to redirect row for each and every column right..? because i am not aware of data's i mean only the rows not columns..and tables.. i feel redirecting does not look fair..that's why i need some log details in case error arrives...
is it the only way to get error rows....?
Thanks,
Charmer
December 13, 2011 at 6:54 am
It is the only way.
You redirect all the rows that generate an error to an output. Include the ErrorCode and the ErrorColumn with it and with some scripting, also the ErrorDescription.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
December 13, 2011 at 7:01 am
Koen Verbeeck (12/13/2011)
It is the only way.You redirect all the rows that generate an error to an output. Include the ErrorCode and the ErrorColumn with it and with some scripting, also the ErrorDescription.
thank you so much buddy....i didn't full fill my needs..but i came to know that what are all the non possibilities in logging...thanks pal...
Thanks,
Charmer
December 13, 2011 at 7:35 am
I get lost when you are talking about executing on a client pc. All of our SSIS packages execute at server level. Are you creating a client utility to run the package on a non-SQL box?
December 13, 2011 at 7:42 am
herladygeekedness (12/13/2011)
I get lost when you are talking about executing on a client pc. All of our SSIS packages execute at server level. Are you creating a client utility to run the package on a non-SQL box?
no...not like that..
Thanks,
Charmer
Viewing 12 posts - 16 through 26 (of 26 total)
You must be logged in to reply to this topic. Login to reply