Viewing 15 posts - 1,696 through 1,710 (of 22,219 total)
Okay, maybe I misunderstood the OP, but I thought from their explanation of the problem that they were trying to use the TOP clause to only get 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
July 23, 2020 at 2:03 pm
A stored proc would just use the script you have. It'll work.
"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 23, 2020 at 2:03 pm
In addition to everything Grant said, and he literally wrote the book on execution plans:
I'd also point out that the ORDER BY dufp.FeatureName will cause a sort 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
July 23, 2020 at 12:24 pm
The key here is the types of queries, not simply should I throw an index on. Columnstore indexes are meant for analytical, aggregation & large scan types of queries. That's...
"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 23, 2020 at 12:12 pm
I assume you've tried and the error explained that your column names are not there. You can't create a view based on ad hoc queries because the view definition needs...
"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 23, 2020 at 12:08 pm
All the cost is located here: [Excel_DK].[dbo].[Excel_DK].[pk_ID] [DUFP]
The predicate is: [Excel_DK].[dbo].[Excel_DK].[PartNumber] as [DUFP].[PartNumber]=[@partNumber]
Probably need an index on that with some INCLUDE for the other returned columns.
Also, you have three different...
"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 22, 2020 at 12:53 pm
Then, ever so strongly, I recommend you pursue other approaches. Partitioning almost never succeeds in improving performance. By almost never, I mean, probably, a 99% failure rate. It's purpose 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
July 22, 2020 at 11:45 am
So, have you and the business worked out your Recovery Time Objective and Recovery Point Objective? If not, go do that first. If so, test this method on a restore....
"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 21, 2020 at 11:47 am
Define a role. Put the users in that role. Then GRANT SELECT to the role for the schema in question. You can also grant additional functionality to the role....
"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 21, 2020 at 11:43 am
Not really. You have to rebuild the structures. This means data movement. The more data you have to move, the longer it will take.
One possibility would be to snapshot 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
July 21, 2020 at 11:39 am
Yeah, I'm not at all surprised that it installed. I just doubt it did anything during that install. It found higher versions or the same versions on all the 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
July 17, 2020 at 12:22 pm
Way back in the day, Brad Macgeehee did a bunch of testing around reorganize and rebuild. What he found is that the majority of the time, reorganize almost didn't do...
"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, 2020 at 11:38 am
I like to hope for the best, but plan for the worst.
This sums it up. You're taking a risk. It'll probably be OK. But it might not be.
"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, 2020 at 11:31 am
In terms of function, yes. They're identical. In terms of supported hardware, etc., No, they're not identical. The developer version should function perfectly as a test system in non-production environments....
"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, 2020 at 11:28 am
Look at the execution plan. It's possible that your data crossed a threshold that changed the row counts. Maybe it used to do an index seek and now it's doing...
"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, 2020 at 11:26 am
Viewing 15 posts - 1,696 through 1,710 (of 22,219 total)