Viewing 15 posts - 55,861 through 55,875 (of 59,086 total)
Dave,
If you want to do this from an app or even TSQL itself, see the following script for how to do it... and, yes, it is a registry change...
http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=1854
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2007 at 6:50 am
I guess I just don't understand why you are using OpenRowSet when Bulk Insert will load the file in about two heart beats. You wanna try that, instead? Lemme know...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2007 at 10:46 pm
Could it be that the sender of the files is sending the trigger file before the data file is received in total?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2007 at 8:34 pm
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
Viewing 15 posts - 55,861 through 55,875 (of 59,086 total)