|
Home > Archive > MS SQL Server DTS > July 2005 > Import Error
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Using DTS, I imported a bunch of tables from Access to SQL. All the tables
have been transferred except but two that are giving me similar error
messages:
"Error Destination for Row number 58. Errors encountered so far in this
task:1. Insert Error, column 10 ('Block From Date', DBTYPE_DBTIMESTAMP),
status 6: Data Overflow. Invalid character value for cast specification".
I checked the row and column mentioned in the error message in the access
table and nothing looked suspicious. Please help!!
Thanks
--
TS
| |
| Allan Mitchell 2005-07-26, 8:24 pm |
| Access' date range is different to that in SQL Server. You may be
experiencing a date in Access that the destination in SQL Server cannot
handle.
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"TS" <TS@discussions.microsoft.com> wrote in message
news:BCED7E0E-AA1F-4444-881B- C3A8E956BD85@microso
ft.com...
> Using DTS, I imported a bunch of tables from Access to SQL. All the tables
> have been transferred except but two that are giving me similar error
> messages:
> "Error Destination for Row number 58. Errors encountered so far in this
> task:1. Insert Error, column 10 ('Block From Date', DBTYPE_DBTIMESTAMP),
> status 6: Data Overflow. Invalid character value for cast specification".
> I checked the row and column mentioned in the error message in the access
> table and nothing looked suspicious. Please help!!
>
> Thanks
> --
> TS
| |
|
| And the solution is? The Date was repeated in other rows with no problem!!
How can I resolve this?
Thanks
--
TS
"Allan Mitchell" wrote:
> Access' date range is different to that in SQL Server. You may be
> experiencing a date in Access that the destination in SQL Server cannot
> handle.
>
> --
>
>
>
> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> www.SQLDTS.com - The site for all your DTS needs.
> www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
> www.konesans.com - Consultancy from the people who know
>
>
> "TS" <TS@discussions.microsoft.com> wrote in message
> news:BCED7E0E-AA1F-4444-881B- C3A8E956BD85@microso
ft.com...
>
>
>
| |
| Allan Mitchell 2005-07-26, 8:24 pm |
| The date was repeated in the same column on different rows exactly the same
format?
You can test to see if the values in that column fall between the range that
SQL Server will accept and if not either enter a default or a null.
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"TS" <TS@discussions.microsoft.com> wrote in message
news:00A199B0-9A81-4164-AC42- 19F9E90ECF5F@microso
ft.com...[color=darkred]
> And the solution is? The Date was repeated in other rows with no problem!!
> How can I resolve this?
>
> Thanks
> --
> TS
>
>
> "Allan Mitchell" wrote:
>
|
|
|
|
|