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

SSIS Package when deployed causes Datatype Mis-Match between unicode and non-Unicode data

$
0
0

The package runs with no errors in Visual Studio 2015 - I check the datatypes in the package and they all match. but when I deploy it - the package fails with data type mismatch. I am using SQL server 2016. The package is loading data between a Oracle and SQL Database.

Any Ideas ?

Thanks

What do I look for - to see if they are out of sync?


Excel 2013 Connection Manager: Microsoft.ACE.OLEDB.15.0 is not registered

$
0
0

I'm having an OLEDB provider issue in an SSIS package where the source file is an Excel 2013 64 bit file. The following is a breakdown of the environment I am working in:

OS: Windows Server 2012 R2 Standard 64 bit
Excel: 2013 64 bit
Visual Studio Community 2015 version 14.0.25425.01 Update 3
SQL Server 2016 Management Studio
SQL Server database instance is 2016(RTM) 13.0.1601.5 x64 Standard Edition

The problem has shown up in the SSIS package and with the Import/Export wizard. I have the 32 bit and 64 bit versions of the wizard. Using the 64 bit version, I have been able to import the worksheet I need from the Excel file into a table, without issues. The package I created was created from the Import/Export wizard.

The SSIS project's Run64BitRuntime property is set to 'true'. In the package, the Excel connection manager is configured to Excel 2013.  The package runs without issue, but when I try to view the columns from the Excel Source Editor, I cannot view the columns, and I receive the following error message:

'The requested OLE DB provider Microsoft.ACE.OLEDB.15.0 is not registered. I fthe 32-bit driver is not installed, run the package in 64-bit mode.'

In the research I've done, one idea to fix the issue was to install the 64 bit Microsoft Access Runtime. I've done this, but I still have the problem.

What other steps should I take?

Thank you for your help.

scheduled sql server agent job would not run?

$
0
0

I have created package under VS SSDT target to 64 -bit  sql server 2017.

I am able to run job from integration service catalogs but If I schedule it or run it fromSQL server Agent, it would not run.

I am running it as admin and role is Public and sysadmin.

I try to run this job as other role but it would say same message for all,

then I tried create proxy account and map that credential to user\admin that would not run either.

Error :

Executed as user. NT service\SQLSERVERAGENT sql server execute package utility version 14.0.1000 for 64 bit copy right 2017

Package execution IS server failed.

I also tried changing - Project properties to 32- bit and then deply and start job, did not run , and throw same error message.


chipsy

Azure SSIS Runtime version?

$
0
0

Straight from this documentation (docs microsoft dot com/create-azure-ssis-integration-runtime), it states "When you provision an instance of Azure-SSIS IR, the Azure Feature Pack for SSIS and the Access Redistributable are also installed". 

Has anyone had any luck exeucting a pipeline with the  Azure Blob Source component? If so, what version of the cloud components are you leveraging?

Does anyone know what version of the Azure Feature Pack is installed on Azure SSIS Integration Runtime?

Here's our error message: 

Fill TempTable from File:Error: The managed pipeline component "Microsoft.SqlServer.IntegrationService.CloudComponents.Source.AzBlobSrc, Microsoft.SqlServer.IntegrationService.CloudComponents, Version=13.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" could not be loaded.  The exception was: Could not load file or assembly 'Microsoft.SqlServer.IntegrationService.CloudComponents, Version=13.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Azure SSIS Runtime Feature Pack version?

$
0
0

Straight from this documentation (docs microsoft dot com/create-azure-ssis-integration-runtime), it states "When you provision an instance of Azure-SSIS IR, the Azure Feature Pack for SSIS and the Access Redistributable are also installed". 

Has anyone had any luck executing an SSIS package from Data Factory with the  Azure Blob Source component? If so, what version of the cloud components are you leveraging?

Does anyone know what version of the Azure Feature Pack is installed on Azure SSIS Integration Runtime?

Here's our error message: 

