May 26, 2011 at 3:14 pm
I get a warning when executing a package.
Does anyone have any idea what I'm missing?
- Executing (Warning)
Messages
Warning: Preparation SQL Task 1: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. (SQL Server Import and Export Wizard)
Warning: Preparation SQL Task 1: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. (SQL Server Import and Export Wizard)
List are the results of the report:
The execution was successful
- Initializing Data Flow Task (Success)
- Initializing Connections (Success)
- Setting SQL Command (Success)
- Setting Source Connection (Success)
- Setting Destination Connection (Success)
- Validating (Success)
- Prepare for Execute (Success)
- Pre-execute (Success)
- Executing (Warning)
Messages
Warning: Preparation SQL Task 1: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. (SQL Server Import and Export Wizard)
Warning: Preparation SQL Task 1: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. (SQL Server Import and Export Wizard)
- Copying to `London` (Success)
120 rows transferred
- Post-execute (Success)
Messages
Information 0x4004300b: Data Flow Task 1: "component "Destination - London" (22)" wrote 120 rows.
(SQL Server Import and Export Wizard)
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
May 26, 2011 at 5:17 pm
I hate to post a "didja plug it in?!" answer, but seriously - have you tried recreating the OLE DB connection? I've often found that when I get bizarre, non-sensical results from SSIS, you have to jog its memory a little.
May 27, 2011 at 12:33 pm
coronaride (5/26/2011)
I hate to post a "didja plug it in?!" answer, but seriously - have you tried recreating the OLE DB connection? I've often found that when I get bizarre, non-sensical results from SSIS, you have to jog its memory a little.
Thanks.
It has been a few years but I exported from the same table from SQL Server 2005 and I did not have any issues.
When I go to edit mapping in SQL Server 2008 R2 I get warning symbols on each column.
Someone initially imported this table from Excel and it created an ugly table structure and all of the columns are NVARCHAR(255).
There are warning symbols on all of the columns except for the column that I excluded in the transformation.
I have experimented with the data types, etc but I still get the warning but I can't come up with a datatype that does not give me a warning on the column.
Regards.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply