This is an integrated component OLE DB Destination. There is no any Output section:
... and here is the Devart MySQL Destination. There is an Output section (and cannot be manually deleted and because is last in the flow, the system generates the warning).:
Search found 6 matches
- Wed 05 May 2021 21:32
- Forum: SSIS Data Flow Components
- Topic: Removing this unused output column
- Replies: 6
- Views: 22018
- Wed 05 May 2021 21:18
- Forum: SSIS Data Flow Components
- Topic: Removing this unused output column
- Replies: 6
- Views: 22018
Re: Removing this unused output column
Yes, that is true ... for the SOURCE component. But the problem is with the DESTINATION component.
In my case, Dataflow has two components OLE DB Source and Devart MySQL Destination. All fields from the Source output are mapped to destination fields, there is not any unused field. And Destination component is the last component in the flow. Even this fact, the destination component has then output column and this column generate this warning. When I used the integrated OLE DB Destination component (slow, I rather use your Devart component), there is no output column.
In the rare case can be useful to have an output column even on the destination component (eg. chain) but ordinary is the destination final component.
My Source components are optimized for reading only fields, which are necessary for data transfer. I transfer gigabytes and I need high speed. Second important thing is to have validated data, so I regularly (mostly by script) check event logs for problems. That's the reason I need to have logs without warnings.
In my case, Dataflow has two components OLE DB Source and Devart MySQL Destination. All fields from the Source output are mapped to destination fields, there is not any unused field. And Destination component is the last component in the flow. Even this fact, the destination component has then output column and this column generate this warning. When I used the integrated OLE DB Destination component (slow, I rather use your Devart component), there is no output column.
In the rare case can be useful to have an output column even on the destination component (eg. chain) but ordinary is the destination final component.
My Source components are optimized for reading only fields, which are necessary for data transfer. I transfer gigabytes and I need high speed. Second important thing is to have validated data, so I regularly (mostly by script) check event logs for problems. That's the reason I need to have logs without warnings.
- Mon 03 May 2021 14:34
- Forum: SSIS Data Flow Components
- Topic: Removing this unused output column
- Replies: 6
- Views: 22018
Re: Removing this unused output column
Thanks for the reply...
I understand that the behavior is the same as in the PostgreSQL component. But when I have no connection from the Destination component to the next component in the flow, I suppose that I will not receive any similar warning message.
I have quite a lot of tasks build in SSIS and I try to have zero number of warnings. This component generates me full log of these warnings and I can lose another important message.
I understand that the behavior is the same as in the PostgreSQL component. But when I have no connection from the Destination component to the next component in the flow, I suppose that I will not receive any similar warning message.
I have quite a lot of tasks build in SSIS and I try to have zero number of warnings. This component generates me full log of these warnings and I can lose another important message.
- Mon 03 May 2021 10:10
- Forum: SSIS Data Flow Components
- Topic: Removing this unused output column
- Replies: 6
- Views: 22018
Removing this unused output column
I'm using the Devart Mysql Destination component. From time to time this component automatically fills output columns property. Manually is possible to remove this property from Output\External Columns, but removing the property from Output\Output columns ends with error message:
Pipeline component has returned HRESULT error code 0xC020800F from a method call.
I try to remove these output properties because of the generation warning message in the SSIS log:
The output column "CF" (27) on output "Output" (26) and component "Devart MySql Destination" (2) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
... and all warnings are sent to my email for the fix. So please fix this behavior or at least write me, how can I fix it manually...
Thanx
Jan
Pipeline component has returned HRESULT error code 0xC020800F from a method call.
I try to remove these output properties because of the generation warning message in the SSIS log:
The output column "CF" (27) on output "Output" (26) and component "Devart MySql Destination" (2) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
... and all warnings are sent to my email for the fix. So please fix this behavior or at least write me, how can I fix it manually...
Thanx
Jan
- Mon 03 May 2021 09:11
- Forum: dbForge for MySQL
- Topic: Support for Sphinx and Manticora
- Replies: 5
- Views: 8585
Support for Sphinx and Manticora
dbForge for Mysql has the ability to run SQL scripts for Sphinx and Manticore engines. But in the comparison with your competition (EMS ...), there is no option to show FACET results. For example next script:
SELECT *
FROM company
FACET location_code
ORDER BY COUNT(*) DESC
your competition display on two tabs. Main result on first and the result of the facet on the second tab. dbForge displays just the main result. You have the ability to display more SQL queries on separate tabs, so I will be glad if you implement the same functionality for these engines.
SELECT *
FROM company
FACET location_code
ORDER BY COUNT(*) DESC
your competition display on two tabs. Main result on first and the result of the facet on the second tab. dbForge displays just the main result. You have the ability to display more SQL queries on separate tabs, so I will be glad if you implement the same functionality for these engines.
- Thu 22 Apr 2010 12:38
- Forum: SQL Server Data Access Components
- Topic: Unassigned in OUTPUT parameter
- Replies: 1
- Views: 1453
Unassigned in OUTPUT parameter
I decide to convert my db engine from ADO to SDAC. I realized different behavior of returned OUTPUT parameters from stored procedures. In this case, returned value of AIUD variable was NULL in ADO engine, but Unassigned in SDAC. I can fix it directly in this place, but these places in my code are really frequent. Where is the problem?
here is the code in Delphi2010 (TlLowStoredProc is successor of TMSStoredProc, AUID is OleVariant):
and here is the stored procedure in MSSQL 2005/2008:
here is the code in Delphi2010 (TlLowStoredProc is successor of TMSStoredProc, AUID is OleVariant):
Code: Select all
LStored := TlLowStoredProc.Create(nil);
try
try
with LStored do
begin
StoredProcName := sSP_LoginUser;
Connection := AConnection;
PrepareSQL;
ParamByName(sSP_ALogin).Value := ALogin;
ParamByName(sSP_APass).Value := APass;
ParamByName(sSP_AUID).Value := Null;
ExecProc;
AUID := ParamByName(sSP_AUID).Value;
Result := ParamByName(AConnection.ReturnField).Value;
end;
except
end;
finally
LStored.Free;
end
Code: Select all
CREATE PROCEDURE DSP_LoginUser
@ALogin nvarchar(50),
@APass nvarchar(50),
@AUID uniqueidentifier OUTPUT
AS
SET NOCOUNT ON
SET @AUID = NULL
SELECT @AUID = User.UID
FROM dbo.User
WHERE User.LOGIN = @ALogin AND User.PASS= @APass AND User.DELETED = 0
RETURN (@@ERROR)