Viewing 15 posts - 20,221 through 20,235 (of 22,219 total)
Thanks guys. I realize it's kind of an obscure topic, but I had such a hard time tracking down the individual pieces of information that I felt compelled to share...
"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
June 5, 2008 at 10:44 am
That's a report definition file, a part of Reporting Services used by the Management Studio to show the data. It shouldn't be something you have to create.
"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
June 5, 2008 at 9:25 am
That's actually what the report is doing. I watched it through Profiler.
"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
June 5, 2008 at 8:46 am
You can add a nullable column to a table using alter table. It won't affect the rest of the table at all.
NO CHECK is functionality around check constraints. If 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
June 5, 2008 at 8:21 am
Cool! I'm glad to hear something worked. Thanks for the feedback.
"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
June 5, 2008 at 7:27 am
Not a problem. Just alias the table. Self-join or not, you're looking at the equivalent of a cursor.
"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
June 5, 2008 at 7:17 am
Yeah, I actually posted some comments about that issue at your other post.
Not seeing the code or the execution plan, it's hard to say, but it could be parameter sniffing...
"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
June 5, 2008 at 6:51 am
First, based on what you said, don't use table variables. Performance will likely degrade.
Second... It really depends on what's going on here, but in general, views serve two purposes. They...
"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
June 5, 2008 at 6:45 am
I love that article from MS on tuning using WAIT states. It's great.
Here's a simple article that might help.
http://www.simple-talk.com/sql/performance/sql-server-performance-crib-sheet/%5B/url%5D
"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
June 5, 2008 at 6:39 am
There's "used" and there's "used"
Do the indexes get scanned or is there a seek operation against them? If scanned, how many rows are reported as being scanned?
Also, the code snippet...
"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
June 5, 2008 at 6:38 am
Assuming the system hasn't been rebooted, yes. Right click the database and you can run a report called "Schema Changes History." It'll tell you everything done to the database in...
"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
June 5, 2008 at 6:35 am
Not knowing the business needs, it looks like what you're doing is correct. Having a calculation or CASE statement in the SELECT criteria is not a bad thing. The only...
"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
June 5, 2008 at 6:29 am
radu.poenaru (6/5/2008)
I've this was a compilation from the creation script of the DB. It seems the table is initially created w/ a clustered PK , then that index...
"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
June 5, 2008 at 6:22 am
Do you normally run the query against the view with no WHERE clause? Because it's returning everything, you're getting nothing but table and index scans. It's rather difficult to drill...
"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
June 5, 2008 at 6:16 am
Thanks for the response Tanya. Like I say, I may whine a bit now & then, but I'm seriously addicted to your product.
"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
June 5, 2008 at 6:04 am
Viewing 15 posts - 20,221 through 20,235 (of 22,219 total)