January 8, 2018 at 11:54 pm
My SSDT job is:
OLEDB Source Table: SQL Command, Left Join on Two Tables. Preview works fine.
RowCountSource: Gets row count from left join.
Conditional Split: Checks if there was a match (!ISNULL(KEYS_ID) ). KEYS_ID is in the right table, and will be NULL is there was no match on the natural keys.
Default output name: NoMatch, which is input to the script task. I want the script task to generate messages to the log and throw an error for the entire job.
Script Component: Three input columns: facility_identifier, stay_number, episode_sequence_number, all ReadOnly
Below is the script: Is based on https://stackoverflow.com/questions/18235830/ssis-conditional-split-force-default-path-to-throw-exception
#region Help: Introduction to the Script Component
/* The Script Component allows you to perform virtually any operation that can be accomplished in
* a .Net application within the context of an Integration Services data flow.
*
* Expand the other regions which have "Help" prefixes for examples of specific ways to use
* Integration Services features within this script component. */
#endregion
#region Namespaces
using System;
using System.Collections;
using System.Data;
using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
using Microsoft.SqlServer.Dts.Runtime.Wrapper;
#endregion
/// <summary>
/// This is the class to which to add your code. Do not change the name, attributes, or parent
/// of this class.
/// </summary>
[Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
public class ScriptMain : UserComponent
{
#region Help: Using Integration Services variables and parameters
/* To use a variable in this script, first ensure that the variable has been added to
* either the list contained in the ReadOnlyVariables property or the list contained in
* the ReadWriteVariables property of this script component, according to whether or not your
* code needs to write into the variable. To do so, save this script, close this instance of
* Visual Studio, and update the ReadOnlyVariables and ReadWriteVariables properties in the
* Script Transformation Editor window.
* To use a parameter in this script, follow the same steps. Parameters are always read-only.
*
* Example of reading from a variable or parameter:
* DateTime startTime = Variables.MyStartTime;
*
* Example of writing to a variable:
* Variables.myStringVariable = "new value";
*/
#endregion
#region Help: Using Integration Services Connnection Managers
/* Some types of connection managers can be used in this script component. See the help topic
* "Working with Connection Managers Programatically" for details.
*
* To use a connection manager in this script, first ensure that the connection manager has
* been added to either the list of connection managers on the Connection Managers page of the
* script component editor. To add the connection manager, save this script, close this instance of
* Visual Studio, and add the Connection Manager to the list.
*
* If the component needs to hold a connection open while processing rows, override the
* AcquireConnections and ReleaseConnections methods.
*
* Example of using an ADO.Net connection manager to acquire a SqlConnection:
* object rawConnection = Connections.SalesDB.AcquireConnection(transaction);
* SqlConnection salesDBConn = (SqlConnection)rawConnection;
*
* Example of using a File connection manager to acquire a file path:
* object rawConnection = Connections.Prices_zip.AcquireConnection(transaction);
* string filePath = (string)rawConnection;
*
* Example of releasing a connection manager:
* Connections.SalesDB.ReleaseConnection(rawConnection);
*/
#endregion
#region Help: Firing Integration Services Events
/* This script component can fire events.
*
* Example of firing an error event:
* ComponentMetaData.FireError(10, "Process Values", "Bad value", "", 0, out cancel);
*
* Example of firing an information event:
* ComponentMetaData.FireInformation(10, "Process Values", "Processing has started", "", 0, fireAgain);
*
* Example of firing a warning event:
* ComponentMetaData.FireWarning(10, "Process Values", "No rows were received", "", 0);
*/
#endregion
ArrayList notFound;
/// <summary>
/// This method is called once, before rows begin to be processed in the data flow.
///
/// You can remove this method if you don't need to do anything here.
/// </summary>
public override void PreExecute()
{
base.PreExecute();
notFound = new ArrayList();
}
/// <summary>
/// This method is called after all the rows have passed through this component.
///
/// You can delete this method if you don't need to do anything here.
/// </summary>
public override void PostExecute()
{
base.PostExecute();
foreach (string msg in notFound)
{
ComponentMetaData.FireWarning(0, "Unmatched Keys: ", msg, string.Empty, 0);
}
}
/// <summary>
/// This method is called once for every row that passes through the component from Input0.
///
/// Example of reading a value from a column in the the row:
/// string zipCode = Row.ZipCode
///
/// Example of writing a value to a column in the row:
/// Row.ZipCode = zipCode
/// </summary>
/// <param name="Row">The row that is currently passing through the component</param>
public override void Input0_ProcessInputRow(Input0Buffer Row)
{
string msg = string.Format("{0}:{1}:{2}", Row.facilityidentifier, Row.staynumber, Row.episodesequencenumber);
notFound.Add(msg);
}
}
The script builds fine within the script editor. However, one weirdness is the Intellisense in the script editor shows the input column names as facilityidentifier, staynumber, episodesequencenumber (no underscores). The columns have a "wrench" symbol, and there is also an Intellisense entry for <columnname>_IsNull.
However, when I try to run the job, I get the error Microsoft.SqlServer.Dts.Pipeline.CannotCreateUserComponentException.
Any ideas? Bug in SSDT? Been Googling for hours...
January 9, 2018 at 5:01 pm
Further steps taken:
* Updated SSDT to 17.4
* Updated DacFramework to 17.4
* Installed DotNet Framework 4.7.1
* Installed DotNet Core SDK 2.1.4
* Created a simplified package Package1
* Single Data Flow task
* OLEDB source tiny table
* Conditional split: Column X, NotNull, default output Null. There will never be Null output.
* OLEDB target table same schema as source table
* Target table consumes NotNull output
* Script component consumes Null output
In the script component:
* It's a destination component
* For the script, I just accepted the default script generated. It is a nothing, no-op script.
* Of course, it compiles ok
But still generates the error once I run the package.
Can anyone else confirm this bug in SSDT? Doesn't Microsoft test this?
Is there another approach I can use to fail the entire job if any rows have certain columns that are NULL?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply