Viewing 15 posts - 6,331 through 6,345 (of 22,219 total)
The solution posted by Cadavre looks very complete.
One possible change, when looking at the situation where there are fewer columns, in the SELECT clause, I'd probably use COALESCE instead of...
"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
April 14, 2015 at 4:28 am
I believe it's part of this report.
"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
April 14, 2015 at 4:25 am
That book is absolutely the place to start.
Performance monitor is one of the tools you'll use to capture metrics. Those metrics are listed in the book. You're also going 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
April 14, 2015 at 4:23 am
It would be very helpful to know the error.
You can attach an image by scrolling down. There's a section below called Attachments.
"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
April 14, 2015 at 4:17 am
Company I worked for did regular searches of the internet for the use of their name. One hit came back on Ebay. A stolen laptop was being advertised for sale...
"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
April 14, 2015 at 4:16 am
ScottPletcher (4/13/2015)
Yeah, a couple of hundred rows with no overlap is not much of a test bed. But the plan still shows what I expected: the UNION-only queries concat...
"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
April 13, 2015 at 4:40 pm
It made me curious, so I put this together real quick:
SELECT a.City,
a.PostalCode
FROM Person.Address AS a
WHERE a.City...
"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
April 13, 2015 at 3:53 pm
And if you are getting multiple results, instead of DISTINCT which is an aggregation command, use TOP 1 with an ORDER BY of some sort. That's much more likely 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
April 13, 2015 at 12:07 pm
SQLRNNR (4/13/2015)
Grant Fritchey (4/13/2015)
SQLRNNR (4/13/2015)
Grant Fritchey (4/13/2015)
SQLRNNR (4/13/2015)
Grant Fritchey (4/11/2015)
"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
April 13, 2015 at 12:06 pm
Brandie Tarvin (4/13/2015)
edyeh (4/13/2015)
"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
April 13, 2015 at 12:05 pm
Especially when doing an ONLINE rebuild, it's a combination of the transaction you're running to rebuild the indexes (might want to break that down to smaller transactions) combined with 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
April 13, 2015 at 12:03 pm
Yes. A query hash is based on the query itself. So:
DBCC CHECKDB('Myfirstdatabase')
Is going to have a different hash value than:
DBCC CHECKDB('ADifferentDatabaseEntirely')
No shocks there at all.
"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
April 13, 2015 at 10:51 am
SQLRNNR (4/13/2015)
Grant Fritchey (4/13/2015)
SQLRNNR (4/13/2015)
Grant Fritchey (4/11/2015)
"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
April 13, 2015 at 10:48 am
The biggest part of the undertaking won't be making the calls to the objects. The biggest part of the work is all the modifications you'll have to make to all...
"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
April 13, 2015 at 9:34 am
I'm with Gail.
Although, if you wanted to you could make this a derived table and then GROUP BY the function. But I don't think it will help your performance any....
"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
April 13, 2015 at 9:32 am
Viewing 15 posts - 6,331 through 6,345 (of 22,219 total)