Viewing 15 posts - 52,336 through 52,350 (of 59,098 total)
We had a similar problem at work... caused an average of 640 deadlocks per day with spikes to 4,000 per day. Here's how to fix it...
Step 1... Rewrite the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 7:38 am
I agree with the others... it depends on two things... how they're written and how they're called.
One of the worst things you can do is create aggragate columns in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 7:27 am
martin.griffiths (2/27/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 7:22 am
Adam Haines (2/26/2008)
In this case, the sorting of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 7:06 am
meichner (2/27/2008)
Matt's method worked perfectly.
Does that mean that you're all set or is there still a problem?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 7:02 am
Lookup "hierarchical queries [SQL Server]" in Books Online... what you're asking for is how to expand a hierarchy...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2008 at 8:14 pm
There's a style #126 in 2k... but no style #127... at least none that I can see under CONVERT in BOL...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2008 at 8:07 pm
Ummm... why is Cross-Apply necessary here? Seems to be a bit of overkill when the simple substrings would probably do just fine...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2008 at 7:45 pm
Something like this will get you started...
SELECT OBJECT_NAME(sc.ID) AS Name,
so.XType,
sc.Text
FROM...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2008 at 7:33 pm
Just a different approach... note that this is only good if within 60 minutes as the OP seemed to indicate wanting... (09:13)...
DECLARE @StartDate DATETIME
DECLARE @EndDate DATETIME
SET...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2008 at 7:11 pm
Nicely done folks...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2008 at 7:00 pm
That's because you didn't do like Matt did... you must include a delimiter on either side of what you're searching for...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2008 at 6:50 pm
Ummm... looking back at some of the code in this thread...
Make sure that the INDEX you're using in the hint is a clustered index... there's the possibility that a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2008 at 6:30 pm
It just works that way... you can execute just about any stored procedure the same way. It's like doing a PRINT to do an immediate calculation.
But if you mix...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2008 at 6:25 pm
Heh... no problem... I just like thoughtful code that helps the OP... the approaches to the problem were interesting.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2008 at 6:21 pm
Viewing 15 posts - 52,336 through 52,350 (of 59,098 total)