Fill TempTable from File:Error: The managed pipeline component "Microsoft.SqlServer.IntegrationService.CloudComponents.Source.AzBlobSrc, Microsoft.SqlServer.IntegrationService.CloudComponents, Version=13.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" could not be loaded.  The exception was: Could not load file or assembly 'Microsoft.SqlServer.IntegrationService.CloudComponents, Version=13.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.



SSIS Flat File Import : "Table or view - Fast load" Option Error

$
0
0

Hi,

While Importing a flat file containing 151 columns to SQL Database we are getting an exception.

"SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x8007000E.

An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x8007000E  Description: "Not enough storage is available to complete this operation."

Failed to open a <g class="gr_ gr_133 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling" data-gr-id="133" id="133">fastloadrowset</g> for "[dbo].[TestTable]". Check that the object exists in the database."

When columns reduced 131 in SQL it's working. Is it a limitation of SSIS <g class="gr_ gr_272 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="272" id="272">dataaccess</g> mode "Table or view  - Fast load" option.

Thanks,

Arun


Running SSIS as an Agent job using a proxy

$
0
0

Hello,
 I built a simple SSIS package using BIDS.

The package does a backup of a DB to a network share.
I imported the dtsx file into SQL Server using SQL Server WB (connected to the SSIS server)

I created a SQL Agent job to run the SSIS package.

I have created a credential that maps to a domain account (BackupUser1). The domain account has access to the network share: I verified it by running a command line using the Run As and accessing the network share as that user.

Of course, I have a sql agent proxy associated to the credentials which is assigned to run the job step that executes the SSIS package.
When the job runs it fails because of access denied to the network share.
To see what actually happened, I changed the permissions and the share (and the NTFS permissions) to allow R/W access to 'everyone'.

I re-scheduled the job and this time it succeeds. I went over to the backup file that was created when the SSIS package executed and discovered that the owner (i.e. the creator) of the file is not the domain account (BackupUser1), rather it's the data base server computer account name DBSRV$
this means that SQL Server Agent didn't impersonate the account defined by the SQL Agent proxy.

I looked for information and wasn't able to find an answer...
A couple of things I made in the local security policy (user rights assignment):
allowed the specified domain account the permission to log-on as a batch job
allowed the SYSTEM principal (the agent runs under LocalSystem) to replace process level token (i.e. impersonate, at least as I understand this user right)

Any thoughts, suggestion on why SQL Server Agent doesn’t actually use the credentials associated with the proxy account to access the network share?

Thanks,
Asher

The 'OraOLEDB.Oracle.1' provider is not registered on the local machine.

$
0
0

Hi,

I am creating a SSIS package for which uses oracle provider for OLEDB.

Where as it's throwing an error when testing the connection. Please find the below error..

Test connection failed because of an error in initializing provider. The 'OraOLEDB.Oracle.1' provider is not registered on the local machine.

SSIS is on server1 and Oracle is on Server2.

Do u i need do anything with TNSNAMES.ORA file?? If yes, in which server??

Thanks

Bhanu


Renaming File with DatetimeStamp

$
0
0

Hi All,

    I am using Visual Studio 2015. While moving the files from source to destination i want to rename the files with datetimestamp. I have csv files . I have added expression as

@[User::ArchiveFolderPath]+ @[User::Fname]+ 
(DT_STR,4,1252)DATEPART( "yyyy" , getdate() ) + RIGHT("0" + (DT_STR,4,1252)DATEPART( "mm" , getdate() ), 2) + RIGHT("0" + (DT_STR,4,1252)DATEPART( "dd" , getdate() ), 2) +".csv"

While applying Evaluate expression i am getting filenamewithdate.csv. While transferring i am getting filename as

Accounts.csv20181218. I need to get the filename as Accounts20181218.csv and Fname value is Accounts. Please let me know if i miss any thing.

Please guide me on this.

Generate Dynamic column based on SQL output

$
0
0

I have source data i.e. is present in SQL like below

Product CodeItem IDItem DescriptionCustomer NameMonth of OrderQty Ordered
10125Food ItemsHanaJan-01-201820
10125Food ItemsHanaFeb-01-201824
10125Food ItemsHanaMar-01-201844


