Viewing 15 posts - 8,131 through 8,145 (of 59,091 total)
The client need to update a big table. the UPDATE will be done in the application and the application is using cursor to update the table. I am worrying...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2019 at 4:12 pm
Heh... "42".
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2019 at 10:33 pm
Another thing to look into is Trace Flag 692 and the problems it solves with "Fast Inserts" that take place in a RBAR fashion. It doesn't cause "sudden growth" but...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2019 at 10:32 pm
Online index rebuilds could cause the MDF file to grow quickly and leave free space behind once it's completed
There's a way to keep that from happening but you do...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2019 at 10:29 pm
So and end of day "upsert" would seem to have been in order.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2019 at 10:18 pm
Can I check proactively that any Insert/Update will cause page split.
Sure...
For inserts, you need to check to see if the inserts will occur in the same order as the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2019 at 9:06 pm
We had a need to track the changes happening to an order over time (some of our orders can be active for years). There were many columns of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2019 at 8:51 pm
This works great for me.
How would I go about grabbing the dates dynamically?
Thanks!, D
With the understanding that I have no love for the Pivot operator, please see the following...
--Jeff Moden Change is inevitable... Change for the better is not.
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
December 13, 2019 at 6:52 pm
If the inserts are done in a particular order and the order is actually preserved by the ID column, this could be pretty easy to pull of. You just need...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2019 at 6:45 pm
Awesome. Thanks for the feedback, Steve. I really appreciate it.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2019 at 6:28 pm
Hi,
I'm a bit late to this discussion but we had a requirement to work out median values in SQL this week so I was looking for a method to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2019 at 2:59 pm
SELECT dest.TEXT AS [Query],
deqs.execution_count [Count],
deqs.last_execution_time AS [Time]
FROM sys.dm_exec_query_stats AS deqs
CROSS APPLY sys.dm_exec_sql_text(deqs.sql_handle) AS dest
ORDER BY deqs.last_execution_time DESC
Just to warn again, you have to understand the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2019 at 2:43 pm
If you're also looking into overall performance, don't neglect to specify both BUFFERCOUNT and MAXTRANSFERSIZE.
Totally agreed on that. I use both.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2019 at 4:15 am
I was told (but have not tested) that Extended Events cannot return the query that is causing an event. If that's not true, then my apologies and I'll...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 13, 2019 at 4:13 am
I was told (but have not tested) that Extended Events cannot return the query that is causing an event. If that's not true, then my apologies and I'll go back...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 12, 2019 at 7:12 pm
Viewing 15 posts - 8,131 through 8,145 (of 59,091 total)