6 ms·
-- No longer has a DEFAULT constraint; this means we have to insert the date -- ourselves, but it reduces the work on SQL server kill_time datetime My
by j_baker 14y ago
-- No longer has a DEFAULT constraint; this means we have to insert the date
-- ourselves, but it reduces the work on SQL server
kill_time datetime
My gut reaction is that this is unnecessary micro-optimization. Does making SQL server come up with the date and time really make that big a performance difference?
- emn13 14y agoNot just that; it might well be slower. It's definitely possible to saturate a network connection with a bulk operation like this; less wire overhead matters. I suspect it's mostly just necessary to permit the delay between data generation and storage.
- deleted 14y ago[deleted]
- Cushman 14y agoI think you misread the code-- the datetime is still being generated in SQL, in the stored procedure, as GETDATE(). Nothing extra is going down the wire. The point is to remove the default constraint, and thus the check for null on every insert. May still be unnecessary, but seems like a fair optimization.
- deleted 14y ago[deleted]