ssdt-bi

To run a SSIS package outside of SQL Server Data Tools you must install Move File to Archive of Integration Services or higher

妖精的绣舞 提交于 2020-01-19 05:55:27
问题 I am testing SSIS package that I upgraded from VS2005 project to VS2013 (package deployment model) project. This is very simple package which just processes files one by one from specific location and updates database based on those files and once done it moves file to archive or non-parsing directory based on outcome. And I am getting odd error and I cant find solution for that. Issue is my package runs fine and it does exactly what it suppose to do (extracting data from file and inserting

Why is SSDT Schema Compare showing difference in DefaultExpressionScript?

為{幸葍}努か 提交于 2020-01-02 04:31:11
问题 While comparing Database instance to a Database project in VS2010 using SSDT, it shows a difference in one of the Stored Procedures. The Store Procedure DDL script is exactly the same but when I expanded the Properties folder under the Store Procedure it show a difference in the DefaultExpressionScript. The source SP shows this in the DefaultExpresionScript: DefaultExpressionScript = at While the destination SP has this: DefaultExpressionScript = -1 I don't see where I can change this there

Change .NET Framework in Integration Services Project

北城余情 提交于 2019-12-23 16:48:07
问题 When creating a new Integration Services Project in Visual Studio 2013 I can select the .NET framework to target. How can I see what .NET framework is being targeted on an existing project and potentially change it? 回答1: You need to open one of the Script Tasks and click the "Edit script..." button. This will open the script on a new instance of Visual Studio with the script in its own project. There you can change the properties of that project to modify the targeted framework for that

SSDT, SSDT-BI confusion in backwards compatibility for different SQL version

风格不统一 提交于 2019-12-22 14:06:41
问题 After extensively searching over google about SSDT and SSDT-BI for different SQL Server versions, I would like someone to pin-point differences and clear my messed up thoughts ! Aim: To upgrade SSIS packages from sql server-2012 to sql server-2014. Originally build from: build on SSDT-BI 2010 Shell(Integrated) which were deployed on SQL Server 2012 Enterprise edition. Now I need to deploy them on SQL Server 2014 Developer edition (for test purpose). I have successfully installed SSDT-BI 2013

use expression to dynamically decide which subreport to open

蹲街弑〆低调 提交于 2019-12-22 08:38:35
问题 I have a report that contains several pages with graphs, tables and so on. This report is used by different customers who always want small modifications to the report. At the moment if a customer wants a change on page 5 the whole report is recreated with the modifications, even though the only change is in the graph on page 5. More so, some customers don't want to see page 3, others want a custom table at page 6. My boss would like the report to be modular so he can simply switch parts on

SSDT, SSDT-BI confusion in backwards compatibility for different SQL version

蹲街弑〆低调 提交于 2019-12-06 07:18:39
After extensively searching over google about SSDT and SSDT-BI for different SQL Server versions, I would like someone to pin-point differences and clear my messed up thoughts ! Aim: To upgrade SSIS packages from sql server-2012 to sql server-2014. Originally build from: build on SSDT-BI 2010 Shell(Integrated) which were deployed on SQL Server 2012 Enterprise edition. Now I need to deploy them on SQL Server 2014 Developer edition (for test purpose). I have successfully installed SSDT-BI 2013 Shell(Integrated) and SSDT 2015 Shell(Integrated). Problem: When I open my package in 2013, it prompts

Why is SSDT Schema Compare showing difference in DefaultExpressionScript?

一世执手 提交于 2019-12-05 09:56:32
While comparing Database instance to a Database project in VS2010 using SSDT, it shows a difference in one of the Stored Procedures. The Store Procedure DDL script is exactly the same but when I expanded the Properties folder under the Store Procedure it show a difference in the DefaultExpressionScript. The source SP shows this in the DefaultExpresionScript: DefaultExpressionScript = at While the destination SP has this: DefaultExpressionScript = -1 I don't see where I can change this there is no such object called DefaultExpressionScript in my database project. where should I fix this? This

Visual Studio 2013 High DPI workaround causes debugger to fail

↘锁芯ラ 提交于 2019-12-04 22:35:20
问题 Similar to this question Visual Studio 2013 High DPI on 4k Screen to which I had posted an answer but have now removed since uncovering the issue below. I too have just bought a new 4K laptop and have been having problems with high DPI with the display of the SSIS package designer and dialogs in VS2013 as well as dialogs etc in SSMS. A workaround I found for SSMS is to enable bitmap scaling and create a manifest file - ssms.exe.manifest - in the same folder as ssms.exe. This article describes

Visual Studio 2013 High DPI workaround causes debugger to fail

穿精又带淫゛_ 提交于 2019-12-03 15:48:49
Similar to this question Visual Studio 2013 High DPI on 4k Screen to which I had posted an answer but have now removed since uncovering the issue below. I too have just bought a new 4K laptop and have been having problems with high DPI with the display of the SSIS package designer and dialogs in VS2013 as well as dialogs etc in SSMS. A workaround I found for SSMS is to enable bitmap scaling and create a manifest file - ssms.exe.manifest - in the same folder as ssms.exe. This article describes how to fix this for SSMS http://www.sqlservercentral.com/blogs/spaghettidba/2015/10/14/ssms-in-high

64 bit Microsoft SQL Server Data Tools

这一生的挚爱 提交于 2019-12-03 04:28:44
问题 I am having trouble finding the 64 bit version of Microsoft SQL Server Data Tools. Does any one know where i can download the 64 bit version of Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013 and SQL Server 2014. I have only been able to find the following 32 bit version http://www.microsoft.com/en-us/download/details.aspx?id=42313 but i need the 64 bit version. 回答1: As the others have said, there is only a 32 bit version. The important thing is, if you’re