Ssis package variables not updating

6854933580_2c8b688306_z

The General tab of the Execute SQL Task has the following properties and SQL command – INSERT INTO [dbo].[sysssislog] ([event] ,[computer] ,[operator] ,[ source] ,[sourceid] ,[executionid] ,[starttime] ,[endtime] ,[datacode] ,[databytes] ,[message]) VALUES ('*SSIS-On Variable Value Changed' -- Custom event name ,? In my case, two package scoped variables are handled by a single package level event handler.

The variable value really has to change to fire the event.

To do this, you can use the new features in SQL Server 2012, such as parameters and project-level connection managers, or you can use the package configurations that were first made available in the package deployment model in earlier versions of SQL Server. When you are developing Microsoft SQL Server Integration Services (SSIS) packages, it is a good practice to make each task or transformation as dynamic as possible.

To do this, you can use the new features in SQL Server 2012, such as parameters and project-level connection managers, or you can use the package configurations that were first made available in the package deployment model in earlier versions of SQL Server.The reason is that the initial value of the variable is set to zero in the package. ) -- param 7 Notice that I precede the custom event name with an asterisk to differentiate it from the log entries created by the system.The row count of a brand new empty table is also zero. The On Variable Value Changed event fires only when the value actually changes! The Parameter Mapping tab of the Execute SQL Task has the following properties – Pay attention to the (last variable) in this screen.Log entries created during the execution of an SSIS package help in monitoring, analysis, and issue resolution.In addition to logging events, you might want to capture the run-time values of variables in the package. If you are wondering about the funny prefixes in the object names then you can read about my naming conventions mentioned in my other blog post.Configuration tables are a best practice in just about any SSIS environment.

You must have an account to comment. Please register or login here!