Viewing 15 posts - 4,651 through 4,665 (of 22,224 total)
When SQL Server 2005 was released, there was an upgrade to ADO. The previous version of ADO had a particular call structure (I forget the precise details, it has been...
"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 30, 2016 at 1:37 am
I'd say the same thing. Knowing what the wait statistics were before you moved the SAN and after will tell you a lot. Same thing with query metrics. 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 29, 2016 at 10:46 pm
tindog (6/29/2016)
ChrisM@Work (6/29/2016)
tindog (6/29/2016)
ChrisM@Work (6/29/2016)
tindog (6/29/2016)
Now Wales are after independence from England to 'safeguard' their future...despite the fact that they also voted in favour of Brexit :w00t:
The Welsh aren't like...
"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 29, 2016 at 4:14 am
You have to capture performance metrics from the old system and the new system and compare them. You'd want to look at the wait statistics, percentage of cpu, i/o and...
"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 29, 2016 at 2:38 am
What's the goal here? To join everything to everything and bring back all the data? To what purpose?
Also, you say "single row per record". What do you mean by this?
"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 29, 2016 at 2:35 am
You're saying deadlock. Do you mean that the SELECT query in question is being chosen as a deadlock victim and it's transaction is being rolled back? Or do you mean...
"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 29, 2016 at 2:33 am
You've got two choices on capturing this information within SQL SErver 2012 and one more with SQL Server 2016 (and Azure SQL Database).
First, extended events. You can capture rpc_completed event...
"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 28, 2016 at 9:46 am
And just so you know, the way filtering works in Trace, it captures the events first, using whatever memory & cpu it needs to do that, then determines if 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 28, 2016 at 9:40 am
Each of the individual statements are going to reflect the statement, but the whole RPC will include any round trip waits between the statements as the data moves back 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
June 28, 2016 at 9:38 am
Gary Varga (6/28/2016)
Grant Fritchey (6/28/2016)
Microsoft 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 28, 2016 at 9:32 am
OK, you'll have to explain that to me better. If Azure releases are bad, that makes the SQL Server release better? I don't get that.
Microsoft is releasing SQL Server more...
"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 28, 2016 at 8:18 am
Without seeing the error, it's hard to say. However, if you start a transaction and that transaction fails, you will get a rollback of that transaction.
"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 28, 2016 at 6:39 am
You'll have to set up an Azure account too. If you have access to MSDN, you can get a free account with a limited amount of funds for each month....
"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 28, 2016 at 6:37 am
CASE statement in the GROUP BY clause is also going to lead to some pretty poor choices by the optimizer.
If you have two different sets of logic, rather than try...
"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 27, 2016 at 2:52 am
I absolutely hear you. I've been working with 2016 for quite some time now. I just haven't hit major issues. Not like with other releases. I'm not about to argue...
"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 27, 2016 at 1:40 am
Viewing 15 posts - 4,651 through 4,665 (of 22,224 total)