Actually, partitioning came sometimes accidentally (or coincidentally) help performance.  For example, the data was originally clustered by id, but to partition you cluster it first by a date.  IF you...

Remove the second column from the first IN subquery:

SELECT minutes FROM dbo.timeaccountmovement WHERE ownertype = 1 AND timeaccountid = 8 AND ownerid IN

(

SELECT ownerid FROM dbo.timeaccountmovement WHERE timeaccountid = 73...

Yes, I've used CDC.  I ended up creating my own proc to view change data (basically pre-prepping the params for the MS proc) because the MS proc itself is so...

I see "emp." being referenced, but I don't see "emp" anywhere in the supplied query.

You would have to check each of the joined tables to see if there is an...

You don't really need to partition, assuming you re-cluster, although you could.  What will happen is that you will partition on date, so you will have to add date to...

If avol is actually numeric.  If it's varchar, could be an issue.

Cluster both tables by ( StartDateTime, ID ) rather than just ID.  Then, since you'll be moving data in cluster key order, you can just use a standard copy-then-delete approach.

Btw,...

Another possibility is, assuming that:

(1) column avol was NULL before this UPDATE

(2) your server still has the default FILLFACTOR 0f 0 (=100)

Then this UPDATE could a lot of leaf page...

You *might* also want some background process to remove carts after a certain period of time, or maybe not.  For example, I can go into Amazon, put something in my...

Creating and dropping tables is significant overhead.  You'd be much better of, as others have noted, with a permanent table.  You could key rows in that table by user id...

Just use a method that works under any/all DATEFIRST settings, much simpler and safer:

/* calc immediately previous Sunday; day 0 = Monday, so day 6 = Sunday...

With 20 name columns, how do you verify that all the names are unique across all rows?  And, if they're not unique, how do you know which id to assign...

The CHECKPOINT is one of the steps required before SQL can mark the existing log space as reusable.  Since you're in SIMPLE recovery model, the only thing that could prevent...

Also, you should issue an explicit CHECKPOINT on the db when you want logs to clear.  Part of the requirement for freeing log space, SIMPLE recovery, is that a CHECKPOINT...

SET @sql_template = N'SELECT...