Viewing 15 posts - 3,121 through 3,135 (of 22,219 total)
"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 19, 2018 at 9:14 am
Oh, the love/hate relationship with PowerShell will only deepen, on both sides.
"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 19, 2018 at 7:32 am
Yeah, that's an approach that will work and get done what you're looking for. However, I'd strongly suggest you take a look at dbatools. It's the best way...
"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 19, 2018 at 4:59 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
July 18, 2018 at 8:26 am
This is a very complicated procedure and generally should not be the norm for most queries. I see a series of issues.
First thing I see is several DISTINCT...
"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 18, 2018 at 7:56 am
Hey!
I work for Redgate, just wanted to state that up front.
Instead of using Compare and Data Compare, have you tried looking at SQL Source Control? 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
July 18, 2018 at 7:08 am
It does. It's called merge replication, but it's more than a little bit difficult to implement and maintain. The showstopper for most people is that one of the first requirements...
"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 18, 2018 at 6:05 am
So, if one is read only and the other is not... How high volume is the database with writes? If the volume is relatively low, you could use transactional replication...
"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 17, 2018 at 11:59 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
July 17, 2018 at 11:54 am
Maybe it's your query. You have columns in the WHERE clause for a table in a LEFT JOIN. Move those out of the WHERE clause up to the JOIN criteria...
"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 17, 2018 at 7:18 am
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
Viewing 15 posts - 3,121 through 3,135 (of 22,219 total)