Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

SSIS Load to table results is different from SSMS query

$
0
0

I'm going to try to explain this odd results as best as I can.

Say I have an application server, it has an SQL database. I'm attempting to load details from a table from that application database to another server's database for reporting purposes. 

So, I have a SSIS package created. It pulls in all details for customer orders. Lets call this table Customer_Orders_Source.

In my Data Flow, for my Read From Data Source, I have my SQL query, it runs with no problem. 

I have my load to table, everything seems good. My package will load all details from Customer_Orders_Source from the application server, to a table called Customer_Orders_Rpts on the reporting server database. 

I run the package. It runs successfully. 

Now, from running my query on the application server, I know that for example customer_id '55110' has 6 unique transactions. 

However, after the package runs and I check my target table ' Customer_Orders_Rpts', only 1 row returns for this customer. Run the package again and still only one row returns, but another transaction. 

SO let's say the first time I ran the package, the result was for customer_id= 55110, transaction_id= '2'. The second time I run the package, the result would change to customer_id=55110, transaction_id='4'.

So the results are alternating, but why? Can anyone explain and assist me in finding a solution for why the results are less when I run the package as oppose to when I run my query directly in SSMS. 

I've tried recreating the package. 

A similar question suggested checking the permissions, although I'm not sure how or which permissions to check since I do have other packages running that seem to pull in all details. Same application server, same destination. 


Viewing all articles
Browse latest Browse all 24688

Trending Articles