Expected output is when I run at Feb month,this output required in excel

 

    Product CodeItem ID    Item DescriptionCustomer NameJan-18
10125  Food ItemsHana20

Expected output is when I run at Mar month  

Product CodeItem ID Item DescriptionCustomer NameJan-18             Feb
10125    Food ItemsHana2024

Expected output is when I run at Apr month  

Product CodeItem IDItem DescriptionCustomer NameJan-18                 Feb         Mar
10125    Food ItemsHana202444


I need to generate columns dynamically Jan-18,Feb-18,etc.

Like that need to get output in Excel from SQL like above.

Could you please any one help me for this scenario.I hope any one person will help?

Regards,

Niranjan B

Migrating from SQL2012 to SQL2016 - Issues when Programmatically Generating SSIS Data Flows

$
0
0

We have an SSIS application running successfully using SQL Server 2012 and Visual Studio 2012 in which a SSIS Script Task (Visual Basic 2012) is utilised to programmatically generate SSIS packages with Data Flow tasks and execute these. We now face issues when migrating from SQL Server 2012 to SQL Server 2016. We are out of ideas and would be grateful for any suggestions. The problem has been distilled down to the following simple SSIS Package with one Script Task and one Connection Managers entry for localhost.

================== Script Code - Start ==========================

#Region"Imports"

Imports System

Imports System.Data

Imports System.Math

Imports Microsoft.SqlServer.Dts.Runtime

#EndRegion

<Microsoft.SqlServer.Dts.Tasks.ScriptTask.SSISScriptTaskEntryPointAttribute()>

<System.CLSCompliantAttribute(False)>

PartialPublicClassScriptMain

   Inherits Microsoft.SqlServer.Dts.Tasks.ScriptTask.VSTARTScriptObjectModelBase

   PrivateFunction AddConnection(ByRef p AsPackage,ByVal cmAsConnectionManager)AsConnectionManager

       Dim newCMAsConnectionManager = p.Connections.Add(cm.CreationName)

       newCM.Name = cm.Name

       newCM.ConnectionString = cm.ConnectionString

       Return newCM

   EndFunction

   PublicSub Main()

       ''

       '' instantiate runtime application and package

       ''

       Dim appAsApplication =NewApplication()

       Dim pAsPackage =NewPackage()

       p.Name = "SSIS Dynamic DataFlow Example"

       p.PackageType = DTSPackageType.DTSDesigner100

       p.VersionBuild = 1

       ''

       '' Add DataFlow Task to package

       ''

       Dim eAsExecutable = p.Executables.Add("STOCK:PipelineTask")

       Dim mainTaskHostAsTaskHost =CType(e,TaskHost)

       Dim dataFlowTaskAsMainPipe =CType(mainTaskHost.InnerObject,MainPipe)

       mainTaskHost.Name = "Main Data Flow"

       ''

       ' Source Connection - Use this package's Connection Managers Connection called "LocalHost"

       '

       Dim LocalSrceAsConnectionManager = AddConnection(p, Dts.Connections("LocalHost"))

       '

       Dim sourceDBAsIDTSComponentMetaData100 = dataFlowTask.ComponentMetaDataCollection.New

       '  sourceDB.Name = "SourceDatabase"

       sourceDB.Name = "SourceDB"

       '    sourceDB.ComponentClassID = "DTSAdapter.OleDbSource"

       sourceDB.ComponentClassID = "{165A526D-D5DE-47FF-96A6-F8274C19826B}"       ' Ref: //msdn.microsoft.com/en-us/library/gg587414(v=sql.105).aspx

       '

       ' Initialise the component and assign connection manager

       '

       Dim sourceInstanceAsCManagedComponentWrapper = sourceDB.Instantiate

       sourceInstance.ProvideComponentProperties()

       sourceDB.RuntimeConnectionCollection(0).ConnectionManagerID = LocalSrce.ID

   EndSub

