Hi all, I'm writing an ETL process that should execute in the Load operation some INSERTS towards relational databases (that could be Sql Server, DB2, Oracle, or what else). I simply use and OutputCommandOperation for this. The INSERT statements are quite simple and "standard" in their syntax, but could affect a lot of columns in a single table (in the order of a number of columns beetween 10 and 100).
Sometimes, during the development and testing of these systems, can happen that some value is not correctly managed by the destination database, e.g. a string value is longer than the supported length of the columns, a data type doesn't correspond, etc... In these situations, the errors raised from the database could be quite "generic", e.g. the infamous "String or binary data would be truncated" of Sql Server that doesn't signal which is the column that causes the problem. In some situations we could use a profiler, such as the one of Sql Server, and see which is the offending INSERT statement, and from there we can try to detect the offending column, but this is not always an applicable and efficient strategy. In situations like this one, does RhinoEtl provide some kind of support for diagnostic, or can you suggest some steps to detect in an easier way the problem? -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To view this discussion on the web visit https://groups.google.com/d/msg/rhino-tools-dev/-/TSUjx41RwqEJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
