Viewing 15 posts - 43,891 through 43,905 (of 59,101 total)
Oh... and my definition of "Performance Tuning" is one of two things... either writing code to let the optimizer do its job, or rewriting someone else's code to let the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 11:04 pm
The basic idea is to allow the optimizer to do it's job using properly written set based code. You do that by avoiding cursors and while loops in 99.99%...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 11:02 pm
GilaMonster (5/4/2009)
No, it is covering and the optimiser should, theoretically, be picking it. Might be a bug, might be something subtle that we've missed.
I'm not sure how creating a filtered...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 10:23 pm
I'd like to know why anyone cares? Either the DBA is doing (or can do) a good job or not. When I conduct an interview for a potential...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 10:07 pm
Barkingdog (5/4/2009)
I agree with what you wrote:
>>
You need to reset TempDB to a reasonable size and setup a trace for TempDB growth to help isolate the code that's causing this...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 9:42 pm
Clark Bones (5/4/2009)
I have a simple csv-file that I want to import into a table. I have some code and the file is imported, but the columns in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 8:42 pm
Drop the following into the URL field of BOL for how to implement it. It has nothing to do with the app...
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/035b3297-6f89-4043-9ba0-76108781b827.htm
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 8:32 pm
Barkingdog (5/4/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 8:28 pm
We get the exact same error on one of our servers. I've not figured out what is causing it, yet... but, it doesn't seem to bother either replicaton nor...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 8:23 pm
ifila (5/4/2009)
Each file SIZE is between 30k and 35k.
The complete text documents are stored in one table, but the parsed information extracted from the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 8:20 pm
Everyone say it with me... G-O-O-G-L-E 😉
On a different note, I would also recommend Grant's book.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 8:02 pm
Mh (5/4/2009)
Sorry my bad, I know why I was getting the error:multi-part identifier could not be bound.
Thanks!
Two way street, please... tell us what you found! 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 7:57 pm
Heh... if you want to play the part of a BSOFH, take the databases offline one at a time and wait for someone to sqawk. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 7:55 pm
As a side bar, considering things like hurricane Katrina and other major disasters, I'm thinking that <100 miles isn't enough especially in coastal regions and earth quake prone areas.
Shifting back...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 7:39 pm
Frank Carrelli (5/4/2009)
I found my issue that was causing my slow running queries. It appears the Coalesce statements...
How serendipitous... I've recently made that same discovery with doing things like concatenation...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2009 at 7:08 pm
Viewing 15 posts - 43,891 through 43,905 (of 59,101 total)