September 19, 2009 at 7:04 am
I have a problem when executing a job which contains a dtsc package. The package i created is an import data where a flat file source (txt file on the same server as our sql server) is imported in a table. When I execute the dtsx package or the job, i receive an error.
Code: 0xC00470FE Source: Data Flow Task DTS.Pipeline Description: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Source - EXPORT_SPE_txt" (1). End Error DTExec: The package execution returned DTSER_FAILURE (1)
Our SQL server is a Workgroup Edition and the OS is Windows Server 2003 SE SP2.
I also already created the Credential and the proxy.
Does anyone know why I receive this error?
September 19, 2009 at 10:50 am
The error message is self-descriptive:
The product level is insufficient for component
You don't have SQL Server Integration Services (SSIS) installed, but Database Services have limitation to ran SSIS packages.
One of these limitations related to import data from flat file.
So, install SSIS on a server (and apply service packs).
September 19, 2009 at 12:34 pm
Sergey Vavinskiy (9/19/2009)
The error message is self-descriptive:The product level is insufficient for component
You don't have SQL Server Integration Services (SSIS) installed, but Database Services have limitation to ran SSIS packages.
One of these limitations related to import data from flat file.
So, install SSIS on a server (and apply service packs).
Incorrect..
SSIS is not a supported feature in the workgroup version.. Only import/export..
See:
http://www.microsoft.com/sqlserver/2005/en/us/compare-features.aspx
CEWII
September 19, 2009 at 2:18 pm
Elliott is correct.
But I was correct too in my diagnosis.
SQL Server can run SSIS packages regardless of edition and using just the Database Services' DTEXEC.exe executable for that.
That is correct about Workgroup edition as well.
According to Books Online, these SSIS features are supported in Workgroup Edition:
o SQL Server Import and Export Wizard with the Execute SQL task and basic sources, transformations, and destinations
o Integration Services runtime
o Integration Services API and object model
The problem is, as I said, this way is very limited and you can run only simple packages that provide very basic import/export operations without any data transformations and without flat file connections.
In a Standard and Enterprise editions this limitations can be overrideded by installing Integration Services. But since Workgroup edition doesn't support SSIS, it is not a solution.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply