Viewing 15 posts - 11,911 through 11,925 (of 22,224 total)
Backups are largely an I/O operation. How fast are your disks? Are you backing up over the network? Are there contentions on the system? Can you put multiple disks 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
September 5, 2011 at 7:58 am
beejug1983 (9/5/2011)
Only backup job is running at scheduled time.
There has to be something else going on. Has to. SQL Server doesn't just randomly decide to slow down. Are you backing...
"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
September 5, 2011 at 7:55 am
GilaMonster (9/4/2011)
Grant Fritchey (9/4/2011)
"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
September 4, 2011 at 6:24 am
The question is, what is causing it? What are your queries doing and what is your structure such that you're getting excessive writes? Could something have changed between RTM &...
"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
September 4, 2011 at 6:09 am
And having Enterprise wouldn't change the fact that you need to adjust the trace events to collect only the information you need. Nothing magic there.
"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
September 4, 2011 at 6:07 am
What do you mean by row versioning? Do you mean the data type rowversion? It's meant as a mechanism for concurrency, to determine if someone has modified a record that...
"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
September 4, 2011 at 6:05 am
I'm assuming that Common.dbo.AuthorizedDepartments is a table valued function, right? Is it a multi-statement table valued function? If so, that's the problem right there. Based on what you're saying about...
"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
September 4, 2011 at 6:01 am
The only deviation I would make on the clustered index over what Gail says is to look for the most frequently accessed path to the data. Usually, it's the primary...
"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
September 4, 2011 at 5:53 am
falcon00 (9/2/2011)
Grant Fritchey (9/2/2011)
So when do you need the old value again? I don't completely understand.
🙂
NEVER!!!
I know I know, that's what I said.
All they want is just to send...
"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
September 3, 2011 at 4:56 am
GilaMonster (9/2/2011)
Grant Fritchey (9/2/2011)
I was just reading about monitoring latch waits over on Paul Randal's blog. He suggested this white paper to understand what's happening with latch waits..
There seems 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
September 2, 2011 at 5:04 pm
I was just reading about monitoring latch waits over on Paul Randal's blog. He suggested this white paper to understand what's happening with latch waits..
"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
September 2, 2011 at 1:17 pm
So when do you need the old value again? I don't completely understand.
"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
September 2, 2011 at 1:13 pm
GilaMonster (9/2/2011)
Considered snapshot isolation?
+1
"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
September 2, 2011 at 9:03 am
And, you have to determine what defines "long running" on your system. On mine it might be when a query breaks 60 seconds. On someone elses it might be 60...
"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
September 2, 2011 at 9:02 am
In general, in these situations, I nest stored procedures. It's not like nesting views or functions, so performance should be fine. Check the execution plans of your queries to be...
"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
September 2, 2011 at 9:00 am
Viewing 15 posts - 11,911 through 11,925 (of 22,224 total)