Viewing 15 posts - 55,876 through 55,890 (of 59,098 total)
Spot on, Michael ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2007 at 6:48 pm
Why wouldn't someone just use Bulk Insert on this one?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2007 at 6:47 pm
How in the heck does RA3 equate to an RBO of 4000??? And, what is the primary key of the table? We need some more info on this one, for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2007 at 6:43 pm
Yes... I've changed my stance on XML, Frederick. I hate it even more simply because of it's similarity to bloat-ware... but, the folks in OPS just love what it does...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2007 at 5:19 am
Other guesses might be that someone opened the file to see if the FTP was done or a system defrag was running.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2007 at 4:47 am
Yes... why have you defined both a delimiter and a row teminator when you are using a format file?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 11:48 pm
Try a single select with outer joins to MyTable...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 11:45 pm
So, you mean having all of my data for each database in a single name/value table really won't work unless I partition across multiple databases using views? Dang... 
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 10:24 pm
Heh... yeaup... and this time, the newbie started it ![]()
Can't flame if there's no fuel so I'm gonna let William think what he wants...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 8:28 pm
You're kidding...right?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 7:20 pm
Yes, Kavita... make it a DateTime datatype and most of your problems go away. Convince your boss that it's the right thing to do.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 6:54 pm
No... but you could place the results of the proc in a temp table...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 5:58 pm
Heh... now THAT's important... so, lemme ask... is Patient_ID an autonumbering column (or, at least, an incrementing sequence number)?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 5:40 pm
Heh... just can't bring myself to do that, Serqiy... that would mean I'd have to demo saving the date as an integer that looks like an ISO date or storing...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 5:33 pm
If it's "inline" code, as you say, I've previously told the OP's to use the DATEADD/DATEDIFF method to ensure that there's no chance of an "anomoly" like what appeared in...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2007 at 5:28 pm
Viewing 15 posts - 55,876 through 55,890 (of 59,098 total)