Viewing 15 posts - 14,506 through 14,520 (of 22,227 total)
You'll still possibly end up with page splits in the nonclustered index AND you'll be dealing with the fact that your structure isn't taking advantage of a good clustered 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
August 10, 2010 at 11:48 am
Excellent Jonathan. Thanks.
"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
August 10, 2010 at 7:54 am
The execution plan stores all the information of what is accessed. This information is stored as XML. So you can run an XML query against the execution plan to return...
"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
August 10, 2010 at 7:20 am
email-935809 (8/10/2010)
"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
August 10, 2010 at 7:07 am
Probably would have worked with ISNULL too, but COALESCE came into my head 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
August 10, 2010 at 6:49 am
You've got a query that is selecting everything from the client table to insert into the client table... I'd figure out who was doing that right away if it were...
"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
August 10, 2010 at 6:46 am
On fairly simple queries the order of tables in the WHERE clause usually doesn't affect performance or the plan generated in any way. As queries get more complicated the order...
"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
August 10, 2010 at 6:45 am
Looks OK to me. Are you getting an error? If so, what is it?
"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
August 10, 2010 at 6:27 am
Not directly and not easily.
What you can do is an XQuery against the queries in cache to see which have accessed a given index, but the read values of 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
August 10, 2010 at 6:25 am
I think this does what you need.
--test table
CREATE TABLE OrderTest
(id INT,
parentid INT NULL)
--test data
INSERT INTO OrderTest
VALUES
(1, NULL),
(2, NULL),
(3, NULL),
(4, 1),
(5, 1),
(6, 2),
(7, 2),
(8, 3),
(9, 3)
--query
SELECT *
FROM OrderTest
ORDER BY COALESCE(ParentId,Id),...
"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
August 10, 2010 at 6:22 am
CirquedeSQLeil (8/9/2010)
Of the people that have a Kindle or Nook or both, can books be shared between people with the same device?
Still digging through the Thread from three days off,...
"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
August 10, 2010 at 5:08 am
Swirl80 (8/6/2010)
Not sure what you're refering to? Whats not on the same SP? We're on Service Pack 3 Cumulative Update 4 on live and Service Pack 3 Cumulative Update 5...
"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
August 6, 2010 at 12:53 pm
I notice they're not at the same SP... since this functionality was introduced with an SP on 2005, maybe you're on the wrong one?
"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
August 6, 2010 at 12:26 pm
Swirl80 (8/6/2010)
If you create this:
CREATE PROCEDURE [dbo].[spProcTest]
AS
BEGIN
CREATE TABLE #qwerty
(
id INT
)
SELECT * FROM #qwerty
END
and get and estimated plan on it then it works. I can 100% guarantee that there 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
August 6, 2010 at 11:20 am
Not sure why Get-Content didn't work for you. I tested it several times. Still, glad you solved the problem.
"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
August 6, 2010 at 7:55 am
Viewing 15 posts - 14,506 through 14,520 (of 22,227 total)