April 20, 2009 at 7:05 am
WHILE I SELECTING THE TABLE
LIKE
SELECT * FROM TABLE NAME
THIS BELOW ERROR HAS OCCURRED TELL ME A WAY TO REDUCE THAT ERROR, IT HAS THREE FIELDS AS DATETIME DATATYPE...
"
An error occurred while executing batch. Error message is: SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM.
"
April 20, 2009 at 7:22 am
I think you've got a form of data corruption there. I'm not sure how to deal with that myself, not on SLQ 2000. I've pinged an expert on corruption, I'm sure he'll give you some pointers shortly.
How long has this been happening?
Do you have a clean database backup (backup without this problem)
How critical is the data in this table?
p.s. Please don't post in all caps. It's the online equivalent of shouting at someone.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 20, 2009 at 6:00 pm
Gail asked me to comment on this.
Yup - you've got corruption. On 2005 there's a documented way to check for this - DBCC CHECKDB ... WITH DATA_PURITY, but there's no documented option on 2000. You can do some of the same checks on 2000 using the undocumented trace flag 2570, and then running DBCC CHECKDB.. but you'll have to manually remove the corrupt values.
You can figure out how to do this using the info in KB 923247.
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
April 20, 2009 at 6:01 pm
And of course, you could restore from your backups. Do you have backups?
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
April 20, 2009 at 11:18 pm
Thanks for Reply .. I have solved that problem At early i posted here..
April 21, 2009 at 2:43 am
Thanks Paul
S.saravanan: Out of curiosity, how did you fix it?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply