Viewing 15 posts - 1,411 through 1,425 (of 22,227 total)
Then you may need to create a temporary storage between the two. Load a table somewhere, then call the other query.
"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
March 9, 2021 at 1:48 pm
Also test whether doing an outer join to the approved table and looking for nulls might be faster than the NOT IN.
"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
March 9, 2021 at 1:43 pm
To tell you where the row estimates are coming from, I need to see the execution plan, query and statistics. However, in general, the row counts come from the statistics....
"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
March 9, 2021 at 1:39 pm
Piling on just a little. It could break things. It completely depends on how you do deployments of changes to the structures in your database. A schema bound view means...
"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
March 9, 2021 at 1:36 pm
There are a number of things that can cause different execution plans. First up, and usually the most common, is parameter sniffing. A value is passed to a stored 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
March 9, 2021 at 1:33 pm
I'm a little confused as to why this is a problem. If you have a way to tell SQL Server, hold all the data on this query, then, you have...
"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
March 9, 2021 at 1:28 pm
Try running a query or three to see what happens. The system tables are pretty straight forward to use. Let's figure out if it's Query Store itself that's a problem...
"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
March 8, 2021 at 2:03 pm
Cheers!
"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
March 8, 2021 at 1:48 pm
The reports are pretty chatty. Have you tried just running a query directly?
"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
March 8, 2021 at 1:22 pm
What about using TOP 1 and order by the 'Last touch date'?
"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
March 8, 2021 at 1:21 pm
I read The Fort. I've also read Cornwall's books about the battle of Agincourt. And the Last Kingdom. He's got some great stuff.
"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
March 8, 2021 at 12:41 pm
BTW, you'll get a lot more attention by posting your stuff to a new question. The only people likely to respond to this are those of us who are following...
"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
March 5, 2021 at 7:56 pm
You may have kind of outlined the issue. You truncated the data, which will empty the statistics automatically. The SELECT query runs after the truncate, but before the data load...
"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
March 5, 2021 at 7:55 pm
You're past the edge of what Express is used for. I'd strongly advise you to upgrade to a paid version of SQL Server. You can take advantage of more 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
March 5, 2021 at 12:34 pm
I'm going to agree with Jeffrey here. I think you would need to tear down the existing AG before you can create a new AG, especially using the same name.
"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
March 5, 2021 at 12:27 pm
Viewing 15 posts - 1,411 through 1,425 (of 22,227 total)