Hi,
I am developing Package in Dev Environment. And I want to test it eventually in QA and move into PRODUCTION.
I have declared Package level Variables, and running them from a batch file.
How can I do this by configuring variables in SSIS and enable my package to migrate from DEV to QA?
Regards
Ravi
Hello,
we have several sql agent jobs that start ssispackages (stored in a server store in the same server).
They worked fine for the last months. This weekend our sql server restarted due to hyper-v problems. After this restart
the ssis packages do not work any more when start via sql agent jobs. If i start the package via SSMS directly without a job step in sql agent
everthing works fine.
If i start the job it is running but it doesn´t end. If i log on to the sql server i see the process "dtexec" in the
task manager. But it doesn´t finish. i also have o log entries etc. If i then try to stop the sql agent job in SSMS i get an
error in the sql agent error log "[136] Job TEST SSIS reported: Unable to terminate process 1544 launched by step 1 of job 0x308211B401FBA641BC9F7762C3EB6868 (reason: Access is denied)"
But this error only appears if i try to stop the job.
what´s wrong with the sql agent? two day ago everything worked fine.
Thanks
Markus
Hello,
I was working on SSIS package and was using Execute SQL Task OR Script to get/set data in database.
In many cases, i found that people are also using Data Flow task and define flow there.
So would like to know the best practice on when to use Data Flow task and when to implement directly in Control Flow.
This will help me to understand that i am not using feature more when i can do it in easy and simple flow.
Technical Project Manager cum Architect
So how does control flow relate with data flow(not difference)? They are processed in parallel or some part of the control flow will activate the data flow? or data flow first, then control flow?
How does SSIS mingle them together?
Hi ,
In my SSIS package I am loading a data from flat file to SQL server In-memory table and then updating to target table from In-memory table.
In my one of the target table I am having data count like 50 million and in source table data count is 1 million.
I am using execute sql task in my package to call the update stored procedure.It bis taking around 18 minutes to complete that particular update task.
Is there any way to improve the update time
Thankx & regards, Vipin jha MCP
Hi Experts,
I don't know this is a right place to post this question if not please move in right place.
I have an Oracle ERP with following configuration.
Machine Information :
Operating System | Oracle Linux |
Operating System Release no | Oracle Linux Server release 6.5 |
Kernel | 3.8.13-16.2.1.el6uek.x86_64 |
Database Version | Oracle Database 11 g Enterprise Edition Release 11.2.0.2.0 64 Bit |
Application Version | EBS R12 12.1.3 |
Enterprise Business Suit | EBS R12 |
Now I have an HRMS based application which has Microsoft SQL Server 2014 Express DB now I want to connect this DB with Oracle DB (Having Parent Schema) , Please guide me how can I easily achieve this task.
Hi all,
I'm working on a client on an SSIS solution with VS2010. In an SSIS package we have a script component. It ran fine untill a couple of days ago we started receiving an `Object reference not set to an instance of an object`. This came from the script component.
Now the strange part:
It's not just this one script component: it happens with all script components I run from VS2010. We're unable to explain. Anyone seen something like this before?
Thanks for you time.
Frederik
Hi
I have a data flow task that fails on a foreign key constraint. I was hoping that by creating an Error Output flow on the destination object, I would get the actual error message from SQL Server, something like this (which I get when running SSIS from Visual Studio
"Error: 0xC020844B at Data Flow Task, tblEmp_Pay_Prd Destination [1458]: An exception has occurred during data insertion, the message returned from the provider is: The INSERT statement conflicted with the FOREIGN KEY constraint "xxxx". The conflict occurred in database "xxxx", table "xxxxx", column 'xxxxx'."
However, the only error logging I get is the error code -1071610801 and the generic "An error has occurred while sending this row to destination data source." error message.
I tried turning on SSIS logging and the error message is still vague
"SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "xxxx Destination" (1458) failed with error code 0xC020844B while processing input "ADO NET Destination Input" (1461). The identified component returned an error from the Process
Input method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure."
How can I get the first error message and log that to a file (or table)?
I'm on SSIS 2008r2
Hi,
We currently use Attunity SSIS Connectors v2.0 for Oracle with SQL Server 2012 Integration services within the Visual Studio 2012 IDE.
We are moving to SQL 2014 and want to leverage Visual Studio 2015 SSDT as this now includes all the BI projects (SSIS, SSAS, SSRS) + SSDT and integrated with Visual Team Services. We are testing the dev tools prior to the upgrade.
I have installed the version 3.0 Attunity SSIS Connectors for Oracle (both 32bit and 64bit) which states that is works for VS 2013+, but the Connection type is not available within my Visual Studio 2015 SSIS project.
So my question is - are the Attunity SSIS Connectors v3.0 for Oracle supposed to be compatible with VS 2015, and if not, is there expected to be an update in the future?
Kind Regards,
James
I have Visual Studio 2013 installed on machine in addition to MS SQL Server 2012. I used to use all the Business Intelligence projects in MS VS 2013 in a very normal way. However, recently when I created a new SSIS project and then clicked on the SSIS packages in order to create a new SSIS package, I got the following error:
Error creating package
------------------------------
ADDITIONAL INFORMATION:
Retrieving the COM class factory for component with CLSID {B5F5B1CF-7950-436C-B3BD-E193B1F5E5A5} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E). (Microsoft.SqlServer.ManagedDTS)I hope the that the information I have provided are sufficient to explain my problem clearly.
Well, I've just gone through my first real exposure to VS2013 with SSIS. Up to now, I've been using VS2008.
At the moment, just one word.
Yuck.
Ya know, visually, VS2008 was so clean and crisp. VS2013 may have some new functionality - I don't know, yet, as I've not really explored it - but, visually? It's a hunk of junk.
What was wrong with the visuals of VS2008? Why did MS have to go all cartoony and slap in monochrome tasks that are hard to distinguish at a glance? I have some fairly large SSIS packages and it was not all that hard to find, for example, the Data Flow task embedded among a group of SQL Tasks. The double yellow cylinders stood out among the red checkmarks.
I'll go search the options, but I'll ask, anyway, is there a way to revert the VS2013 visuals and graphics back to what they were in VS2008?
Hi. We run 2012 enterprise. I just finished a poc that showed if I insert my finder keys to db2 thus allowing my joins on db2 to render 10's of thousands of lookup records instead of 10's of millions, that my job can run in about half the time. The run time reduced from 21 minutes to 10. The db2 datasets are used in merge joins for lookup purposes. SQL Server datasets serve as the left side of most of these merge joins. In one case a sql server dataset is inner joined with the db2 data.
I noticed that the finder inserts themselves were taking a substantial amount of that 10 minutes. Anywhere from 3-6 minutes. And the source sql server query was only 8 seconds of that 3-6 minutes in the insert DF. There are only 46k records that need to be inserted into the db2 finder table.
My db2 connection says my provider is Native OLE DB\IBM OLE DB Provider for DB2 - DB2COPY1. My db2 table name is from a variable because for some reason the dropdown of db2 table names didn't seem to go far enough into the alphabet for me to pick my table.
I poked around and concluded that while fastload rowset and fastload rowset from variable could be chosen in the properties of the target oledb db2 component, choosing them over "rowset from var" wasn't legal and in fact turned the destination component red.
Does the community have any recommendations for making these inserts perform faster?
Hello,
My Flow is as follows
Get Filenames & Table names to load data -> Truncate Table Name -> Load data from CSV file
Now in control flow, i want to truncate table before loading data from csv file.
I get Table name in variable and now i want to execute truncate command. As i do not want to write small stored procedure which take table name as parameter and then use sp_executesql stored procedure to execute the command.
So i want to do same in SQL statement within SQL task but it give error, so not sure how to pass SSIS variable inside SQL statement as adding to parameters is also not working with "?"
Something like this
DECLARE @sql VARCHAR(200)Technical Project Manager cum Architect
I need to read value from a sql column ( varchar(Max) which contains multiple lines text split by char(13)) as string. Then inset the string value to a multiple line text column in a sharepoint list. I have the following code in my script component:
result = System.Text.Encoding.Unicode.GetString(Row.Comments.GetBlobData(0,Convert.ToInt32(Row.Comments.Length)));
item["Comments"] = result;
Here is the value in sql:
Christopher Wax ** Summer Associate Abraham Murach
This is what I get in sharepoint:
潦浲牥祬䌠牨獩潴桰牥传瑲穩丠⁙畓浭牥䄠獳捯慩整㈠〰�
Please let me know is this the right method to convert sql blobcolumn value to string? If it is, then what is wrong in my code. Thank you.
Hi -
I was working on a SSIS Package which simply loads an excel file and it contains no complicated transformations. The SSIS Package executed via Visual Studio 2015 works completely fine. However, when I try to load it via SSIS Catalog (SSISDB), the execution fails. The size of excel source file is (approximately) 2 MB.
If I reduce the number of rows inside the excel source file and bring the file size down to around 1.16 MB, then the file is loaded successfully via SSIS Catalog (SSISDB). The error messages that I am receiving while loading the original excel source file are as follows:-
Any help for resolution of this particular issue will be greatly appreciated. Thanks in advance.