#Region"ScriptResults declaration"

   EnumScriptResults

       Success = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Success

       Failure = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Failure

   EndEnum

#EndRegion

EndClass

================== Script Code - End ==========================

The script fails on the following statement:

sourceInstance.ProvideComponentProperties()     

Failure:{"Exception from HRESULT: 0xC0048021"}

When drilling into the sourceInstance variable value the following error is seen:

{System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "".

   --- End of inner exception stack trace ---

   at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)

   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)

   at System.Dynamic.IDispatchComObject.GetMembers(IEnumerable`1 names)}

The References that are in place are:

Microsoft.SqlServer.DTSPipelineWrap

               C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.SqlServer.DTSPipelineWrap\v4.0_13.0.0.0__89845dcd8080cc91\Microsoft.SQLServer.DTSPipelineWrap.dll

Microsoft.SqlServer.ManagedDTS

               C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.SqlServer.ManagedDTS\v4.0_13.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.ManagedDTS.dll

Microsoft.SqlServer.ScriptTask

               E:\Program Files (x86)\Microsoft SQL Server\130\DTS\Tasks\Microsoft.SqlServer.ScriptTask.dll

System

               C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.dll

System.Data

               C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Data.dll

System.Windows.Forms             

               C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Windows.Forms.dll

System.Xml

               C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Xml.dll

error when creating table fast load for ms access

$
0
0

hi,

i created package in which data is loaded from sql server 2016 to ms access 2016 and it works ok for small amount of data.

now i have to load 2+ million of records and this way is very very slow so i tried to change in my ole db destination data access mode to "table or view - fast load" but i get this error:

Exception from HRESULT: 0xC0202040
Error at Data Flow Task [OLE DB Destination [2]]: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available.  Source: "Microsoft Office Access Database Engine"  Hresult: 0x80040E21  Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".

Error at Data Flow Task [OLE DB Destination [2]]: Failed to open a fastload rowset for "Smanjenja_i_iskljucenja". Check that the object exists in the database.

my package data flow looks like this:

destination (ms access) connection manager "connSmanjenjaAcc":

and when I change to fast load error is thrown as mentioned above:

could someone tell me what am i doing wrong ?

Visual Studio 2008 crashes on SSIS Data Flow Task opening

$
0
0
Hi,

Visual Studio 2008 crashes on SSIS Data Flow Task opening.
This is a random behavior on random SSIS packages on Data Flow Task opening on packages that I’ve finished developing last week. The packages does not executes with error.

Error Description from Event Viewer:
Faulting application devenv.exe, version 9.0.30729.1, stamp 488f2b50, faulting module msdds.dll, version 9.0.30729.1, stamp 488f2e31, debug? 0, fault address 0x00012b6a.

I'm runnig SSIS development against SQL SERVER 2008 ENT 64.

There is already a fix for this ?




My environment description:
Microsoft Visual Studio 2008
Version 9.0.30729.1 SP
Microsoft .NET Framework
Version 3.5 SP1
Installed Edition: Professional

Microsoft Visual Basic 2008 91605-270-4167253-60984
Microsoft Visual Basic 2008
Microsoft Visual C# 2008 91605-270-4167253-60984
Microsoft Visual C# 2008
Microsoft Visual Studio 2008 Tools for Office 91605-270-4167253-60984
Microsoft Visual Studio 2008 Tools for Office
Microsoft Visual Web Developer 2008 91605-270-4167253-60984
Microsoft Visual Web Developer 2008
Crystal Reports    AAJ60-G0MSA4K-68000CF
Crystal Reports Basic for Visual Studio 2008
+
KB944899, KB945282, KB946040, KB946308, KB946344, KB946581, KB947171, KB947173, KB947180, KB947180, KB947180, KB947540, KB947789, KB948127, KB953256, KB971091, KB973674, KB972222
SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 10.0.1600.22

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 10.0.1600.22 ((SQL_PreRelease).080709-1414 )

SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 10.0.1600.22

Execute SQL component failing when using OLE DB connection manager

$
0
0

Hi There, 

Can anyone out there shed some light on why an Execute SQL Task would fail when using an OLE DB connection manager ?

I am using SQL server 2014 and it seems I am missing something.

Any help would be much appreciated.

Thank you.




SSIS Fuzzy Lookup. No Columns are displayed

$
0
0

My Data Flow is very simple. I have an OLE DB linked to a fuzzy Lookup. When I set up the OLE DB connection in the fuzzy lookup I am able to select my reference table. When I click on the columns tab there are no available columns. 

If anyone have solution ...please help???@ " shyamthakur679@gmail.com"

https://social.msdn.microsoft.com/Forums/getfile/1372339


ODBC Destination batch load into HIVE Table

$
0
0
Hello, everyone. I am attempting to port an SSIS package from DB2 to HIVE. I am having an issue with the ODBC Destination task using the Hortonworks HIVE ODBC. I previously tried the Microsoft ODBC but that failed to create a valid insert query.

The problem:
I have a data flow task with an OLE DB Source(DB2) and a ODBC Destination(Hive). If I set the ODBC Destination to 'Row-by-row' then the load completes as expected. However, if I set it to 'Batch' then I only receive the following error:

Error: 0x384 at Push Tokens to HIVE, ODBC Destination [2]: Open Database Connectivity (ODBC) error occurred. SQLExecute returned error while inserting row 1

I have attached the ODBC trace from the problematic task. I expected to see a SQLExecute SQL_ERROR in the trace but that seems to be missing.

DtsDebugHost    1e9c-2488	ENTER SQLPrepareW 
		HSTMT               0x08D45108
		WCHAR *             0x0583CEE4 [      86] "INSERT INTO `default`.`temp_000000000000_return` ( `link_id`,`tok_data`) VALUES (?, ?)"
		SDWORD                    86

DtsDebugHost    1e9c-2488	EXIT  SQLPrepareW  with return code 0 (SQL_SUCCESS)
		HSTMT               0x08D45108
		WCHAR *             0x0583CEE4 [      86] "INSERT INTO `default`.`temp_000000000000_return` ( `link_id`,`tok_data`) VALUES (?, ?)"
		SDWORD                    86

DtsDebugHost    1e9c-2488	ENTER SQLSetStmtAttrW 
		SQLHSTMT            0x08D45108
		SQLINTEGER                  21 <SQL_ATTR_PARAMS_PROCESSED_PTR>
		SQLPOINTER          0x057D8578
		SQLINTEGER                   0 

DtsDebugHost    1e9c-2488	EXIT  SQLSetStmtAttrW  with return code 0 (SQL_SUCCESS)
		SQLHSTMT            0x08D45108
		SQLINTEGER                  21 <SQL_ATTR_PARAMS_PROCESSED_PTR>
		SQLPOINTER          0x057D8578
		SQLINTEGER                   0 

DtsDebugHost    1e9c-2488	ENTER SQLSetStmtAttrW 
		SQLHSTMT            0x08D45108
		SQLINTEGER                  20 <SQL_ATTR_PARAM_STATUS_PTR>
		SQLPOINTER          0x084B4158
		SQLINTEGER                   0 

DtsDebugHost    1e9c-2488	EXIT  SQLSetStmtAttrW  with return code 0 (SQL_SUCCESS)
		SQLHSTMT            0x08D45108
		SQLINTEGER                  20 <SQL_ATTR_PARAM_STATUS_PTR>
		SQLPOINTER          0x084B4158
		SQLINTEGER                   0 

DtsDebugHost    1e9c-2488	ENTER SQLBindParameter 
		HSTMT               0x08D45108
		UWORD                        1 
		SWORD                        1 <SQL_PARAM_INPUT>
		SWORD                      -16 <SQL_C_SLONG>
		SWORD                        4 <SQL_INTEGER>
		SQLULEN                   10
		SWORD                        0 
		PTR                0x08316178
		SQLLEN                     4
		SQLLEN *            0x08315F98

DtsDebugHost    1e9c-2488	EXIT  SQLBindParameter  with return code 0 (SQL_SUCCESS)
		HSTMT               0x08D45108
		UWORD                        1 
		SWORD                        1 <SQL_PARAM_INPUT>
		SWORD                      -16 <SQL_C_SLONG>
		SWORD                        4 <SQL_INTEGER>
		SQLULEN                   10
		SWORD                        0 
		PTR                0x08316178
		SQLLEN                     4
		SQLLEN *            0x08315F98 (137452312)

DtsDebugHost    1e9c-2488	ENTER SQLBindParameter 
		HSTMT               0x08D45108
		UWORD                        2 
		SWORD                        1 <SQL_PARAM_INPUT>
		SWORD                       -8 <SQL_C_WCHAR>
		SWORD                       -8 <SQL_WCHAR>
		SQLULEN                   35
		SWORD                        0 
		PTR                0x057F85C8
		SQLLEN                    72
		SQLLEN *            0x08315FB8

DtsDebugHost    1e9c-2488	EXIT  SQLBindParameter  with return code 0 (SQL_SUCCESS)
		HSTMT               0x08D45108
		UWORD                        2 
		SWORD                        1 <SQL_PARAM_INPUT>
		SWORD                       -8 <SQL_C_WCHAR>
		SWORD                       -8 <SQL_WCHAR>
		SQLULEN                   35
		SWORD                        0 
		PTR                0x057F85C8
		SQLLEN                    72
		SQLLEN *            0x08315FB8 (137452312)

DtsDebugHost    1e9c-2c5c	ENTER SQLExecute 
		HSTMT               0x08D45108

DtsDebugHost    1e9c-2c5c	EXIT  SQLExecute  with return code 0 (SQL_SUCCESS)
		HSTMT               0x08D45108

DtsDebugHost    1e9c-2c5c	ENTER SQLGetDiagRecW 
		SQLSMALLINT                  3 <SQL_HANDLE_STMT>
		SQLHANDLE           0x08D45108
		SQLSMALLINT                  1 
		SQLWCHAR *          0x0927EFA0
		SQLINTEGER *        0x0927D784
		SQLWCHAR *          0x0927DF98 
		SQLSMALLINT               1024 
		SQLSMALLINT *       0x0927D788

DtsDebugHost    1e9c-2c5c	EXIT  SQLGetDiagRecW  with return code 100 (SQL_NO_DATA_FOUND)
		SQLSMALLINT                  3 <SQL_HANDLE_STMT>
		SQLHANDLE           0x08D45108
		SQLSMALLINT                  1 
		SQLWCHAR *          0x0927EFA0
		SQLINTEGER *        0x0927D784
		SQLWCHAR *          0x0927DF98 
		SQLSMALLINT               1024 
		SQLSMALLINT *       0x0927D788

DtsDebugHost    1e9c-2488	ENTER SQLFreeHandle 
		SQLSMALLINT                  3 <SQL_HANDLE_STMT>
		SQLHANDLE           0x08D45108

DtsDebugHost    1e9c-2488	EXIT  SQLFreeHandle  with return code 0 (SQL_SUCCESS)
		SQLSMALLINT                  3 <SQL_HANDLE_STMT>
		SQLHANDLE           0x08D45108

DtsDebugHost    1e9c-2488	ENTER SQLDisconnect 
		HDBC                0x0254EBD8

DtsDebugHost    1e9c-2488	EXIT  SQLDisconnect  with return code 0 (SQL_SUCCESS)
		HDBC                0x0254EBD8

DtsDebugHost    1e9c-2488	ENTER SQLFreeHandle 
		SQLSMALLINT                  2 <SQL_HANDLE_DBC>
		SQLHANDLE           0x0254EBD8

DtsDebugHost    1e9c-2488	EXIT  SQLFreeHandle  with return code 0 (SQL_SUCCESS)
		SQLSMALLINT                  2 <SQL_HANDLE_DBC>
		SQLHANDLE           0x0254EBD8

DtsDebugHost    1e9c-2488	ENTER SQLFreeHandle 
		SQLSMALLINT                  1 <SQL_HANDLE_ENV>
		SQLHANDLE           0x0254E748

DtsDebugHost    1e9c-2488	EXIT  SQLFreeHandle  with return code 0 (SQL_SUCCESS)
		SQLSMALLINT                  1 <SQL_HANDLE_ENV>
		SQLHANDLE           0x0254E748


SSIS Project Build Failure - FileNotFoundException

$
0
0

I have an SSIS project that has several packages. I built two SSIS packages in the project as a couple of test packages. I eventually didn't need them.

I deleted the packages from the project and permanently deleted them.

Now when trying to build the project, SSIS is STILL trying to find these packages that were deleted!

I did a "Find in Files" and the package name is not anywhere in the project. 

I have no idea where SSIS is even getting this package name from - it doesn't exist anywhere in the project directory.

I've done a restart a dozen times, I've tried rebuild 100 times and every time it fails looking for a nonexistent package.

Has anyone else encountered this?


A. M. Robinson

Any way to determine if there is a result set in a Data Flow?

$
0
0

Is there any way in my Data Flow to determine if my SQL Server Stored Procedure produces an empty file...No result set? Like I have no orders for that client today...so abort and end the job without writing out an empty file...or do I have to somehow control this behavior in the Control Flow?

Thanks for your review and am hopeful for a reply.

XML Data Loading - Issue

$
0
0

Hi,

SQL Server:

Microsoft SQL Server 2014 (SP2-GDR) (KB4019093) - 12.0.5207.0 (X64)
 Jul  3 2017 02:25:44
 Copyright (c) Microsoft Corporation
 Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

Windows :

Windows Server 2012 R2 Standard Edition 6b bit

Clustering is being Used

We have Xml Data Stored in a SQL Server database (TEST_Source) and want to load the data into another SQL Server database(Test_Destination) on the same Server.

Error Message:

Error Message:

Started:  11:48:41 AM
Error: 2018-11-29 12:07:39.81
   Code: 0x80070070
   Source: DST_Table_Archive
   Description:
End Error
Error: 2018-11-29 12:07:40.05
   Code: 0xC0208266
   Source: DST_Table_Archive
   Description:
End Error
Error: 2018-11-29 12:07:40.27
   Code: 0xC0208265
   Source: DST_Table_Archive OLEDB_Src_tTable_Source [111]
   Description: Failed to retrieve long data for column "Output".
End Error
Error: 2018-11-29 12:07:40.50
   Code: 0xC020901C
   Source: DST_Table_Archive OLEDB_Src_tTable_Source [111]
   Description: There was an error with OLEDB_Src_tTable_Source.Outputs[OLE DB Source Output] on OLEDB_Src_tTable_Source. The column status returned was: "DBSTATUS_UNAVAILABLE".
End Error
Error: 2018-11-29 12:07:40.73
   Code: 0xC0209029
   Source: DST_Table_Archive OLEDB_Src_tTable_Source [111]
   Description: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.  The "OLEDB_Src_tTable_Source.Outputs[OLE DB Source Output]" failed because error code 0xC0209071 occurred, and the error row disposition on "OLEDB_Src_tTable_Source" specifies failure on error. An error occurred on the specified object of the specified component.  There may be error messages posted before this with more information about the failure.
End Error
Error: 2018-11-29 12:07:40.96
   Code: 0xC0047038
   Source: DST_Table_Archive SSIS.Pipeline
   Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on OLEDB_Src_tTable_Source returned error code 0xC0209029.  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.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started:  11:48:41 AM
Finished: 12:12:32 PM
Elapsed:  1430.55 seconds

Thank You,

Visual Studio 2017 SSIS: Orcale as Source

$
0
0

Hi,

I need to develop a SSIS package to load the data from oracle source and post the files on Azure Data lake.

For that, I am using VS 2017. But I am not able to create the successful connection with oracle db. could you please guide what is the correct procedure or is there any tutorial for making successful connection?

Thanks in advance.

Regards,

Gohar

Viewing all 24688 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>