Viewing 15 posts - 36,151 through 36,165 (of 59,067 total)
wbrianwhite (11/1/2010)
Jeff Moden (11/1/2010)Heh... there're a couple of dozen people on this site alone who are capable of pulling off huge multi-row inserts from a GUI via a stored procedure....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2010 at 7:51 pm
Perry Whittle (10/30/2010)
JeffThere isn't really any hard fast link for a fix, it depends what the failure is. Each situation is taken on it's own merit.
Heh... nah... Gail is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2010 at 7:29 pm
GilaMonster (10/30/2010)
Jeff Moden (10/30/2010)
GilaMonster (10/29/2010)
p.s. The last integrity check of any of these databases was almost 2 years ago. You like living dangerously?
That actually brings up a good subject. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2010 at 7:27 pm
Craig Farrell (11/1/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2010 at 7:19 pm
David Ziffer (11/1/2010)
Jeff Moden (10/31/2010)
David Ziffer (10/30/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2010 at 7:08 pm
Heh... makes no moxnix... some revived conversations are just as fun. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2010 at 6:49 pm
GilaMonster (10/31/2010)
Just noticed that I missed spotting a milestone. Better (a little) late than never
Freakin' awesome, Gail! If you see a glow in the NorthEast tonight, you know I...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2010 at 6:45 pm
Thanks for taking the time to write that feedback, Craig.
Bah, it's a perfectly valid thing when you're coding in the 'now', not the 'eventually whatever'. Our jobs are accuracy and...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2010 at 6:25 pm
Damn! There is a trade off. If you don't know there's going to be dupes or not, pray for dupes when you use it. 🙂
USE ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2010 at 6:54 am
Paul White NZ (10/29/2010)
Super-fast DISTINCT using a recursive CTE:
Absolutely awesome! What on earth made you look for an alternative to DISTINCT?
On my 8 year old 1.8GHz P4, here's what...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2010 at 11:53 pm
Jeff Moden (10/31/2010)
SwePeso (10/31/2010)
I think Jeff means extending date ranges.If you have three date ranges
20100101-20100630, 20100515-20100930 and 20100928-20101010,
the end result is 20100101-20101010.
That would be a separate article I was going...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2010 at 11:40 pm
WayneS (10/30/2010)
Jeff Moden (10/30/2010)
Ya beat me to it by a long shot. Well done.
Thanks. I've got just five words to say... "SQL Server MVP Deep Dives[/url]"
Oddly enough, I just...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2010 at 11:38 pm
WayneS (10/31/2010)
It still has to be declared before it is referenced... if you move the if/declare block to the end of the code, it does generate an error.
Sorry, Wayne... blew...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2010 at 11:29 pm
David Ziffer (10/30/2010)
I certainly would load rows into a single table as a group, but even those insertions must be done through individual calls to the RAP insertion procedure.
I'm not...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2010 at 11:11 pm
David Ziffer (10/30/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2010 at 10:53 pm
Viewing 15 posts - 36,151 through 36,165 (of 59,067 total)