(newbie) - Stored Procedure Problem

Can anyone tell me what is wrong with this stored procedure?

CREATE PROCEDURE [dbo].[AddGroupPermission]
@.Perm varchar(16)
AS
ALTER TABLE tblUserGroups ADD @.Perm VARCHAR(1) NULL
GO

When I click on Check Syntax, I get 'Error 170 - Line 4: Incorrect syntax near @.Perm'

I have checked the syntax for the ALTER command, and it looks correct to me...

This is my first day at using SQL Server in anger, so any help appreciated :)You must use dynamic sql for that, check out :

http://www.sqlteam.com/item.asp?ItemID=4599

The following will work

CREATE PROCEDURE [dbo].[AddGroupPermission]
@.Perm varchar(16)
AS
exec ('ALTER TABLE tblUserGroups ADD ' + @.Perm + 'VARCHAR(1) NULL')
GO|||Oh wow! Thanks for that - I didn't even know you could do that directly in SQL server - I'm used to doing it in ASP pages, of course, but this DB is new to me :)

I'm off to check your link now - thanks very much for taking the time to post.

Mark.sql

(GUID problem) What is wrong with this code ?

Hi, just learning SQL2000.
I have this code:
mSQL = "UPDATE Contactpersonen SET Naam=? WHERE ContactpersoonID=?"
Command = New SqlClient.SqlCommand(mSQL, C_CP)
Command.Parameters.Add("Naam", txtNaam.Text)
Command.Parameters.Add("CPID", SqlDbType.UniqueIdentifier).Value = m_CP_ID

where m_CP_ID is defined as a GUID in:
Public Property m_CP_ID() As Guid
Get
If Not viewstate("m_CP_ID") Is Nothing Then
Return viewstate("m_CP_ID")
End If
'Return 0
End Get
Set(ByVal Value As Guid)
viewstate("m_CP_ID") = Value
End Set
End Property

When running the app I got this error:
Server Error in '/4D' Application.
------------------------

Line 1: Incorrect syntax near 'Naam'. Line 1: Incorrect syntax near '?'.(points to mSQL above)
I know it has something to do with the GUID, but I cannot guess what.
Help is appreciated, Ger.

Try this:
mSQL = "UPDATE Contactpersonen SETNaam=@.Naam WHEREContactpersoonID=@.CPID"
Command = New SqlClient.SqlCommand(mSQL, C_CP)
Command.Parameters.Add("@.Naam", txtNaam.Text)
Command.Parameters.Add("@.CPID", SqlDbType.UniqueIdentifier).Value = m_CP_ID
|||Hey SonuKapoor, that works !!!!!!
Thanks a lot, every day I learn more and more... thanks to guys as you,
regards from the North Sea,
Ger.

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)
Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)
Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "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)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

$25,000 per processor for this?

What is wrong with Microsoft? How could you honestly release this product?

I agree with everyone else - the new features in SQL Server 2005 are not worth losing the features in 2000!

I'm telling my clients to not upgrade.

You guys had better release a new version or upgrade fast. mySql is starting to be a real competitor. I can no longer justify your cost.

Well, it depends.

There might be also situations where an update is not necessary, but SQL Server 2005 is really more powerful than the SQL Server 2000. If you don′t need the new features and don′t need e.g. the high scalablity functions you might not need the new SQL Server 2005. (In the most cases you will not need the enterprise features and there can use a smaller edition then enterprise.) But this does not justify your general statements here.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

I happen to agree with you about how you describe your disatifaction. Most likely MySQL is your best choice.

However, all of my clients have most definitely found that upgrading to SQL 2005 to be well worth the time and expense. I wouldn't consider using MySQL at all since SQL 2005 provides so much functionality that the time and effort to painstakenly code such functionality would easily and quickly surpass the cost of SQL 2005.

Most of us that 'know' how to use SQL 2005 can easily justify the cost. That you cannot speaks to SQL 2005 not having any value to you or your needs, and/or your not having the skills to use the product to it best use.

Really, what goes does a post such as your accomplish? Constructive critique is often welcome, mindless bitching does no one any good -except perhaps for a brief catharsis for the writer...

|||I agree with Jens in this case and you may contact the Microsoft support (local) in order to get more information onthe licensing part or upgrades information in thsi case.

$25,000 per processor for this?

What is wrong with Microsoft? How could you honestly release this product?

I agree with everyone else - the new features in SQL Server 2005 are not worth losing the features in 2000!

I'm telling my clients to not upgrade.

You guys had better release a new version or upgrade fast. mySql is starting to be a real competitor. I can no longer justify your cost.

Well, it depends.

There might be also situations where an update is not necessary, but SQL Server 2005 is really more powerful than the SQL Server 2000. If you don′t need the new features and don′t need e.g. the high scalablity functions you might not need the new SQL Server 2005. (In the most cases you will not need the enterprise features and there can use a smaller edition then enterprise.) But this does not justify your general statements here.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

I happen to agree with you about how you describe your disatifaction. Most likely MySQL is your best choice.

However, all of my clients have most definitely found that upgrading to SQL 2005 to be well worth the time and expense. I wouldn't consider using MySQL at all since SQL 2005 provides so much functionality that the time and effort to painstakenly code such functionality would easily and quickly surpass the cost of SQL 2005.

Most of us that 'know' how to use SQL 2005 can easily justify the cost. That you cannot speaks to SQL 2005 not having any value to you or your needs, and/or your not having the skills to use the product to it best use.

Really, what goes does a post such as your accomplish? Constructive critique is often welcome, mindless bitching does no one any good -except perhaps for a brief catharsis for the writer...

|||I agree with Jens in this case and you may contact the Microsoft support (local) in order to get more information onthe licensing part or upgrades information in thsi case.