RunGuid Value upto 23 digits in derived Column
Thousands of zero length files in SQLAgent AppData Local Temp while dtsx is running under SQL Server Agent?
Massive disk contention while this is running with disk queue lengths in the teens to 25. SQL Server Agent runs under its own account, TracSuiteSQLAgent. Unfortunately, I cannot move LocalAppData.
A periodic SQL Server Agent job runs a local DTSX file to pull newest data from another local system (Native OLE DB\SQL Server Native Client 11.0) and seems to generate the same number of zero length files as are returned from the first query.
Source Query: SELECT [ID],[ClientLabelType],[LabelName],[Usage],[LabelSerialNumber],[LabelXML],[LabelLotcode]
FROM [appDB].[dbo].[tblLabelInfo] where ClientLabelType like 'scale%' and LabelSerialNumber like '%MWT%' and substring(LabelLotcode,1,4)>'2018'
LabelLotcode is an index. Against a local table lookup (no cache, redirect rows with no matching entries to output):select * from (select * from [dbo].[tblLabelInfo]) [refTable]
where [refTable].[ClientLabelType] = ? and [refTable].[LabelName] = ? and [refTable].[Usage] = ? and [refTable].[LabelSerialNumber] = ? and [refTable].[LabelLotcode] = ?
Usually less than 2 are found as this job runs every minute during business hours.
Output to local table with data access mode set to table or view.
File names are of the form:
C:\Users\TracSuiteSQLAgent\AppData\Local\Temp\DTB{1464E310-B61F-40DE-A415-61DC24F8BD97}.tmp
Any suggestions about reducing the local I/O contention? Why are these files being created?
Regards and thanks, Ira
Ira Grollman
SSIS Attunity Oracle connector Job failing while submitting from SQL Server
Hi,
I am developing ssis packages using SSDT from my local system. I have ODAC 12c and Oracle client 12c all 64bit installed. When i submit this job from my local system job runs fine.
Now i have created another box where SQL Server 2014 is installed. This box is Windows Server 2012. In this box i installed ODAC 12c and Oracle client 12c all 64bit. I import .dtsx packages into this SQL Server and submit job using SQL Server agent. I get following error.
In both the machine i have both ssis attunity connector v3 & 4 64bit version.
Error:
MessageExecuted as user: METRARR\d_sqlagentsvc. Microsoft (R) SQL Server Execute Package Utility Version 12.0.4100.1 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 2:38:45 PM Error: 2017-12-20 14:38:48.13 Code: 0xC0016016 Source: TestOracle2 Description: Failed to decrypt protected XML node "OraPassword" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2017-12-20 14:38:49.14 Code: 0x000002C0 Source: TestOracle2 Connection manager "Oracle Connector 1" Description: OCI error encountered. ORA-01005: null password given; logon denied End Error Error: 2017-12-20 14:38:49.14 Code: 0x0000020F Source: Data Flow Task Oracle Source [2] Description: The AcquireConnection method call to the connection manager Oracle Connector 1 failed with error code 0x80004005. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2017-12-20 14:38:49.14 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline Description: Oracle Source failed validation and returned error code 0x80004005. End Error Error: 2017-12-20 14:38:49.14 Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2017-12-20 14:38:49.14 Code: 0xC0024107 Source: Data Flow Task Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 2:38:45 PM Finished: 2:38:49 PM Elapsed: 3.453 seconds. The package execution failed. The step failed.
Attunity Error in SSIS - "OCI Error Encouneterd"
I have SSIS BIDS (SQL Server 2008) (32 bit), and am using Attunity connector to connect to an Oracle DB. A while back we had our systems upgraded to windows 7 64 bit.
I have installed Oracle 11g client on my machine, added TNS entries for the above Oracle server connection and also pointed this path (path for TNSNames.ORA) in the "PATH" environment variable as well as "TNS_ADMIN" (which I created) environment variable.
Even after doing all this, I get the following error when validating the Attunity Oracle source connector, the error is as follows:
"OCI Error Encouneterd. ORA-12154: TNS could not resolve the connect identifier specified, Test connection failed".
I also researched that this might be due to paranthesis in the path for devenv.exe (BIDS).... So I went through the following post, installed JUNCTION, and created a junction pointing to the actual directory for devenv.exe.
http://danieladeniji.wordpress.com/2011/08/03/microsoft-sql-server-integration-services-attunity-error-oci-error-encountered-ora-12154-tnscould-not-resolve-the-connect-identifier-specified/
This too has not resolved the problem....
Any help appreciated!!
Error encountered while creating OCI environment - NEED SOME HELP PLEASE !!!
Hello,
I have posted the below problem to Attunity Forum already. I thought I would post it here as well since, at this point, I am sure if this is an SSIS, MSSQL or the Microsoft Oracle Connector (by Attunity). If anyone has experience with resolving my error, PLEASE HELP!! Any kind of ideas/suggestios is appreciated because I am running out of ideas.
Thank you
-----------------
http://forums.attunity.com/forums/microsoft-ssis-oracle-connector/error-encountered-while-creating-oci-environment-3196.html
Hello,
Some background info:
- Windows 2012 Server R2
- Oracle client x32 11gR2
- Running SSIS x32 DTExec utility
- Microsoft Oracle Connector x32 2.0
The package I have connects to Oracle 11gR2, pulls data and loads them into MSSQL 2012. The package runs
perfectly in SSDT (aka BIDS) as well as executing it from the command line calling Microsoft x32 DTExec.exe. However, when the job
is invoked from the SQLAgent as a scheduled job, it keeps failing with the following error:
Error: 2016-04-03 10:34:52.99
Code: 0x000002C0
Source: Load_Expense_to_SQL Connection manager "WHSE"
Description: OCI error encountered. Error encountered while creating OCI environment
End Error
Error: 2016-04-03 10:34:52.99
Code: 0x0000020F
Source: Execute the Oracle SQL Oracle Source [74]
Description: The AcquireConnection method call to the connection manager WHSE failed with error code 0x80004005. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
End Error
WHSE is my Attunity Oracle connector connection name just as an FYI. It's also the name of my TNS. The SQL Server Agent runs under a domain\sqlagent account. I even logged on to the server as "domain\sqlagent" and executed the x32 DTExec commaind
line, it worked perfectly. So this service account clearly has enough permissions to run the job. I also see my Oracle x32 oracle home (C:\app\oracle\product\11.2.0\client_1\bin) as part of the PATH. I have read a lot of posts about ensuring the Oracle Home
is part of the PATH. Well it's there.
Again, I have successfully executed this SSIS using various methods BUT SQL Agent. I created a BAT file and ran it as Windows Scheduled Task. But I
can't get this to work in SQL Agent job running this same BAT file.
Can someone please help?
Thank you.
The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009
I have deployed my packages into Sql Server and I am using Configuration File. As my Data Source is Excel, I have changed the connection string during deployment with Server Path. But I am getting the following errors. Actually the File Exist in Path. May I know What is cause of the issue? Do I need to give any permission to execute the package.
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
component "Excel Source Service Contract Upload" (1) failed validation and returned error code 0xC020801C.
One or more component failed validation.
There were errors during task validation.
DTS_E_OLEDBERROR, Error Code: 0x80004005 Source: "MS JET DB Engine" Description : Path is not valid
Package execution
String value truncated over 255 character in mixed data type
Hi Folks,
I have a mixed data type column in excel and it contains (date, string and numeric value). For mixed data type data load I provided "IMEX=1"in the excel connection properties. Now we can see all the records but the string values are truncated if has more than 255 characters and it fails to load more than 255 characters.
Even when I tried "TypeGuessingRows=0" that also not worked for me. Please provide me any solution to avoid this truncation issue that might be helpful for me.
Importing data from excel with fields occasionally having more than 4000 characters
Hi Experts,
We are struggling with excel data import issue with fields occasionally having large text in it.
The text in the field is not always more than 4000 characters.
Initially we have changed the registry setting to read maximum number of rows in the excel to get the correct datatype of the fields, for long text. Also, have set the SSIS field length to read as long text.
It works fine as long as the excel has a record with long text.
However, not every import of the excel file would end up having the field length more than 4000 characters. Hence, the SSIS is failing every time the excel with no long text record.
This issue is driving us insane. If anyone can shed some light and provide suggestions would be saviour of the year for us(may be i should say first saviour of the year ;) ).
Thanks heaps in advance.
SSIS package Just fails...not compatible with this version of the DataFlow?
Executed as user: x ...0.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:27:08 AM Error: 2013-01-09 11:27:09.74 Code: 0xC0048020 Source: import file import file (DTS.Pipeline) Description: The version of component "Flat File Source" (1) is not compatible with this version of the DataFlow. End Error Error: 2013-01-09 11:27:09.75 Code: 0xC0048020 Source: import file DTS.Pipeline Description: The version of component "Flat File Source" (1) is not compatible with this version of the DataFlow. End Error Error: 2013-01-09 11:27:09.75 Code: 0xC004706C Source: import file DTS.Pipeline Description: Component "component "Data Conversion" (773)" could not be created and returned error code 0x80070005. Make sure that the component is registered correctly. End Error Error: 2013-01-09 11:27:09.75 Code: 0xC0048021 Source: import file Flat File Source [1]... The package execution fa... The step failed.
I am unsure what i am running into here.... Any ideas?
Launching SSDT "As a Different User" - concerns?
Fellow SSISers,
I am addressing some security challenges from my network team.
We are using SQL 2016 and SSDT for ssis development.
BELOW IS A DEVELOPMENT ENVIRONMENT SCENARIO!!!
Developers run the SSIS packges thru sql agent and that is using the SQL Agent account when the job runs. Works fine.
When they launch ssdt, they launch it as just like you and I. They sign on to the box with their domain id and open the packages on the drive. Alter and run their ssis package manually for testing there.
So obviously their domain id needs permissions to get to anything it needs – file shares and the like. Instead of altering a security pattern and give their domain ids access to certain shares that the package needs, security is asking if the developers can just launch ssdt “as a different user”. The different user would be likely the same account as the SQL Agent would use. That sql agent account is inhibited from being able to log into the box thru Remote desktop but it is obviously being used on the box to run sql agent so it should work. And it can be given access to other locations as needed.
Years ago, I thought that launching “as different user” could cause issues in that, at one time, I thought ssis did track the user that was altering the package and that got saved somewhere in the package metadata and/or security structure. That Id kind of became the owner of the package. it was a long time ago but I could be wrong on that.
Before we go spending effort in testing this out, I wanted to see if you think launching ssdt “as a different user” would cause an issue with the package itself. We are using package deployment model at this time.
Thanks MG.
Loading Fact Table using SSIS
Hello,
I am working on my first data warehouse project. I have a question regarding handling null values for FK's in the fact table. Currently I am using derived column to load all non matching records values with '-1' after the lookup's are done. My concern however is what happens if we find a matching surrogate key in the future doesn't it create duplicate records in the fact table ?
SSIS OData Source, PRIME OUTPUT FAILED
A package work fine in my local o in remote pc, but in Azure Pipeline dont work, they show me this message>
"SsisDBOperationGuid": "37d33190-6253-4404-bcfa-73855a3daa37", "SsisDBOperationId": 12, "OperationErrorMessages": "1/8/2020 4:29:15 PM+00:00 : Package1:Error: The OData was unable to process the data. Unable to connect to the remote server\r\n\n1/8/2020 4:29:15 PM +00:00 :Package1: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method onODatareturned error code 0xC02090F5. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.\r\n\n", "effectiveIntegrationRuntime": "integrationRuntime1 (West Europe)", "executionDuration": 237, "durationInQueue": { "integrationRuntimeQueue": 0 }
Thanks
Breakpoints Have Stopped Working
Good afternoon, all -
I have VS2015 and, for some reason, breakpoints in Script Tasks have stopped working. I've tried to find the Project Property setting to turn off Run64BitRuntime, as suggested in many of the hits I got when researching what's happening, but it's nowhere to be found. I recall setting this on an earlier version, but have, until now, not needed to do so in this one.
Breakpoints work fine on tasks in general, but not when they're with a script.
Is there something else I need to do to get these things working?
Thanx in advance for any assistance!
spatial join query is very slow - STContains(geometry::Point(long,lat,4283)
Hi Experts,
I have an update query as below.
ID columns are set as primary key. the SA3Dim table has spatial index on SP_Geometry field.
I forced the query to include the index. However, the query is very slow. To update a month data it takes over an hour and still running.
UPDATE SA3Table SET [SA3_Name] = SA3Dim.[Sa3_name16] FROM SA3Table AS main Join LUTDataTable as LUT on LUT.ID = main.ID JOIN [dbo].[SA3Dim] AS Voronoi WITH (INDEX (SIndex_SA3_Boundary_LatLong2_SP_GEOMETRY)) ON Voronoi.SP_GEOMETRY.STContains(geometry::Point(LUT.[PickupLongitude],LUT.[PickupLatitude],4283)) = 1 WHERE (LUT.[PickupLongitude] IS NOT NULL AND LUT.[PickupLatitude] IS NOT NULL)
Any idea how to improve the performance of this query?
Appreciate any inputs here. Thanks in advance.
Data Flow task long run with no ending ,while importing data from Excel to table in SSIS
Hi ,
I have excel file to be loaded through data flow task to a SQL Table.
There are around 10 columns (wich includes one vlookup column in the excel sheet(*.xls) ,which is not required by me ),in the excel sheet , i needed only 5 columns ,so i using the sql select command to select value from the sheet$ excel for result set in excel connection manager.
While loading the source file the data flow task is taking long run ,and analysis in depth it came to know it was in pre execute phase ,running abruptly for running long time.
scenario 1: when i remove the VLOOKUP column in excel sheet then the file is loading in fraction of seconds.
I dont know why the pre execute task is considering the VLOOKUP calculated columns ,since i am not querring that column in connection manager.
while excution i found that in the out put column "Package.dtsx is finished : cancelled"
Please help on this ,
GOVINDARAJ P
How to export data from SSIS source to Google SpreadSheet
Execute package in job agent delete all the records in the table
Hello everyone,
I have a package to update a table in data warehouse. The updates include adding, updating, and deleting. When I run the package through Visual Studio and integration services catalogs. It works fine. However, when I run this package in a scheduled job, it deletes all the records in the table even though there are not records need to be deleted.
I have been trying to solve this problem for a while, but no success. Any help would be greatly appreciated.
Thanks,
Xiaowen
Pass project parameter to package using PowerShell SMO
Using PowerShell & SMO I want to execute a child package that gets parameter values from it's parent.
So far I have this, see below, but get an error saying the parameter doesn't exist. I think it's because i'm passing it as a package parameter and not the parent parameter but can't find how to do it correctly.
Can anyone help with this?
$SSISServer = 'servername' $FolderName = 'DW_Exports' $ProjectName = 'ETL.Exports' $PackageName = 'MasterETL.dtsx' $sqlConnectionString = ` "Data Source=" + $SSISServer + ";Initial Catalog=master;Integrated Security=SSPI;" $sqlConnection = New-Object System.Data.SqlClient.SqlConnection $sqlConnectionString $SSISNamespace = "Microsoft.SqlServer.Management.IntegrationServices" $SSIS = New-Object $SSISNamespace".IntegrationServices" $sqlConnection $catalog = $SSIS.Catalogs["SSISDB"] $Project = $catalog.Folders[$FolderName].Projects[$ProjectName] $Project.Parameters $ssisPackage = $Project.Packages[$PackageName] $setValueParameters = New-Object 'System.Collections.ObjectModel.Collection[Microsoft.SqlServer.Management.IntegrationServices.PackageInfo+ExecutionValueParameterSet]'; $executionParameter = New-Object 'Microsoft.SqlServer.Management.IntegrationServices.PackageInfo+ExecutionValueParameterSet'; $executionParameter.ObjectType = 50; $executionParameter.ParameterName = "NetworkInternalCode" $executionParameter.ParameterValue = "abc"; $setValueParameters.Add($executionParameter); $ssisPackage.Execute("true", $null, $setValueParameters);
merger two results
Hi,
I have 2 queries to get the data from last year and this year. I need to compare and combine the results.
if the item exits in both, then get the latest one from this year (item bbb), Can you help please?