Viewing 15 posts - 20,296 through 20,310 (of 22,224 total)
Thank you again. Feedback, positive or negative, is always welcome.
"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
May 30, 2008 at 6:46 am
Thank you, but Books Online is better and much more complete.
"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
May 30, 2008 at 6:32 am
You're in Full Recovery mode and have log backups in place right?
"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
May 30, 2008 at 6:31 am
Yes, that's normal behavior. As noted above, if there are multiple statements within a stored procedure, each statement will have an individual plan. Each plan will show as a percentage...
"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
May 30, 2008 at 6:23 am
Definately a Books Online topic. I did write a primer on backups & restores over here[/url]. I'd still hit BOL first.
"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
May 30, 2008 at 6:16 am
Flush the procedure cache, dbcc freeproccache(), and then rerun the queries. I think MANU might have it. You inserted one table from the other. It's indexes are going 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
May 30, 2008 at 6:12 am
I would definitely start with the trace to see which procedures are running long because I'll bet they're the same ones that are causing this problem. There are some great...
"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
May 30, 2008 at 6:08 am
Blocking will require more than perfmon & profiler. Do a search in the scripts and you'll find some timed scripts that will gather that data for you.
SQL Server 2008 is...
"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
May 30, 2008 at 6:01 am
Since you're already joining to the table, why not use the FREETEXT in the WHERE clause instead of joining the table to itself?
"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
May 30, 2008 at 5:59 am
Whoops. I'm a moron.
"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
May 30, 2008 at 5:56 am
Get the execution plan and it will tell you exactly what's occurring when. That's what they do.
"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
May 30, 2008 at 5:52 am
You're pretty close
But, am I supposed to drop the foreign key from the other tables that use this pk as a fk ?
Yes, you need to drop the foreign key...
"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
May 30, 2008 at 5:50 am
sherlockian21 (5/30/2008)
Select *
from
(
select (top 500 row_number() OVER (ORDER BY(rank desc) as resnum, rank, description, table2.col, table3.col, table4.col
from table1 inner...
"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
May 30, 2008 at 5:43 am
To determine what the queries are doing your friend needs to look at the execution plans. That will identify where the time is being spent and suggest possible solutions.
Also, I...
"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
May 29, 2008 at 11:52 am
So, if I understand this correctly, the plan is to break down a title into it's component words, store each word in seperate table with a link back the title...
"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
May 29, 2008 at 10:20 am
Viewing 15 posts - 20,296 through 20,310 (of 22,224 total)