Data Viewer not triggered in SSIS

Question

Using: Windows 7 Enterprise; Visual Studio Pro 2017 (15.3.5); SSDT 15.1

Can't get Data Viewer to pop up on my SSIS package. I did do some Google-fu, and can't find anything relevant (or newer than 2010).

I've used the DV many times in the past, so I'm aware of how to enable a DV, the magnifying glass icon is present on the data flow paths, and I know it's not an issue of a hidden window since my package never actually pauses at any of the DV-enabled points.

Has anyone experienced this before? Am I missing something?

Fruiterer

Have you tired deleting and recreating the dataviewer? Is the dataviewer docked, so you just can't see it? Is SSDT losing it's mind? :) – Candidate

I do face the similar issue with VS 2017 with SSDT for VS 2017. However, I am still figurig out the solution. – Sangraal

have you find a solution yet? – Raskind

When I change the Target Server property in configuration to SQL Server 2016 (eventhough target is SQL Server 2017) , data viewer works fine – Sangraal

Same problem here. But so far no solution. – Teakettle

Answer 1

I found this question because I was having this problem also. For me it turns out that the Data Viewer was not popping up simply because there were no rows in the underlying recordset. I had expected it would pop up anyhow and show zero rows, but apparently not.

Quintus

1+ Gah... this was exactly my issue, I forgot that I had truncated my staging table earlier! Thanks! – Nance

I ran into the same thing. I was dealing with a temporary table and from time to time, it was not filled even though I had not changed the code. During my first tests, this might also have happened, even though I later also found Data Viewer windows that had been opened in the background and had only null entries. I guess that you need not just null entries, but no rows at all, as this answer also says it. – Esemplastic

Answer 2

On project property page Change the "TargetServerVersion" so the target server is the same as your database server.

Antinomy

Welcome to Stack Overflow community. Please take some time and complete Welcome tour and read How do I ask a good question? guide. – Cyclosis

@Roy Bercovitch, is there any workaround to use DV with target server SQL Server 2017? I am in a position that I used a dependency which will not work with target SQL Server 2016 so just checking around. Many thanks in advance. – Fanya

Or the closest to it. I was using SQL Server 2008 (!), the package was looking for 2017 and setting it to 2014 still worked. – Corene

Answer 3

Try to set the Runtime for debugging to 32Bit (right click your project, choose "Properties"-entry, click "Debugging", set "Run64BitRuntime" to "false")

In my case i was able to use Dataviewers then.

Bille

I did that, but I later changed it back and in both settings, it showed up. Therefore, I guess that this is a placebo. But I am not sure either since it might also have helped in the first place and then afterwards is not needed anymore. But I think that this is unlikely. – Esemplastic

Answer 4

What do you have downstream of the DV? Can it be optimized out? For example, sometimes I will want a DV after a transform and nothing after that (ie, for debugging). Since I can only put a DV on a connecting line, I will stick a dummy transform (say, Union All or Multiplex) so that I can use it's connecting line.

However, sometimes SSDT will optimize that transform -- it'll notice that the Union All's output is going nowhere and deduce that it is not needed, and there goes my viewer. I usually see this outside of the IDE (ie, dtexec), but once in a while inside the IDE.

Also, you could try resetting your IDE's window layout (under the Window menu). Sometimes the viewers hide outside of the desktop, particularly if you're RDPing to the machine.

Toniatonic

Answer 5

I have facing same issue , i have deleted the existing package and create new one.. It is worked for me..!!!

Exist