Viewing 15 posts - 7,471 through 7,485 (of 22,226 total)
The way SQL Server works, it will take all the memory in a server that it needs unless you tell it not to. That's just the way it functions. Here's...
"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
September 15, 2014 at 7:20 am
You can see live connections by querying sys.dm_exec_requests. But to really audit connections, I'd suggest using the extended events. You can then capture all connection events to the server.
"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
September 15, 2014 at 7:17 am
First five chapters of my book.
"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
September 15, 2014 at 7:15 am
True, and while we're on it, there's also the object_id in sys.dm_exec_procedure_stats. So you have a number of ways to get at the plan handle for a given procedure.
"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
September 15, 2014 at 7:12 am
If you're looking for a particular procedure name, then those extra spaces in the WHERE criteria are going to mess you up. Remove them and try again.
"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
September 15, 2014 at 6:58 am
SQL DJ (9/13/2014)
I have made the modification as below. It gives me duplicates...how can I remove these ?
isnull((select distinct (SUM(a1.ActualDebit) - SUM(a1.ActualCredit) ) from #MainAccount a1
LEFT OUTER JOIN
#BudgetAccount bb ON...
"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
September 13, 2014 at 9:19 am
Well done! Just keep coming back and slogging away. You'll get to the next level too. Congratulations!
"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
September 13, 2014 at 6:17 am
freddyism00 (9/12/2014)
I read part of the whitepaper, it said the data columns are stored...
"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
September 13, 2014 at 6:11 am
SQL DJ (9/13/2014)
Grant,What do you mean by execution plan ?
Gail's answer is good. You can also follow the links in my signature to my books on query tuning and execution...
"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
September 13, 2014 at 6:09 am
Really, really, really need the execution plan to understand how things are behaving within your environment. Without that, it's all guesses. But, all these correlated sub-queries:
select (SUM(a1.ActualDebit) - SUM(a1.ActualCredit) )...
"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
September 12, 2014 at 8:56 am
Yeah, you pretty much have to use it. Equality and Inequality columns are the columns being used within the queries in the WHERE, JOIN and HAVING clauses. They would make...
"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
September 12, 2014 at 8:41 am
You need to look to your execution plan to understand how it's using the indexes you've created.
From the looks of things, you have an index on a bit column, IsActive....
"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
September 12, 2014 at 8:38 am
I'm sorry, I'm not quite understanding what you're referring to here. Do you mean a table variable or temporary table?
"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
September 12, 2014 at 8:34 am
You can also use DBCC FREEPROCCACHE and pass it the plan handle of the plan you want removed from cache.
NOTE: If you don't pass it a plan handle, 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
September 12, 2014 at 8:32 am
There's not much on the detailed internals of the in-memory indexes yet. The non-clustered index is still a b-tree, sort of. They also call it a bw-tree. The bw stands...
"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
September 12, 2014 at 8:28 am
Viewing 15 posts - 7,471 through 7,485 (of 22,226 total)