Viewing 15 posts - 31 through 45 (of 72 total)
February 8, 2018 at 2:18 am
February 7, 2018 at 9:37 am
February 7, 2018 at 7:36 am
I highly suspect this issue has something to do with account permissions via Visual...
February 6, 2018 at 6:49 am
February 6, 2018 at 6:44 am
Having recently converted a package to use the ACE drivers instead of JET to export to Excel, you need to ensure you install the 32bit version of the ACE drivers...
December 18, 2017 at 9:32 am
I believe, with result sets, only appeared from SQL 2012 onward to address the issue of using CTE's and getting similar problems to what you are experiencing. See here for...
May 3, 2017 at 6:51 am
Provided the source column was compatible your output field in the Flat File Connection Manager could be text stream[DT_TEXT]
May 3, 2017 at 6:38 am
Okay, I found the issue. It was an error in the Agent Job configuration. The SSISDB server name property was pointing to the wrong server. That's what you get for...
April 11, 2017 at 9:09 am
I inherited a similar problem with SQL 2008, however it was a unique scenario that may not apply to you. There where approximately 320 tables where data was loaded to...
April 10, 2017 at 8:17 am
In my last DBA job we designed an SSIS 2012 solution that contained 530 packages that used project deployment. All of these packages ran every night to reload tables from...
March 30, 2017 at 5:08 am
It looks like you have a bit of a mystery on you hands. As all of the tasks are contained in the For Loop setting FailParent will not help in...
March 29, 2017 at 2:24 am
Does the Error workflow attach from the OLAP Task or the For Loop? If it attaches from the For Loop make sure Fail Parent is set in the properties of...
March 28, 2017 at 3:03 am
Swap to project deployment with different server configurations, it's so much easier.
March 28, 2017 at 2:47 am
Viewing 15 posts - 31 through 45 (of 72 total)