Viewing 15 posts - 56,371 through 56,385 (of 59,069 total)
Sometimes, ya just can't see the forest for the trees
... of course a separate table would do... if I save the SPID...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2007 at 7:36 pm
Heh... guess he got THAT answer ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2007 at 7:32 pm
Good choice... BCP was definitely the way to go especially since you didn't want header info. Nice job and thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2007 at 7:28 pm
Here's all the things that need to be true to do non-logged bulk inserts from BOL...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2007 at 4:57 pm
Cool... Thanks again, Andrew.
Anyone else? It would be really cool if this could be done through T-SQL without modifying SysProcesses directly... don't think it can be done but its worth asking...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2007 at 4:51 pm
Daaaang... thanks, David
Coming from the likes of you, that's quite the compliment.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2007 at 4:46 pm
Heh... and I was too sleepy this morning... I shouldn't post when I'm pooped... ![]()
It is still a bit of a half cross...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 19, 2007 at 6:06 pm
Ok... I was right about the cross-join... and it took more than 3 minutes to exec on 100,000 rows.
And when I change that snippet in the function to have a...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 19, 2007 at 10:54 am
Sure thing, JH... I don't like the looks of that unconstrained cross-join in the function, though... I think it's going to gen 65,536 internal rows every time it executes...
I'll...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 19, 2007 at 10:41 am
I agree... so far as I'm concerned, writing directly to SysProcesses is not an option but a sub for OSQL may be what I have to find (or build). I...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 19, 2007 at 9:15 am
Hey, Richard... just to let you know... I can normally beat most looping functions by using a Tally table... but not this one (least ways, not so far 
--Jeff Moden
Change is inevitable... Change for the better is not.
May 18, 2007 at 9:20 pm
Thanks for the response, Andrew. Yeah... kinda missing what I'm asking for. OSQL doesn't have a "connection string" nor a paramter for it, but the security folks want me to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 18, 2007 at 9:17 pm
Comin' right up...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 18, 2007 at 8:03 am
There's a function in SQL specifially designed to handle IP addresses and similar naming... your instructor probably told you about it.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 18, 2007 at 7:29 am
Never mind... I found it... should I tell him about the function that's specifically designed to take care of IP addresses? NOT!!!
--Jeff Moden
Change is inevitable... Change for the better is not.
May 18, 2007 at 7:23 am
Viewing 15 posts - 56,371 through 56,385 (of 59,069 total)