Viewing 15 posts - 1 through 15 (of 36 total)
Found a workaround. The package has an "overall success" variable, which is just a combination of all the individual success variables. Consequently I'm now stepping through the Expression of this...
February 9, 2022 at 3:23 pm
Thanks kaj; that did it.
Wasn't needed in "native" C# but clearly was in the Script Task.
February 9, 2022 at 3:01 pm
Dts.Variables[string] is just an array where the string represents the variable's name. Iterating through an array should not be a big deal.
I have variables:
table1_Success, table2_Success, etc.
So all I want is...
February 7, 2022 at 10:49 am
Nice idea. However I use the result of the boolean variable in "Expression and constraint" connections so I'd still need that variable.
It seems strange that there isn't a way to...
February 7, 2022 at 10:21 am
Looks like this was caused by an invalid certificate. No idea what was wrong with it but applying a newly-created certificate worked without issue.
January 18, 2022 at 12:27 pm
Hi Jo.
HTTP works fine and I've configured all my reports, subscriptions, etc. without issue. It's only when trying to enable HTTPS that I hit a problem.
I've also attached a screenshot...
January 14, 2022 at 9:23 am
Did someone modify the SQLAgent service account after the installation of this sqlserver instance ?
Just to verify this, how can I check the membership of the MSSQL$INSTANCENAME group? Can't...
December 6, 2021 at 4:05 pm
Not that I'm aware of. I performed the install and selected the AD account to run the SQL Agent service which is currently the one in use.
December 6, 2021 at 10:57 am
Tim - There's an OnError event handler at the package level but that just does an INSERT into a log table
June 18, 2021 at 7:29 am
Not yet, Phil. I'm gonna collate some data from the [operation_messages] and see if that points me in a direction.
June 17, 2021 at 10:34 am
It shows the "For Loop Container" task.
June 17, 2021 at 10:09 am
The variables in each stack are unique to that stack (they're all named for the stack in which they exist).
June 17, 2021 at 9:57 am
This is failing when the package runs from a SQL Agent job.
I forgot to mention that *most of the time*, it works. We just get this failure occassionally.
June 17, 2021 at 9:55 am
Yeah I've already implemented a workaround in this case but wanted to know for future implementations where this might not be possible.
May 20, 2021 at 3:19 pm
Grrr... Such a simple answer! For some reason I'd set it to 0.
Many thanks.
May 20, 2021 at 8:10 am
Viewing 15 posts - 1 through 15 (of 36 total)