SQL Server Integration Services (SSIS)
Copied!
Home
Options
1,047
Lingxi on 08-29-2019 10:23 PM
1,335
Jarod_Zhu on 08-08-2019 11:31 PM
1,028
qianwen_shi on 08-06-2019 02:23 AM
3,344
Tim.Chen on 05-14-2019 01:19 AM
2,135
Sandy Winarko on 03-25-2019 04:11 PM
839
SSIS-Team on 03-25-2019 04:10 PM
2,102
Sandy Winarko on 03-25-2019 04:09 PM
823
Sandy Winarko on 03-25-2019 04:08 PM
923
SSIS-Team on 03-25-2019 04:08 PM
601
SSIS-Team on 03-25-2019 04:08 PM
2,103
SSIS-Team on 03-25-2019 04:08 PM
468
SSIS-Team on 03-25-2019 04:08 PM
1,217
SSIS-Team on 03-25-2019 04:08 PM
432
SSIS-Team on 03-25-2019 04:07 PM
805
SSIS-Team on 03-25-2019 04:07 PM
785
SSIS-Team on 03-25-2019 04:07 PM
566
SSIS-Team on 03-25-2019 04:07 PM
393
SSIS-Team on 03-25-2019 04:06 PM
6,753
SSIS-Team on 03-25-2019 04:06 PM
486
Sandy Winarko on 03-25-2019 04:06 PM
440
SSIS-Team on 03-25-2019 04:06 PM
367
SSIS-Team on 03-25-2019 04:05 PM
1,144
SSIS-Team on 03-25-2019 04:05 PM
756
SSIS-Team on 03-25-2019 04:05 PM
387
SSIS-Team on 03-25-2019 04:04 PM
1,683
SSIS-Team on 03-25-2019 04:04 PM
630
SSIS-Team on 03-25-2019 04:03 PM
404
SSIS-Team on 03-25-2019 04:02 PM
Latest Comments
@Zoe_Luo The documentation states that the issue with HRESULT: 0xC0011001 was supposed to be resolved in SSDT version 15.9.2. However, the issue still persists with that version of SSDT.Are there any known work-arounds besides changing the code to remove all expressions? Thanks in advance for any in...
0 Likes
@Zoe_Luo, I've tried tracing both the 32-bit and 64-bit ODBC source administrator. I can't get a trace log file to produce.
0 Likes
@ckallingerAAH , yes, in new SSDT, the icon is changed and should be like:
0 Likes
I am running VS2017 SSDT v15.9.12 on SQL 2017 Integration Services.I have the Oracle Client and the Microsoft Connector Version 5.0 for Oracle by Attunity targeting SQL Server 2017 both installed.Should I be seeing see the red Icon like I did in prior version for SQL 2012?In SQL 2017 with SSDT v015....
0 Likes
@ctrembea , you mentioned that the connection only fails when executing the package, right? In this case, it is not the LDAP support issue. Then package targeting to SQL2016, Attunity connector will be used at runtime. So it must be Attunity connector required environment is not set correctly. Can y...
0 Likes