after INSERT fail, make UPDATE guidelines

#1

I think, that I have to do something wrong. In periodicaly running updates,
at the end of the transformation, I usually use OLE DB Destination and if the
INSERT fails (usually because of the PK conflict), row is redirected to the
error output and there the OLE DB Command make UPDATE of this row to the DB.

This technique working well, but!!! -> In the UPDATE command is not possible
use named parameters (I have to use UPDATE myTable SET column1 = ? WHERE
column2 = ?). In case I have tables with a few columns, that is no problem.
But I often transform data tables from the AS400 DB and there are 140 columns
with 8 primary keys and with only 8 characters in the column name. Which
means, it is very unclear (not well arranged). On one side I have columns
from AS400 DB2 named for example GLPMJ, GLGTGF, GLRUID, etc.. on other side
unnamed parameters Param_0, Param_1, Param_3. etc....

My questions are:
1) Is there way to use named parameters in the OLE DB Command?
2) Is there another way to perform update command based on keys in the
destination table??

Thanks alot for the help.

#2

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup.

By design OLE DB does not accept named parameters. However if your intention is to recognize which column for each parameter it represents, you can create a stored procedure in your SQL
Server database. Once you set the SqlCommand text as "exec proc_name ?,?,...", you can find that the Destination Columns are automatically displayed as the parameters names of the
stored procedure. If you create meaningful parameters names for your stored procedure, you can get meaningful parameter names in your OLE DB Command.

So regarding your two questions:
1) Is there way to use named parameters in the OLE DB Command?
Yes, by using a stored procedure.

2) Is there another way to perform update command based on keys in the destination table??
Yes, by using a stored procedure.

Hope this helps. If there is anything unclear, please feel free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

#3

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup.

By design OLE DB does not accept named parameters. However if your intention is to recognize which column for each parameter it represents, you can create a stored procedure in your SQL
Server database. Once you set the SqlCommand text as "exec proc_name ?,?,...", you can find that the Destination Columns are automatically displayed as the parameters names of the
stored procedure. If you create meaningful parameters names for your stored procedure, you can get meaningful parameter names in your OLE DB Command.

So regarding your two questions:
1) Is there way to use named parameters in the OLE DB Command?
Yes, by using a stored procedure.

2) Is there another way to perform update command based on keys in the destination table??
Yes, by using a stored procedure.

Hope this helps. If there is anything unclear, please feel free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

#4

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup.

By design OLE DB does not accept named parameters. However if your intention is to recognize which column for each parameter it represents, you can create a stored procedure in your SQL
Server database. Once you set the SqlCommand text as "exec proc_name ?,?,...", you can find that the Destination Columns are automatically displayed as the parameters names of the
stored procedure. If you create meaningful parameters names for your stored procedure, you can get meaningful parameter names in your OLE DB Command.

So regarding your two questions:
1) Is there way to use named parameters in the OLE DB Command?
Yes, by using a stored procedure.

2) Is there another way to perform update command based on keys in the destination table??
Yes, by using a stored procedure.

Hope this helps. If there is anything unclear, please feel free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

#5

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup.

By design OLE DB does not accept named parameters. However if your intention is to recognize which column for each parameter it represents, you can create a stored procedure in your SQL
Server database. Once you set the SqlCommand text as "exec proc_name ?,?,...", you can find that the Destination Columns are automatically displayed as the parameters names of the
stored procedure. If you create meaningful parameters names for your stored procedure, you can get meaningful parameter names in your OLE DB Command.

So regarding your two questions:
1) Is there way to use named parameters in the OLE DB Command?
Yes, by using a stored procedure.

2) Is there another way to perform update command based on keys in the destination table??
Yes, by using a stored procedure.

Hope this helps. If there is anything unclear, please feel free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

#6

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup.

By design OLE DB does not accept named parameters. However if your intention is to recognize which column for each parameter it represents, you can create a stored procedure in your SQL
Server database. Once you set the SqlCommand text as "exec proc_name ?,?,...", you can find that the Destination Columns are automatically displayed as the parameters names of the
stored procedure. If you create meaningful parameters names for your stored procedure, you can get meaningful parameter names in your OLE DB Command.

So regarding your two questions:
1) Is there way to use named parameters in the OLE DB Command?
Yes, by using a stored procedure.

2) Is there another way to perform update command based on keys in the destination table??
Yes, by using a stored procedure.

Hope this helps. If there is anything unclear, please feel free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

#7

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup.

By design OLE DB does not accept named parameters. However if your intention is to recognize which column for each parameter it represents, you can create a stored procedure in your SQL
Server database. Once you set the SqlCommand text as "exec proc_name ?,?,...", you can find that the Destination Columns are automatically displayed as the parameters names of the
stored procedure. If you create meaningful parameters names for your stored procedure, you can get meaningful parameter names in your OLE DB Command.

So regarding your two questions:
1) Is there way to use named parameters in the OLE DB Command?
Yes, by using a stored procedure.

2) Is there another way to perform update command based on keys in the destination table??
Yes, by using a stored procedure.

Hope this helps. If there is anything unclear, please feel free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

#8

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup.

By design OLE DB does not accept named parameters. However if your intention is to recognize which column for each parameter it represents, you can create a stored procedure in your SQL
Server database. Once you set the SqlCommand text as "exec proc_name ?,?,...", you can find that the Destination Columns are automatically displayed as the parameters names of the
stored procedure. If you create meaningful parameters names for your stored procedure, you can get meaningful parameter names in your OLE DB Command.

So regarding your two questions:
1) Is there way to use named parameters in the OLE DB Command?
Yes, by using a stored procedure.

2) Is there another way to perform update command based on keys in the destination table??
Yes, by using a stored procedure.

Hope this helps. If there is anything unclear, please feel free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

#9

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup.

By design OLE DB does not accept named parameters. However if your intention is to recognize which column for each parameter it represents, you can create a stored procedure in your SQL
Server database. Once you set the SqlCommand text as "exec proc_name ?,?,...", you can find that the Destination Columns are automatically displayed as the parameters names of the
stored procedure. If you create meaningful parameters names for your stored procedure, you can get meaningful parameter names in your OLE DB Command.

So regarding your two questions:
1) Is there way to use named parameters in the OLE DB Command?
Yes, by using a stored procedure.

2) Is there another way to perform update command based on keys in the destination table??
Yes, by using a stored procedure.

Hope this helps. If there is anything unclear, please feel free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

#10

Hi Mike,
What is everything going on regarding this issue? Please feel free to drop me a note at your convenient.

Thank you!

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =======
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======