Errors Upsizing an access 2002 Database to SQL server 2005

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

MrKim wrote:

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

Regrading the 4 tables that fail; Are you sure you don't have other errors? 'Table was skipped, or export failed' Is not clear enough

The other message is just a warning telling you that at some point a certain column in the dataflow is not used anymore; the intention is to suggest to remove it if it is no necessary....only you can answer that question.

|||

No, that is is. When you use the Access upsizing wizard that is all the info it gives on the report. More useful maybe is the error messages given when trying to import the data through SQL server. I did finally import the data. There were bad dates which had to be fixed first.

I did it by turning of the SQL atuonumber/Prim Key, then writing a progam to import one record at a time, and noting the ID on the ones that fail - they all had bad dates.

Errors Upsizing an access 2002 Database to SQL server 2005

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

MrKim wrote:

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

Regrading the 4 tables that fail; Are you sure you don't have other errors? 'Table was skipped, or export failed' Is not clear enough

The other message is just a warning telling you that at some point a certain column in the dataflow is not used anymore; the intention is to suggest to remove it if it is no necessary....only you can answer that question.

|||

No, that is is. When you use the Access upsizing wizard that is all the info it gives on the report. More useful maybe is the error messages given when trying to import the data through SQL server. I did finally import the data. There were bad dates which had to be fixed first.

I did it by turning of the SQL atuonumber/Prim Key, then writing a progam to import one record at a time, and noting the ID on the ones that fail - they all had bad dates.

sql

Errors Importing From Enterprise Manager

Hi,
I am attempting to import objects from one database to another, including co
nstraints. However, the operation keeps failing. How do I find out the spe
cific reason for the failure? Enterprise Manager does not provide specifics
in the error message.
Thanks,
MarkIf you are using the wizard, you can find out more specifics by
double-clicking the line that says "error occurred"...
http://www.aspfaq.com/
(Reverse address to reply.)
"mark" <mark@.discussions.microsoft.com> wrote in message
news:4FE6D4E5-7285-4A01-927D-B47C4F4C3AE6@.microsoft.com...
> Hi,
> I am attempting to import objects from one database to another, including
> constraints. However, the operation keeps failing. How do I find out the
> specific reason for the failure? Enterprise Manager does not provide
> specifics in the error message.
> Thanks,
> Mark

Errors Importing From Enterprise Manager

Hi,
I am attempting to import objects from one database to another, including constraints. However, the operation keeps failing. How do I find out the specific reason for the failure? Enterprise Manager does not provide specifics in the error message.
Thanks,
Mark
If you are using the wizard, you can find out more specifics by
double-clicking the line that says "error occurred"...
http://www.aspfaq.com/
(Reverse address to reply.)
"mark" <mark@.discussions.microsoft.com> wrote in message
news:4FE6D4E5-7285-4A01-927D-B47C4F4C3AE6@.microsoft.com...
> Hi,
> I am attempting to import objects from one database to another, including
> constraints. However, the operation keeps failing. How do I find out the
> specific reason for the failure? Enterprise Manager does not provide
> specifics in the error message.
> Thanks,
> Mark

Errors Importing From Enterprise Manager

Hi,
I am attempting to import objects from one database to another, including constraints. However, the operation keeps failing. How do I find out the specific reason for the failure? Enterprise Manager does not provide specifics in the error message.
Thanks,
MarkIf you are using the wizard, you can find out more specifics by
double-clicking the line that says "error occurred"...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"mark" <mark@.discussions.microsoft.com> wrote in message
news:4FE6D4E5-7285-4A01-927D-B47C4F4C3AE6@.microsoft.com...
> Hi,
> I am attempting to import objects from one database to another, including
> constraints. However, the operation keeps failing. How do I find out the
> specific reason for the failure? Enterprise Manager does not provide
> specifics in the error message.
> Thanks,
> Mark

Errors during import and export

I am unable to import anything from one sql 2000 database to another using the 2005 Management Studio - When I try I get an error similar to this -

Could not set up data flow connections.

The connection type "OLEDB" specified for connection manager {ccccc}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
(SQL Server Import and Export Wizard)

Thanks Richard

I saw this solution on another MSDN forum which worked for me:

"It is a SSIS issue.

Open SQL Server Configuration Manager. Right click on SQL Server

Integration Services. Select properties and in the Log On tab change

the built-in account."

I'm only a newbie to this so I don't know what the implications of this change are, other than I was able to import my Access Db.

Errors during import and export

I am unable to import anything from one sql 2000 database to another using the 2005 Management Studio - When I try I get an error similar to this -

Could not set up data flow connections.

The connection type "OLEDB" specified for connection manager {ccccc}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
(SQL Server Import and Export Wizard)

Thanks Richard

I saw this solution on another MSDN forum which worked for me:

"It is a SSIS issue. Open SQL Server Configuration Manager. Right click on SQL Server Integration Services. Select properties and in the Log On tab change the built-in account."

I'm only a newbie to this so I don't know what the implications of this change are, other than I was able to import my Access Db.

Error2Text is not a member of System.Data.SqlClient.SqlParameter

Error 2 'Text' is not a member of 'System.Data.SqlClient.SqlParameter'.

I think this error has something to do with the lack of an Import command, anyone point me in the right direction?

sorry, I've decided to upload all the code of default.aspx.vb...I'm trying to make a mailing list sign up. So member can add their name and email for a monthly newsletter. I'm getting three errors, the one posted above on each of the three text boxes. what do I do?

Thanks very much

Partial Class _Default
Inherits System.Web.UI.Page

Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles AddButton.Click

Dim connect As String
connect = "data source='.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\Database.mdf;Integrated Security=True;User Instance=True'"
Dim sqlconnect As New System.Data.SqlClient.SqlConnection(connect)
Dim command As String

command = "insert into DataForm values(@.firstname,@.lastname,@.email)"
Dim sqlcommand As New System.Data.SqlClient.SqlCommand

sqlcommand.CommandText = command
sqlcommand.Connection = sqlconnect

Dim firstname As New System.Data.SqlClient.SqlParameter()

firstname.ParameterName = "@.firstname"
firstname.Value = firstname.Text
firstname.SqlDbType = System.Data.SqlDbType.VarChar
sqlcommand.Parameters.Add(firstname)

Dim lastname As New System.Data.SqlClient.SqlParameter()

lastname.ParameterName = "@.lastname"
lastname.Value = lastname.Text
lastname.SqlDbType = System.Data.SqlDbType.VarChar
sqlcommand.Parameters.Add(lastname)

Dim email As New System.Data.SqlClient.SqlParameter()

email.ParameterName = "@.email"
email.Value = email.Text
email.SqlDbType = System.Data.SqlDbType.VarChar
sqlcommand.Parameters.Add(email)

sqlconnect.Open()
sqlcommand.ExecuteNonQuery()
sqlconnect.Close()

End Sub

Protected Sub SqlDataSource1_Selecting(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.SqlDataSourceSelectingEventArgs) Handles SqlDataSource1.Selecting

End Sub

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load

End Sub

Protected Sub AddButton_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles AddButton.Click

End Sub
End Class

|||

Hi,

I think you need to start naming your objects a bit better, seems to me that both your textbox and your SqlParameter have the same name(e.g. firstname, lastname)

I'm pretty sure that's the source of your problems. Try renaming either the textbox control or the SqlParameter (or both) to like txtFirstname and parFirstname.

Good Luck,

Tim Lensen

|||

thanks for the reply I'll give it a go and get back shortly!

Thanks!

-Ian

|||thanks that solved my problem!