Viewing 15 posts - 20,221 through 20,235 (of 22,224 total)
Problem is, you can't do the CASE statement like that. You have to use an IF and this becomes a multi-statement query.
"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 6, 2008 at 7:06 am
Maybe you need to better define what you're looking for. ALZ's solution shows procedures that are running and how long they are taking. Determining whether or not a query 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
June 6, 2008 at 6:18 am
A table valued function does require you to define the structure of the table. So, no, this won't work the way you want. I'm not at all sure, but 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
June 6, 2008 at 6:10 am
I'm glad it was helpful.
"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 6, 2008 at 5:57 am
I haven't used JPA, but our developers have been making noises about nHibernate. I did some tests with it. The basic parameterized queries ran similarly to stored procedures. But the...
"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 12:51 pm
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
Viewing 15 posts - 20,221 through 20,235 (of 22,224 total)