Wrox Programmer Forums
Go Back   Wrox Programmer Forums > SQL Server > SQL Server 2000 > SQL Server 2000
|
SQL Server 2000 General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old September 3rd, 2004, 12:50 PM
Registered User
 
Join Date: Sep 2004
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default Import Error - DBTYPE_DBTIMESTAMP

Hi there,
I've got an error while trying to import a table from MS Access to SQL Server 2000.
"Error at Destination for Row number 231. Error encountered so far in this task: 1. Insert error, column 6('DATE', DBTYPE_DBTIMESTAMP), status 6: Data overflow. Invalid character value for case specification."
I've changed the data type from smalldatetime to datetime but it still doesn't work.
What should I do, please anyone help.
Thanks
 
Old September 3rd, 2004, 01:51 PM
Friend of Wrox
 
Join Date: Nov 2003
Posts: 625
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to jemacc
Default

make sure the Dates in your access table are true valid date

for example: These are not valid dates
08-32-2004
02-31-2004



 
Old June 18th, 2007, 08:58 AM
Friend of Wrox
 
Join Date: Oct 2006
Posts: 114
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Same problem here.

For example, the Access table affected has 40 rows, of which 5 have dates in them, which are in the format of dd/mm/yyyyy and the remainder are just empty. Interestingly, the same rows have another date column in the same format, which works just fine? The only noticeable difference seems to be that the problem column (in this table) contains dates that are in the future - as far as 31/03/2093.

I am using DTS to import the Access DB into SQL and in all honesty am not any kind of expert with poking around in the DTS configuration; though I am familiar with SQL.

On a table with 5 rows from 40 records, I can simply recreate the entries, but some of the tables affected by this problem have many thousands of records and I just wouldn't have the time to enter that amount of data.

Any advice welcomed.

Regards,

Sean Anderson
 
Old June 18th, 2007, 09:15 AM
Friend of Wrox
 
Join Date: Oct 2006
Posts: 114
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Further on this matter:

It seems that the problem occurs on a 'Date/Time' column if (a) the column contains only a time or (b) if the column contains a date that is "far" into the future.

I have valid columns containing dates in 2093, which are failing and I have other columns that relate to opening hours - 8:30AM which have been saved in Date/Time as a time.

Whilst I appreciate that SQL will struggle as it would expect 8:30 on a particular date, but doesn't know what date... The data, in the application is valid and needs to be handled as expected.

Regards,

Sean Anderson





Similar Threads
Thread Thread Starter Forum Replies Last Post
SQL Server 2000 DTS Excel Import Error Tglover SQL Server DTS 0 June 22nd, 2007 12:27 PM
Syntax error? <%@ Import Namespace="System.Data" % fjm9 C# 1 January 16th, 2007 09:17 AM
Import Error. lafilip Flash (all versions) 1 January 5th, 2007 01:12 AM
Error import namespace sersanoi Classic ASP Databases 0 August 18th, 2005 12:10 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.