Viewing 15 posts - 40,156 through 40,170 (of 59,072 total)
Stephen Fry (1/21/2010)
Thanks for the effort, much appreciated!
What you have though is precisely my point...while I agree that it's not overly complicated, it's certainly "more" complicated, and i would think...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2010 at 10:46 pm
Revenant (1/21/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2010 at 10:35 pm
Without xp_CmdShell...
EXEC Master.dbo.xp_DirTree 'yourpathhere',1,1
You can use INSERT/EXEC to capture the info in a table if you prebuild the table.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2010 at 10:33 pm
Actually, a Cursor or While Loop is just what the doctor ordered here...
Every system has a "tipping" point where it just loses it's mind during an update. A million...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2010 at 10:31 pm
Lynn Pettis (1/21/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2010 at 10:07 pm
Very cool code and a great link, Jason. Thanks!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2010 at 10:02 pm
Pedro DeRose [MSFT] (1/21/2010)
1. Complex computation that processes lots of data: before SQL CLR, when you had complex computation...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2010 at 8:55 pm
GilaMonster (1/21/2010)
Jeff Moden (1/20/2010)
I'd suggest the relatively new "master DBA" cert. I've forgotten exactly what's it's called but it's similar to what I've just called it.
Microsoft Certified Master
$18,000...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2010 at 7:58 pm
mranganwa (1/21/2010)
Thank you.. It works....
You bet. Thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2010 at 7:56 pm
Ah.... forgot to mention that if you absolutely must write RBAR (not likely if you learn to write nice simple set based code), you should also use SET NOCOUNT ON...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2010 at 6:53 pm
Nicely written article by the author... can't take anything away from Manor for that.
I thoroughly understand the intent of the article... it's a method for making necessary RBAR faster. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2010 at 6:35 pm
You can also use a pass through view with the columns in the correct order.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2010 at 10:35 pm
You've probably just shot yourself in the mouth by saying it's "urgent". 😉
Why are you writing a cursor for this instead of using set based code? And what is...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2010 at 10:31 pm
Run profiler and capture the "growth" event. You probably won't be able to capture the code causing the problem because it never completes but, make no doubt about it,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2010 at 10:21 pm
Use DBCC UPDATEUSAGE with no output and then run sp_SpaceUsed... or, there's a parameter that you can add to sp_SpaceUsed that will do it for you. It's in Books...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2010 at 9:48 pm
Viewing 15 posts - 40,156 through 40,170 (of 59,072 total)