Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
smccreadie
Aged Yak Warrior
505 Posts |
 Posted - 2001-10-08 : 09:31:21
|
| I've got a pull from an Oracle linked server that has some datetime fields in it. The source system has some bad dates in it (nothing I can do about it) so that it exceeds SQL Server's datetime data type. (For example, a user type 1/1/1099 instead of 1/1/1999.In BOL, it says to remove the offending field - which of course isn't terrible practical when you need the date.I could put some addition WHERE clauses into the pull that would limit the query further but the Oracle db isn't indexed on those fields and the table size is over a million rows. I'm afraid the performance would suffer a lot.Another option is to convert these into varchar fields during the pull and then work with the pulled data to convert back to datetime, and doing clean-up with T-SQL.Anybody have a suggestion on the best way to approach this? |
|
|
|
|
|
Handling datetime overruns