sql server - INSERT w/subquery INTO another table - overflow error -
i've been trying insert data 1 access table linked sql server table using following sql statement this question, modified purposes - keep getting 'overflow' error message:
insert dbo_tblgageactivity(strgageid, strcustjobnum, datdateentered, dattimeentered) select [gage id] gageid, [customer job#] jobnum, [date] dateentered, [time entered] timeentered tblinsttrak;
i've tried number of ways, resulting in 'overflow' error. must missing something, life of me, don't know what. >100,000 records 1 insert subquery handle?
-- edited 01/25/2011 @ 1540 hours --
the data types , sizes of fields follows:
tblinsttrak type:size required dbo_tblgageactivity type:size required ---------------------------------------------------------------------------------------------------- gage id text:50 true strgageid text:50 true customer job# text:50 false strcustjobnum text:50 true date date/time:8 false datdateentered date/time:8 true time entered date/time:8 false dattimeentered date/time:8 true
-- edited 01/26/2011 @ 1355 hours --
alright - i've been banging head on few days (before came it, , day it's been here) , differences can come date entered field on local app side formatted 'm/d/yyyy' , time entered field on local app side formatted 'long time' - neither of these fields in sql server table have format set.
for performance reasons, starting wonder if there better way pull current data data table - pull updates local app mirror sql server copy. no data entered sql server side copy, it's used performance test application - data changes on local application side. approach easier wiping sql server database table , repopulating every time want update it?
-- edited 01/28/2011 @ 1236 hours --
after finding dates around roman empire days (thanks david fenton pointing me onto this) modified import sql statement following:
insert dbo_tblgageactivity(strgageid, strcustjobnum, datdateentered, dattimeentered) select [gage id] gageid, [customer job#] jobnum, [date] dateentered, [time entered] timeentered tblinsttrak [date] >=1/1/1900;
i got couple great answers, , can chose 1 answer (mental anguish) please don't pissed - really helped me learn.
do have date values in access outside range of sql server date/time field? that's very, common issue encounter when upsizing old access databases sql server -- lots of finger errors dates during late roman empire!
Comments
Post a Comment