SSIS Package, Use Datepicker control in VB script task

Dim dateTimePicker1 As New DateTimePicker()
Controls.AddRange(New Control() {dateTimePicker1})
MessageBox.Show(dateTimePicker1.Value.ToString())
dateTimePicker1.Value = DateTime.Now.AddDays(1)
MessageBox.Show(dateTimePicker1.Value.ToString())
In an SSIS package, 2008r2....   I trying to add a messagebox to a script task that contains a datepicker control. 
I will pass the date to a variable then stored procedure.  The code above almost works except I get "Name Controls not declared".  I am using
System.Windows.Forms. 
Anyone know how to correct?
Thanks,
MIke

Nope
You cant have forms etc added to script task inside SSIS and make it interactive
If your intention is to pass a value from outside you need to make use of configurations or use command line arguments with utilities like dtexec.
http://www.bidn.com/blogs/DevinKnight/ssis/1655/passing-values-into-an-ssis-package-at-runtime-from-outside-the-package
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Similar Messages

  • When migrating ssis packages from 2005 to 2012 Activex Script Task component doesn't exist in 2012 version

    Hello,
    We are migrating the ssis packages from 2005 to 2012.
    I'm unable to convert Activex Script Task from 2005 vesrsion to 2012 because in 2012 version Activex Script Task doesn't exist.
    Can anyone please let me know what is the alternative way to convert Activex Script Task from 2005 vesrsion to 2012?

    Hi Vinay9738,
    Have you tried to upgrade the SSIS 2005 packages to SSIS 2012 packages by using the SSIS Package Upgrade wizard? In certain cases, ActiveX script in SSIS won’t work and we need to either modify the script or replace the ActiveX Script with stock SSIS
    tasks. You can find the mapping between some most common patterns used in DTS ActiveX Script and SSIS native tasks from the following link:
    http://help.pragmaticworks.com/dtsxchange/scr/ActiveX%20Script%20Task.htm
    Here is also a useful link about how to convert ADODB object of ActiveX Script to SSIS tasks:
    http://help.pragmaticworks.com/dtsxchange/scr/FAQ%20-%20How%20to%20convert%20ADODB%20object%20of%20ActiveX%20Script%20to%20native%20SSIS%20Task.htm
    Regards,
    Mike Yin
    TechNet Community Support

  • SSIS PACKAGE MIGRATION FROM 2005 to 2008 - Script task/component errors

    HI All,
    We have to migrate ssis packages (about 300) from ssis 2005 to 2008 .
    1. I understand that the major concern is regarding the script component/tasks.
    I searched a lot about this and also consulted with many friends , all of them are aware of this issue but not able to provide what could be the issues and the solution.
    Can some one help me with the common script issues that can happen during migration and the solution for the same.
     2. I do have one more question.
    As per my understanding given in the below link 
    http://blogs.msdn.com/b/mattm/archive/2008/03/21/package-upgrade-wizard.aspx
    there is this part which says ... 
    Once the packages have been chosen, the next page asks you to pick the output location. This can be:
    Same as the source location
    File System
    SSIS Service (Package Store)
    SQL Server 
    Does this mean I can deploy in sql server directly on fly while upgrading ?
    Any help highly appreciated .
    Regards
    Praveen..

    Hi Praveen,
    Question 1: The error may occur if there are duplicate input columns in the Script Task/Component or the current user cannot access the C:\Windows\Temp directory. Except for the link provided by SanBhaumik, you can also refer to the following
    threads:
    http://www.sqlservercentral.com/Forums/Topic811208-148-1.aspx 
    http://social.technet.microsoft.com/Forums/sqlserver/en-US/5c11eb57-59d6-4f81-bfdc-13bd6489a0ac/sql-server-2008-ssis-package-script-component-error?forum=sqlintegrationservices 
    Question 2: We can directly save the package to the File System, SSIS Package Store, or SQL Server by selecting the proper destination during the package upgrade. However, this operation is not equal to the package install operation identically.
    For example, if we have enabled package configurations for a package, the package configurations won’t be upgraded or installed during the package upgrade.
    Regards,
    Mike Yin
    TechNet Community Support

  • How to use print control in Sap script

    I would like to use print control in Sap script.Actualy my problem I have security font Troy ECF. Using this font I would like to print amount field in Check printing.
    we count download this font with sap .we talked to customer care they told we should hard code in sapscript. pls can any1 help on this how to do and how to use print control for this fonts.

    call this funcation. crate_text.
    CALL FUNCTION 'CREATE_TEXT'
             EXPORTING
               FID               =
               FLANGUAGE         =
               FNAME             =
               FOBJECT           =
             SAVE_DIRECT       = 'X'
             FFORMAT           = '*'
             TABLES
               FLINES            =
           EXCEPTIONS
             NO_INIT           = 1
             NO_SAVE           = 2
             OTHERS            = 3
           IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
           ENDIF.

  • Execute SSIS Package from JOB which contains Execute Process Task calling a .bat file

    Hi All,
    I have a EXCEL Macro needs to be called from SSIS. We could not use Script task because of some internal reason.
    So we have taken an approach to call a .BAT file using Execute Process Task. This .BAT file will call a .VBS file which will execute the EXCEL Macro.
    The SSIS Package is running good if I execute the package from BIDS.
    But the real problem is with the scheduling this SSIS Package using SQL JOB.
    If i execute this SSIS package from SQL Server Job, its executing the whole package successfully except the Execute Process Task.
    So the overall issue is SQL Server Job is not executing properly if I call any .BAT file from the SSIS Package.
    Please give me suggestion to get rid of the issue. Thanks in advance.

    Hi Sai.N,
    If you run the SQL Server Agent job manually from SSMS, does the package execute properly? If the package executes properly when you run the job manually, the issue should occur due to permission issue. In this case, I suggest that you create a SQL Server
    Agent proxy based on the current Windows account which you use to log onto the operating system, and run the job under the proxy account.
    If it is not the issue, please enable logging in the package as Visakh mentioned and post the warning/error message for further analysis.
    Regards,
    Mike Yin
    TechNet Community Support

  • How to Schedule Job using Database Control for SQLPLUS script?

    Hi All,
    I am using Database version 10.2. I would like to schedule a SQLPLUS script job using Database control (Not using Grid Control!). The following is the script.
    ========================================================
    define OEM_FRIENDLY=1
    define OWB_BACKGROUND=0
    set serveroutput on
    set verify off
    whenever sqlerror exit failure;
    define REPOS_OWNER='&1.'
    define LOCATION_NAME='&2.'
    define TASK_TYPE='&3.'
    define TASK_NAME='&4.'
    define SYSTEM_PARAMS='&5.'
    define CUSTOM_PARAMS='&6.'
    alter session set current_schema = &REPOS_OWNER.;
    set role owb_d_&REPOS_OWNER., owb_o_&REPOS_OWNER.;
    variable exec_return_code number;
    begin
    -- Initialize Return Code
    :exec_return_code := wb_rt_api_exec.RESULT_FAILURE;
    -- Run Task
    :exec_return_code := wb_rt_api_exec.run_task('&LOCATION_NAME.',
    '&TASK_TYPE.',
    '&TASK_NAME.',
    '&CUSTOM_PARAMS.',
    '&SYSTEM_PARAMS.',
    &OEM_FRIENDLY.,
    &OWB_BACKGROUND.);
    end;
    exit :exec_return_code;
    ===========================================================
    Is it possible to schedule SQLPLUS script with 6 different parameters? If yes then how can I schedule for monday to friday or only for Saturday and sundays.
    Please provide brief steps.
    Thanks for your help in advance.
    - Mehul

    Let me explain to you about scheduler.
    You can schedule a pl/sql stored procedure TEST_S as follows...
    Begin
    dbms_scheduler.create_job(
    job_name=>'MY_JOB',
    Job_Type=>'STORED_PROCEDURE',
    job_action=>'TEST_S',
    start_date=>sysdate,
    repeat_interval=>'freq=monthly;BYDAY=MON,TUE,WED,THU,FRI',
    end_date=>null');
    END;
    You can also also execute o/s script like .bat or .sh. For this job type should be EXECUTABLE.
    Example of converting a .sql script in .bat script...
    insert.sql
    insert into dept values(50,'IT','LONDON');
    exit
    insert.bat
    sqlplus scott/tiger @insert.sql
    Executing now...
    C:\Documents and Settings>insert.bat
    C:\Documents and Settings>sqlplus scott/tiger @insert.sql
    SQL*Plus: Release 10.2.0.1.0 - Production on Thu Mar 1 08:01:00 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    1 row created.
    Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - P
    oduction
    With the Partitioning, OLAP and Data Mining options
    C:\Documents and Settings>
    So first read about DBMS_SCHEDULER and do the work in prompt. Then you can go and schedule it even by database control.
    Scheduling by database control...
    http://www.oracle.com/technology/oramag/oracle/04-jul/o44tech_dba.html
    Scheduler
    http://download-uk.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_sched.htm#CIHEHDHA
    PS: By default each job you created is disable state. Please enable it by enable procedure of DBMS_SCHEDULER package.

  • Running multiple SSIS packages using SQL Server Agent question.

    I have a multitude of SSIS packages I want to run using SQL Server Agent.  What would the best practice be for running these jobs using SQL Server Agent?  One job per package or running all pakages from one job?  If you have an answer can
    you explain the technical reasoning behind your answer?  Thanks in advance.
    Stan Benner

    Hi, maybe a bit more analysis will give a better answer
    Do all the packages have to run in sequence? (if yes, single job better)
    Can the list of packages to be executed be grouped by dependency (ex package 1,2 and 5 must run in sequence and can be executed by one job, while package 3,4 are not dependent on package 1,2 and 5 can be run by a separate job).
    Can any jobs be run in parallel?
    How often will the package execution sequence change?
    How will you deploy your packages and job? (the more jobs to create the more install script needed and upgrade scenarios become messy).
    My personal preference:
    I create ONE ssis package which is executed by ONE sql agent job. lets call this 'PackageExecutionWrapper.dtsx'
    PackageExectionWrapper then contains multiple 'Execute Package' tasks for the packages you want to execute.
    In the package you can apply any package execution rules - which packages have to run after the other, which packages can run concurrently, which packages should only run if previous succeeded.
    If you need to change the sequence, simple, just update the PackageExecutionWrapper package.

  • Executing SSIS Package using C# problem

    Hey,
    I developed an WinForms App and SSIS package which I want to run using this App.\
    I'm using folliwng script to run it:
    using Microsoft.SqlServer.Dts.Runtime; class PackageExecutor
    public string PackageFolder = ConfigurationManager.AppSettings["PackageFolder"];
    Logger _logger = new Logger();
    public void ExecutePackage(string location, string packagename)
    Package pckg;
    Microsoft.SqlServer.Dts.Runtime.Application app;
    DTSExecResult pckgResult;
    Variables vars;
    app = new Microsoft.SqlServer.Dts.Runtime.Application();
    pckg = app.LoadPackage(location, null);
    vars = pckg.Variables;
    vars["User::PckgConnection"].Value = ConfigurationManager.ConnectionStrings["SSIS"].ConnectionString;
    pckgResult = pckg.Execute(null, vars, null, null, null);
    if (pckgResult == DTSExecResult.Success)
    MessageBox.Show("Wykonano poprawnie");
    string msg = DateTime.Now.ToString() + " " + ExtensionMethods.LoginData.strUserName + " " + packagename + " Success";
    _logger.WritePackageLog(msg);
    else
    string err = "";
    foreach (Microsoft.SqlServer.Dts.Runtime.DtsError local_DtsError in pckg.Errors)
    string error = local_DtsError.Description.ToString();
    err = err + error;
    MessageBox.Show("Wystąpił błąd więcej informacji w logu.");
    string msg = DateTime.Now.ToString() + " " + ExtensionMethods.LoginData.strUserName + " " + packagename + " Failure with error: " + err;
    _logger.WritePackageLog(msg);
    This one works perfectly on my PC which have SSIS installed, however a client is reciving an error:
    "An Integration Services class cannot be found. Make sure that Integration Services is correctly installed on the computer that is running the application. Also, make sure that the 64-bit version of Integration Services is installed if you are running
    a 64-bit application".
    Inside SSIS project I turned of "Run64BitRuntime".
    I'm running on x64 bit windows with x32 SSIS installed, can't tell on what Windows (x32/x64) is client running. I can get that info if necessary.
    Any idea how may I solve this? Point of everything was to run SSIS package placed on server on any machine without installing any additional software there.

    You needed to do proof of concept before embarking on this design. There is no workaround, and each client needs to have a paid SQL Server license in this case
    Arthur
    MyBlog
    Twitter

  • Unable to run SSIS Package using Stored Procedure

    Hi Guys,
            I have create one simple SSIS Package(Move the first table record to second table).It will execute fine in locally.
    But, If i'm going call/execute .dtsx file using stored procedure. I'm getting Error. so please let me know the valuable solution.
    My Package Path : D:\Temp\SSIS_TESTING\TESTSSIS\TESTSSIS\Package.dtsx
    Stored Procedure
    ================
    CREATE PROCEDURE SPEXECUTESSISPACKAGE
    @FILEPATH VARCHAR(8000)
    ,@STATUS VARCHAR(500) = NULL OUTPUT
    AS
    BEGIN
    DECLARE @SQLQUERY VARCHAR(8000)
    DECLARE @STATUSCODE INT
    SET @SQLQUERY = 'DTEXEC /FILE "'+ @FILEPATH +'"'
    SELECT @SQLQUERY AS 'SSIS FULL PATH'
    EXEC @STATUSCODE = master..xp_cmdshell @SQLQUERY
    SELECT @STATUSCODE AS 'STATUSCODE'
    IF @STATUSCODE <> 0
    BEGIN
    SET @STATUS = 'PACAKGE EXECUTE FAILED'
    PRINT @STATUS
    END
    ELSE
    BEGIN
    SET @STATUS = 'PACAKGE EXECUTE SUCCESS'
    PRINT @STATUS
    END
    END
    GO
    RUN
    ============================================================================
    EXEC SPEXECUTESSISPACKAGE 'D:\Temp\SSIS_TESTING\TESTSSIS\TESTSSIS\Package.dtsx', NULL
    Error
    =============================================================================
    Microsoft (R) SQL Server Execute Package Utility
    Version 9.00.4035.00 for 32-bit
    Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
    NULL
    Started:  5:06:26 AM
    Error: 2014-11-14 05:06:26.07
       Code: 0xC0011007
       Source: {1244CD18-F96A-4DAD-8FC2-35F794015CA1}
       Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted.
    End Error
    Error: 2014-11-14 05:06:26.07
       Code: 0xC0011002
       Source: {1244CD18-F96A-4DAD-8FC2-35F794015CA1}
       Description: Failed to open package file "D:\Temp\SSIS_TESTING\TESTSSIS\TESTSSIS\Package.dtsx" due to error 0x80070003 "The system cannot find the path specified.".  This happens when loading a package and the file cannot
    be opened or loaded correctly
    into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.
    End Error
    Could not load package "D:\Temp\SSIS_TESTING\TESTSSIS\TESTSSIS\Package.dtsx" because of error 0xC0011002.
    Description: Failed to open package file "D:\Temp\SSIS_TESTING\TESTSSIS\TESTSSIS\Package.dtsx" due to error 0x80070003 "The system cannot find the path specified.".  This happens when loading a package and the file cannot be opened
    or loaded correctly int
    o the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.
    Source: {1244CD18-F96A-4DAD-8FC2-35F794015CA1}
    Started:  5:06:26 AM
    Finished: 5:06:26 AM
    Elapsed:  0.047 seconds
    NULL
    I'm getting Execte SSIS Package Status : 4
    ===================================
    4

    Two things to check
    1. The account executing the package has access to the path. If package is stored in different server you need to pass the UNC path (ie like \\machinename\...)
    2. Make sure the version of SSIS service is the same in both the servers ie where package is created/stored and where its getting executed. A lower version SSIS service will not be able to load and execute higher version package and it will throw you similar
    error messages as you posted above.
    Please Mark This As Answer if it solved your issue
    Please Mark This As Helpful if it helps to solve your issue
    Visakh
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • Ssis 2012 parallel execution of ssis packages using catalog database hangs

    i have a simple ssis package in 2012 where I am executing several data flow tasks in parallel using sequence containers, however very often the sql job just runs forever although all the tables have been loaded or I cant see whats going on, the job neither
    fails nor succeeds, just goes on executing,is there an issue with executing several data flow tasks in parallel, why does the job continue to run forver, how to troubleshoot and fix the error, please guide, are there any issues using the catalog db execution,
    is that the reason this behavior is showing?

    multiple execute sql tasks within sequence containers running to execute the ssis packages deployed in ssisdb in sunchronous mode using the catalog database execution model
    all of the ssis packages that have the data flow taks retrieve data from source to 3 different tables.
    some of them push data into the same table.
    please let me know if you need more information.
    the job just runs forever, looks like all the data flow tasks ran and it is still running, because I don't see an increase in the row count of the tables, I may be wrong, if I check the execution status, 1 task does not show as succeeded, I don't know why
    thanks  a lot for ur help, ur help is much appreciated nik

  • Run the SSIS Package using sql server Agent--Memory utilization Problem

    Hi,
    I have Created one SSIS Package it was working fine in BIDS but in SQL Server Agent it takes all the server memory and server gets very slow now.
    in that ssis package i am using merge join,sorting tasks.Can you please suggest me how to handle in the memory usage for this..pls refer the below screen

    Hi aravindhrm,
    You can enable BufferSizeTuning logging event on the Data Flow Task to get how many rows in buffer. Or you can use Performance Counter to obtain more details about the buffers.
    http://microsoft-ssis.blogspot.com/2013/04/performance-best-practice-more-rows-per.html 
    http://www.sql-server-performance.com/2009/ssis-an-inside-view-part-3/ 
    Then, you can tweak the DefaultBufferMaxRows and DefaultBufferMaxSize size settings.
    Besides, you can also go through the blog mentioned by Visakh and try suggestions such as increase OS pagefile size.
    Regards,
    Mike Yin
    TechNet Community Support

  • Trying to Execute Catalog SSIS Package using Catalog stored proc by a Master SSIS package inside a Loop

    Hi Guys ,
    To Execute Packages deployed in Catalog , I have created a wrapper SP  which internally calls  catalog SP  ( below is the code )
    ALTER PROCEDURE [Publish].[usp_ExecutePackages]
                  @PackageName NVARCHAR(255) 
           ,      @ProjectFolder    NVARCHAR(255) 
           ,      @ProjectName NVARCHAR(255) 
    AS    
    BEGIN
    SET NOCOUNT ON;
    DECLARE @Execution_id BIGINT ;
    EXEC [SSISDB].[catalog].[create_execution] @package_name
    = @PackageName
    ,   @execution_id
    = @Execution_id OUTPUT
    ,   @folder_name
    = @ProjectFolder
    ,   @project_name
    = @ProjectName
    ,   @use32bitruntime=
    True;
    EXEC [SSISDB].[catalog].[set_execution_parameter_value] 
    @execution_id,  
    @object_type=50, 
    @parameter_name=N'SYNCHRONIZED', 
    @parameter_value=1
    EXEC [SSISDB].[catalog].[start_execution]            @Execution_id
    Since i have multiple Packages , I am looping through list of PackageName and trying to pass package names to this SP by ExecureSQLTask inside ForLoop Container . But it errors out saying 
     "Cannot access the package or the package does not exist. Verify that the package exists and that the user has permissions to it.
    BUt same Execute SQL task , if i keep it outside the ForLoop Container it works perfectly fine . 
    I am  clueless , Please Please HELP me ASAP :( 
    Question :
    How is that possible to execute same SP with same parameter outside Container , But not in SEQUENCE or FORLOOP or FOREACH Container ?
    Also 
    How to make a master package to execute SSIS deployed packages via TSQL using catalog stored proc ?
    Please help me out .
    Thanks 
    Prasanna Selvaraju

    Hi , 
    After debugging i am getting parameter values as  
    {Extract - ARTL.dtsx\r\n} Unable to evaluate the expression.
    Why do i get  \r\n which i dont want in parameters .
    Actually i pick the values of package name from a custom table . I check it there are no spaces in the cell.
    Any IDEA WHY ? Please help
    Finally it worked to call Wrapper Class for EXEC [SSISDB].[catalog].[create_execution]
    stored procedure .
    Basically , ERROR MESSAGE is culprit
     "Cannot access the package or the package does
    not exist. Verify that the package exists and that the user has permissions to it. 
    Above Message : causing us to think
    its an Access issue , But actually when you pass parameter incorrectly even a " " space or "\n" extra to value, you will get that error .
    Nothing related to access problem .
    Actually , In the parameter which i was passing :
    {Extract - ARTL.dtsx\r\n} --> String with Enter / Carriage Return and Break line was there 
    I have removed the Enter in that variable value .
    Now its WORKING FINE ! Hurry :D :) 

  • How to debug a dll added in script component in SSIS package

    Hi All,
    I have created a Integration Services project in SQL Server Data tools for VS 2012 and added a SSIS package in it. Added a script task to this SSIS package and a DLL referenced in VSTA project. I am trying to debug the dll code by using the following steps
    but unable to do so. 
    1. Added break points in script task
    2. Started debugging 
    3. Stopped at one of the break points in VSTA projects
    4. Opened new instance of VS 2012 project for DLL library
    5. Added break points in the C# DLL library
    6. Attached this process to the VSTA project
    7. Code is not going through into C# DLL library.
    Any ideas would be appreciated.
    Thanks,
    Prav

    Yes, you can debug from a library (DLL) project, or even console. Just attach the debugger, but the DLL will be part of a different project. Make sure you have the pdb of the DLL, or source code, otherwise it is not possible.
    Arthur My Blog

  • In Existing SSIS package how we can call _vti_bin\listdata.svc service using script

    we have already used SSIS package using SharePoint List adapter but its not working properly... Can you will pref-are sharepoint list adapter for business purpose?  
    so we have decided to go with web service (_vti_bin\listdata.svc) and my main challenge is writing script i have to access list oblect from the webservice.
    Can
    you guide me how to write script ..how we can add service into script ...any examples for
    accessing SharePoint list( From Sql server to SharePoint list update)
    Regards,
    Anoop Nagappan

    We have already used SSIS package using SharePoint List adapter but its not working properly... Can you will pref-are sharepoint list adapter for business purpose?  
    so we have decided to go with web service (_vti_bin\listdata.svc) and my main challenge is writing script i have to access list oblect from the webservice.
    Can
    you guide me how to write script ..how we can add service into script ...any examples for
    accessing SharePoint list( From Sql server to SharePoint list update)
    Regards,
    Anoop Nagappan

  • SSIS script task using visual c# 2012 language when creating package in Visual Studio 2013

    Is it right or my installation was all wrong.
    When I am trying to use a script task in an SSIS package using Visual Studio 2013, the available languages are visual c# and VB 2012.
    I was expecting to find visual c# and VB 2013 since I was using Visual Studio 2013.
    I already installed the "Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013" available for sql 2014
    Please help clarify this. Thanks beforehand.
    Paulino

    Hi Paulino,
    According to your description, the ScriptLanguage property of C# script tasks show "Microsoft Visual C# 2012” in SSDT-BI for VS 2013.
    After testing the issue in my environment, I can reproduce it in SSDT-BI for VS 2013. And I find that the ScriptLanguage property of C# script tasks show "Microsoft Visual C# 2010” in SSDT, and show "Microsoft Visual C# 2012” in SSDT for SSDT –
    BI for VS2012. It only appear in SSDT-BI for VS 2013.
    The issue is by design. But we can check "Do not show this again." to ignore the dialog and the task can be executed without any problem.
    The following feedback is for your reference:
    https://connect.microsoft.com/SQLServer/feedback/details/1027035/ssdt-bi-for-vs-2013-compatibility-issue
    Regards,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

Maybe you are looking for