Viewing 15 posts - 3,136 through 3,150 (of 22,224 total)
Here's some great documentation on what's supported within Azure SQL Database for compression. That should fill in all the gaps.
"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
July 13, 2018 at 7:44 am
Yeah, I don't have an immediate answer to that one, sorry.
"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
July 13, 2018 at 6:46 am
This is a three year old question without an answer.
I haven't had to deal with service broker, but if I did and I was using SSDT, I'd suggest...
"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
July 13, 2018 at 5:31 am
Well, every team I was rooting for is out of the cup. We're down to "Not France" in my house.
How has everyone else 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
July 12, 2018 at 8:42 am
The ISNULL command is absolutely going to lead to table scans with no possibility of seeks. You need to get rid of it. If you have to use an OR...
"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, 2018 at 6:59 am
i'm having trouble separating the total query duration into SQL processing time 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 28, 2018 at 6:54 am
There you go. Multiple threads.
"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, 2018 at 6:27 am
Did either of the queries execute in parallel?
"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, 2018 at 5:27 am
Also, look at the execution plans, specifically the ANSI settings (located in the first operator's properties). See if they're different. That could result in differences in data depending on 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 27, 2018 at 4:54 am
I agree with everyone else, if you really want help, make it easier for us to read this.
I took the time to scroll through it a little bit....
"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, 2018 at 4:44 am
Oh yes. Tons to talk about here.
First up, get your database code into source control just the same as your application code. This gives you the ability 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 27, 2018 at 4:37 am
"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 26, 2018 at 8:49 am
You can do a lot of development locally and then deploy to the cloud.
However, cross database queries are horrifyingly slow and difficult to maintain within Azure SQL Database....
"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 26, 2018 at 5:16 am
It says right at the top that the process with an id equal to this value process694076108 was chosen as a victim. You can then find the input buffers for...
"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 26, 2018 at 5:11 am
100% agreement with Anthony. Why write your own script for this? Ola Hallengren's scripts or the Minion Backup scripts will do the work for you. Why reinvent the wheel when...
"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 26, 2018 at 5:04 am
Viewing 15 posts - 3,136 through 3,150 (of 22,224 total)