Viewing 15 posts - 20,626 through 20,640 (of 22,219 total)
From what I can see here, I'd focus on the code. You've got a lot of waits occurring. Do you know why? You also have a reasonably high number of...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 21, 2008 at 8:35 am
Nice article.
I'm not an SSIS expert, but I overheard our SSIS guru's discussing your article. They liked it. That's a good sign.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 21, 2008 at 7:05 am
Before you start focusing on the server, I'd focus on the code and the structure of your database. Is the code set based or row-by-row? Is it using indexes to...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 21, 2008 at 6:52 am
It's sample code from the BOL.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 17, 2008 at 8:40 am
You could also set one of the parameters as OUTPUT and get it it that way.
ALTER PROCEDURE [Video].[addVideo]
@Title nvarchar(50),
...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 17, 2008 at 8:22 am
13,000 or 30, if Access is going to require him to scroll through every select list to the bottom or it will retain a lock on that table... You have...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 17, 2008 at 8:14 am
Straight out of the BOL:
USE AdventureWorks;
GO
-- Declare and set variable
-- to track number of retries
-- to attempt before exiting.
DECLARE @retry INT;
SET @retry = 5;
-- Keep attempting to update
-- table...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 17, 2008 at 8:11 am
Jason Shadonix (4/17/2008)
Grant Fritchey (3/19/2008)
[to the tune "The Yellow Rose of Texas"]
Oh, my body...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 17, 2008 at 6:36 am
I was not going to respond to this, but I can't help it. You just broadcast to the most helpful bunch of people in the world that you'll lie to...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 17, 2008 at 6:25 am
Yes, please do what Micheal said. Use the OUTPUT statement to gather that information. Don't try to write logic to go back & capture it after the fact. When you...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 17, 2008 at 6:14 am
No doubt you're seeing contention for memory & processor. You'll need to run Perfmon and collect counters on wait times to see what is waiting on what. Where possible (and...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 17, 2008 at 6:11 am
Huh, I'd assume a try catch even on a single row single table update. Even there you could run into deadlocks, whatever, that you want to handle within the TSQL...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 17, 2008 at 6:09 am
And how much do you want to bet that they don't have a tested backup in place either... I wish I didn't hate travel so much. I can see why...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 17, 2008 at 5:54 am
OOPS! The "correct" answer generates an error.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 16, 2008 at 6:52 am
Holy crap! That is some seriously heinous code. Makes you wonder what the database looks like doesn't it?
:sick:
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 16, 2008 at 6:47 am
Viewing 15 posts - 20,626 through 20,640 (of 22,219 total)