Viewing 15 posts - 1,186 through 1,200 (of 22,219 total)
You can't substitute "IS NOT NULL" for a parameter value. Now, if you mean that you want to toss, entirely, IS NOT NULL, then you simply would put:
... OR items.UserNumber_02...
"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
Well, for a data collection mechanism like this, I might consider skipping relational data entirely. Instead, look at CosmosDB and use MongoDB to do it.
However, if push came to shove...
"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
I'm looking at what you have shown here, but I don't see any other association between the two data sets except for the first name, SaleAgent in the Revenue data...
"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
Almost sounds like they may be already attached.
"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
100% agreement with Jeffrey on this. I will add though, 2016 to 2019, for most people, most of the time, there's little to no issues on the upgrade. Still, testing...
"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
Could be blocking. Could be resource contention. Could be differences in the amount of data returned. Could be changes in the execution plan caused by changes in parameter values 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
It means pretty much what it says. The query you're attempting to run needs more memory than is available. I did a bunch of reading on this. It's largely a...
"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
Short of building dynamic T-SQL to make it happen, I'm pretty sure you can't. To individually grant permissions on objects, you need to grant them individually. One thing you can...
"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
Thanks for posting the solution. It's helpful to the next person who looks at the question.
"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
Yes, the query looks exactly like you mentioned, Michael. I like the idea of splitting by usage scenarios, especially where there seem to be a couple of the 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
Jeff has nailed the answer. I just want to add that, yes, in Azure you can use Plan Forcing to ensure that a given plan gets used. It's part 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
Changing the database changes the default behavior. Changing the specifics of the connection changes that connection only.
"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
Yep. What Phil says.
Otherwise, you can set up an Extended Events session to capture object_altered. Same goes for created and dropped.
"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
I have a few blog posts that show how Causality Tracking works. The concept is really simple. Things like a login and a DML statement are connected. So, group...
"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
Viewing 15 posts - 1,186 through 1,200 (of 22,219 total)