SSISDB queries return zero rows

June 23, 2019, 5:11 pm

≫ Next: Open Source Job Scheduler for SSIS

≪ Previous: How to log the error in error table in case of lookup mismatch in parent table

$

0

0

Hi All,

I am a member of the db_datareader and SSIS_ReportReader roles on our production SSIS server's SSISDB database.  Confusingly, my queries of catalog views return zero rows.  There's no permission error, just zero rows in the results.  If I change my query connection to the dev server [where I'm sysadmin], the same query returns rows.  I'm able to view production SSIS execution reports, but I can't get results from querying directly.  Is there a likely cause for this? 

Thanks for your help,

Eric B.

---

Open Source Job Scheduler for SSIS

June 23, 2019, 11:47 pm

≫ Next: Implementing temporal tables for dimensions to track changes

≪ Previous: SSISDB queries return zero rows

$

0

0

Hi,

   As part of budget constraints we are planning to migrate our SQL Server DB to PostgreSQL. But still going to use SSIS as ETL.

As the server having only SSIS (No SQL Server with SQL Agent), we required suitable Job scheduler for executing this SSIS.

Please suggest any good Job Scheduler for SSIS... our current plan is Windows Scheduler, but dont think its a flexible one like any Job Scheduler. Pls help....

Implementing temporal tables for dimensions to track changes

June 24, 2019, 1:21 am

≫ Next: SQL Server Integration Services 2016 won't fail package on Stored Procedure Thrown error

≪ Previous: Open Source Job Scheduler for SSIS

$

0

0

I am working on a star schema and I want to track the history of data for some dimensions and specifically for some columns. Is it possible to work with temporal tables as an other alternative ?If yes, how to store the current record in a temporal table?Also, is it logic that the source of my dimension will be the historical table of my temporal table ?

SQL Server Integration Services 2016 won't fail package on Stored Procedure Thrown error

June 24, 2019, 10:12 am

≫ Next: SSIS Server installation

≪ Previous: Implementing temporal tables for dimensions to track changes

$

0

0

Hello,

We have MS SQL Server 2016 with all of the optional components installed.

Within one of my SSIS packages I have an "Execute SQL Script" task that executes a stored procedure. Under properties on that task, I have it set true to "FailPackageOnFailure" and "FailParentOnFailure".

If my stored procedure throws an error, the package will show as successful. However, if it raises an error, then the package fails.

Throw -> https://docs.microsoft.com/en-us/sql/t-sql/language-elements/throw-transact-sql?view=sql-server-2017

Raise -> https://docs.microsoft.com/en-us/sql/t-sql/language-elements/raiserror-transact-sql?view=sql-server-2017

Am I doing something wrong, is anybody else experiencing this?

Sample Syntax:

begin try;
end try;

begin catch;
 throw; /* Doesn't fail the package */
end catch;

SSIS Server installation

June 24, 2019, 12:55 pm

≫ Next: Conversion failed because the data value overflowed the specified type

≪ Previous: SQL Server Integration Services 2016 won't fail package on Stored Procedure Thrown error

$

0

0

HI 

 we are going to have new sql server and ssis installed on my office machine for ETL work. I asked them for the following softwares . 

1. MS Sql Server 2017 Enterprise edition

2. Latest version of Sql Server Management Studio ---SSMS18.1

3. Visual Studio Enterprise 2017 4. Sql Server Data tools for Visual Studio 2017--- Please use version 15.8.0 (please install all three below components below in this)

5. Sql Server integration Services 2017

6. Sql Server Reporting services 2017

7. Sql Server Analysis Services 2017

8. Microsoft connector for oracle by attunity ---V5.0.

we are also going to have a dedicated ETL Server for  running nightly jobs. I am not sure what softwares that needs to be installed  on that server machine for the deploy ssis packages and agent jobs to run . can you please let me know. Company is willing to get all new softwares that are latest. 

Please forgive if this is a basic question. 

Conversion failed because the data value overflowed the specified type

June 24, 2019, 1:17 pm

≫ Next: ODBC Source - External Column to Output column data type settings

≪ Previous: SSIS Server installation

$

0

0

Hi All,

I amloading data from one sql server db to another . In my package its straight forward, no transformations. Its failing since friday with the following emssage

Conversion failed because the data value overflowed the specified type

on a column "temp_deg_c" . The datatype in the source and destination is the same (decimal(9)). I did some analysis and found out that two records have data like this , these are TEMPERATURE recordings .

223627.8
493827160493808.9

I increased the size to 18 and still getting the same error message. Can someone please advice if i have to change the data type to int or something else?

Thanks

ODBC Source - External Column to Output column data type settings

June 25, 2019, 1:09 am

≫ Next: Unable to uninstall SQL Server Integration Services Projects Extension

≪ Previous: Conversion failed because the data value overflowed the specified type

$

0

0

My requirement scenario is as follows:

In source database table, the columns have CHAR data-type, so the EXTERNAL COLUMN DATA-TYPE value is auto-populated as DT_STR. And the auto-populated value of OUTPUT COLUMN data type is also DT_STR. Requirement is to change the OUTPUT COLUMN data type is also DT_WSTR (Unicode).

Solution approach: One option is that doing changes manually using advance editor for each column, but that seems very tedious task, as we have large number of tables.

Could you please tell if there is any automated way to do these changes? 

For example, if there is any settings we can change in visual studio, so that whenever EXTERNAL COLUMN DATA-TYPE value is DT_STR, the OUTPUT COLUMN data type to be populated as DT_WSTR (Unicode).

Or if we can change quickly in dtsx code.

Unable to uninstall SQL Server Integration Services Projects Extension

June 25, 2019, 2:11 am

≫ Next: SSIS Execute SQL Task not deleting records

≪ Previous: ODBC Source - External Column to Output column data type settings

$

0

0

I installed SQL server, then SSDT from VS installer and after that the SSIS Extension v3.0 for VS Community 2019. But now that when I try to uninstall it I get the following error:

Some components will not be uninstalled because removing them would place this computer in an unsupported state. Please manually remove them in Control Panel.

After that I get the following message:

The configuration registry database is corrupt (0x800703F1)

---

SSIS Execute SQL Task not deleting records

June 25, 2019, 5:24 am

≫ Next: Oracle data source connectivity issue in ETL Package using script task(C# Code)

≪ Previous: Unable to uninstall SQL Server Integration Services Projects Extension

$

0

0

Hello,

I'm trying to use an Execute SQL Task to delete records from a table (Test) that  have a specific value in a field (Field1).  The field is a varchar(15) and the records I need to delete have a value that is not equal to HOME.  When I run the task, no records are deleted.  Here is the query I'm running in the task:

DELETE FROM Test WHERE Field1 != 'HOME';

Oracle data source connectivity issue in ETL Package using script task(C# Code)

June 25, 2019, 5:31 am

≫ Next: Running an SSIS package through Batch File

≪ Previous: SSIS Execute SQL Task not deleting records

$

0

0

Hi,

I'm trying to connect Oracle data source in ETL package using script task(C# Code) and getting server version error.

Help me how to resolve this issue.

Visual studio version : 2015

Connection Type : OLEDB Connection

Provider : OraOLEDB.Oracle

Thanks,

Krishnan

Running an SSIS package through Batch File

June 25, 2019, 5:36 am

≫ Next: not display the weekend

≪ Previous: Oracle data source connectivity issue in ETL Package using script task(C# Code)

$

0

0

Is there a way to read the DTEXEC result and when DTExec: The package execution returned DTSER_SUCCESS (0). contine the remaining steps in the batch file otherwise STOP .

not display the weekend

June 25, 2019, 7:01 am

≫ Next: SSIS dev and test on same server

≪ Previous: Running an SSIS package through Batch File

$

0

0

Hi,

I have the report send out to display the due date as below and not show the weekend.  For example, today's report I have 

1= Late,

2= Today,

3= Tomorrow,

4=Tomorrow+1,

5=Tomorrow+2

6= Tomorrow +3

7= Tomorrow +4

but mine logic is displayed 6/29 instead of 7/1.  I am not sure what i have wrong , please help. Thanks

declare @testdate date
set @testdate = '06/25/2019'
select '1' sortGroupBy --late
      ,'' dt
 
  union all
select '2' sortGroupBy--due today
      ,convert(varchar, @testdate,101) dt
     
 union all
select '3' sortGroupBy--due tomorrow
      ,case when datename(dw,dateadd(d,1, @testdate))='Saturday' then convert(varchar,dateadd(d,3, @testdate),101)
            when datename(dw,dateadd(d,1, @testdate))='Sunday' then convert(varchar,dateadd(d,2, @testdate),101)
            else convert(varchar,dateadd(d,1, @testdate),101) end dt
 
 union all
 select '4' sortGroupBy--due tomorrow + 1
      ,case when datename(dw,dateadd(d,1, @testdate))='Saturday' then convert(varchar,dateadd(d,4, @testdate),101)
            when datename(dw,dateadd(d,1, @testdate))='Sunday' then convert(varchar,dateadd(d,3, @testdate),101)
            else convert(varchar,dateadd(d,2, @testdate),101) end dt
   
  union all
  select '5' sortGroupBy--due tomorrow + 2
      ,case when datename(dw,dateadd(d,1, @testdate))='Saturday' then convert(varchar,dateadd(d,5, @testdate),101)
            when datename(dw,dateadd(d,1, @testdate))='Sunday' then convert(varchar,dateadd(d,4, @testdate),101)
           else convert(varchar,dateadd(d,3, @testdate),101) end dt
 --     
 union all
  select '6' sortGroupBy--due tomorrow + 3
      ,case when datename(dw,dateadd(d,1, @testdate))='Saturday' then convert(varchar,dateadd(d,6, @testdate),101)
            when datename(dw,dateadd(d,1, @testdate))='Sunday' then convert(varchar,dateadd(d,5, @testdate),101)
            else convert(varchar,dateadd(d,4, @testdate),101) end dt

 union all
select '7' sortGroupBy--due tomorrow + 4
      ,case when datename(dw,dateadd(d,1,@testdate))='Saturday' then convert(varchar,dateadd(d,7,@testdate),101)
            when datename(dw,dateadd(d,1,@testdate))='Sunday' then convert(varchar,dateadd(d,6,@testdate),101)
            else convert(varchar,dateadd(d,7,@testdate),101) end dt

SSIS dev and test on same server

June 25, 2019, 10:28 am

≫ Next: Stored Procedure Resultset Issue in SSIS

≪ Previous: not display the weekend

$

0

0

HI 

I am new to infrastructure. my director says he wants to have  dev and test as two different databases  in  the same server(he want to use virtual machines) and he also wants to have  dev and test as two different databases  in same server .  we have to eventually create a Sql agent job to deploy ssis packages and  schedule them to run overnight.  and this will also be our database server with tables and data , we wont have dedicated ETL servers for SSIS.

can you please  let me know is this possible? 

I am thinking its not possible, because ssisdb  will hold the same packages for dev  and test. so you are running same packages for dev  and test but   you are pointing to two different databases (dev database and   test database) which are  in same server. 

is it a best practice to keep dev and test in same server(virtual machine)  ? 

The data will be eventually reached to 600GB in next one year.

Stored Procedure Resultset Issue in SSIS

June 25, 2019, 3:00 pm

≫ Next: SSIS Job error: The connection type "PowerQuery" is not recognized as a valid connection manager type

≪ Previous: SSIS dev and test on same server

$

0

0

Hello,

We are upgrading our SQL Server database from 2008 to 2016 and in the process of upgrading, we are also upgrading the SSIS packages. However, there are couple of SSIS jobs that use the update query are failing with the below error message.

'Executing the query "usp_Accts_SFDCAccountId"  failed with the following error. Unable to populate result columns for single row data type. The query returned an empty result set. Possible failure reasons. Problems with the query, Result set not set correctly, parameters not set correctly, or connection not established correctly'.

The "Execute SQL Task" in the SSIS package has not changed, the SSIS package was upgraded using Visual Studio 2017. The Resultset is set to "Single Row" in the Execute SQL task. This is working fine in SQL server 2008 job, but failing with the above error message with SQL Server 2016.

Can someone help?

SSIS Job error: The connection type "PowerQuery" is not recognized as a valid connection manager type

June 25, 2019, 1:59 pm

≫ Next: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

≪ Previous: Stored Procedure Resultset Issue in SSIS

$

0

0

Hi all,

Before posting my question I have already gone through some of the replies on this forum and unfortunately I found no answers. Especially there is this link https://www.powerbi-pro.com/en/power-query-in-ssis/ that describes the how-to. My project runs fine from client side but NOT when deployed. Following is my post: 

I have created an SSIS project and used the PowerQuery component to read from an Excel file. When I execute it from Visual Studio (client side) it runs fine, but when I deploy it on the SQL Server and create a job, by executing it I get a Failed error without any additional information.

When I go through the error list I get the following:

"The connection type "PowerQuery" specified for connection manager "Power Query Connection Manager" is not recognized as a valid connection manager type."

We are stuck and unable to run the job just because it contains the PowerQuery component or connection manager. if there is any resolution to my issue it would be greatly appreciated.

Thank you,

Nikos Zacharakis

---

Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

June 26, 2019, 12:11 am

≫ Next: How to schedule SSIS package weekly or daily based on a parameter?

≪ Previous: SSIS Job error: The connection type "PowerQuery" is not recognized as a valid connection manager type

$

0

0

Hi  Team,

Please help on bellow issue.

[Execute SQL Task] Error: Executing the query "update EIV set

EIV.InvoiceDate = RD.InvoiceDate,
..." failed with the following error: "No value given for one or more required parameters.". 
Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Query in Execute SQL Task:

update EIV set

EIV.InvoiceDate = RD.InvoiceDate,
EIV.ClientName = RD.ClientName,
EIV.AccountNumber = RD.AccountNumber,
EIV.ClientCurrency = RD.ClientCurrency,
EIV.bookingMode = RD.bookingMode
from
 Table1 EIV join Table2 RD 
onEIV.MFRefernce = RD.MFReference and
EIV.InvoiceID = RD.InvoiceID and
EIV.InvoiceNo = RD.InvoiceNo and
EIV.FlightId = RD.FlightId

where RD.isactive=1 and RD.row_id <=?

Screen shots:

main package

---

Thanks Bala Narasimha

How to schedule SSIS package weekly or daily based on a parameter?

June 20, 2019, 2:30 am

≫ Next: ODBC Progress datatype problems after updating to VS 2017 15.9

≪ Previous: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

$

0

0

Hello,

I have a requirement to give the users the possibility to indicate when a SSIS package should be executed. For example, they could say weekly or daily. Is there a way to achieve this? I have not found a pretty straightforward way to do this so far.

Thank you.

ODBC Progress datatype problems after updating to VS 2017 15.9

November 27, 2018, 3:58 am

≫ Next: I'm trying to upload data from excel to a table by the SQL Server Import and Export Wizard

≪ Previous: How to schedule SSIS package weekly or daily based on a parameter?

$

0

0

Hey there,

we are currently using VS 2017 15.7.5 and SSDT 15.8

We've got SSIS packages which read data from a Progress database via ODBC.

We updated to VS 2017 15.9.2 and now all the ODBC Progress packages fail, nothing else has been changed.

The problem we have is that all the columns which were previously correctly identified as DT_DBDATE are now recognized as DT_BYTES.

It seems to be some weird regional or language problem.

Comparing the ODBC Source previews:

On the machine where we still have 15.7.5 date values show as for example "2018-11-05".

On the new machine with 15.9.2 date values show as "3/11/2014 12:00:00 AM".

Changing any of the machine's regional settings didn't help, so it must be a problem within Visual Studio?

I'm trying to upload data from excel to a table by the SQL Server Import and Export Wizard

June 26, 2019, 3:10 am

≫ Next: How to convert ZIP data stored in sql table into text format

≪ Previous: ODBC Progress datatype problems after updating to VS 2017 15.9

$

0

0

I'm trying to upload data from excel to a table by the SQL Server Import and Export Wizard.

But I received this error:

TITLE: SQL Server Import and Export Wizard -

The operation could not be completed. 

ADDITIONAL INFORMATION: The ConnectionString property has not been initialized. (System.Data) 

How to convert ZIP data stored in sql table into text format

June 26, 2019, 4:23 am

≫ Next: How to pass a variable to one package to another package in ssis

≪ Previous: I'm trying to upload data from excel to a table by the SQL Server Import and Export Wizard

$

0

0

Hi Team,

Could you please help on bellow issue.

1. My application team data storing in the format of ZIP in sql table.
2. I need to convert that data into text and again store in a database

sample data:

ColumnNameValue
profilerId1
requestXML0x1F8B0800000000000400858FC14EC3301044EF48FC83E57BB3495BF550392EA8D7362AB4485C5D67492C1A1B7937753F9F104124B870DC796FB41AB5B9751771C5482EF85216592E057A1B6AE79B52F6FC362B5672A3EFEFD411E9CBD946348CCF4F62E8795ADFA82E65CBFCB106482965699185D8C03CCF0B78DDEF8EB6C5CEC84976FFCB33E7898DB72887AF42A8476B43EFB9EABB3346BDDF5683BDCC570A7E83D17D218C95E950BF9BABE3D6289892911F0C510AB1FEE10FC57CA1604A47E7646283AC4F48ACE0FB18E6C39FFDFA1399270E463A010000
responseXML0x1F8B08000000000004008590B18EC2301044FB93EE1F2CF78E6D12E5129498E27405123484E25A6BB30991C041F6E6C2E71310208E867276DEEC48532C4E873DFB431FBADE955C478A3374D0D79D6B4B3E502374CA17E6F3A3A8305C986F8F967053B129E7C2FC14EA92EF888E7329C7718CC638EA7D2B674A69F9BB5E55B0C383E50FB87B0F8BCE05B20E904FAD8CDD7B2BB23404437EC042FEBF3D63CBDA3439400E0842CFE25424598A224B621099822657FA0B92A479BC98F86B7C6B7D8B64B618A8903771357EBCEF7D60F232817CD9C09C014D29514A3E010000
createdOn6/1/2015 11:33

---

Thanks Bala Narasimha