ColdCoffee (5/4/2011)

---

Ninja's_RGR'us (5/4/2011)

---

I know, I'm saying to use between so that you don't force a scan because of non sargable condition.

DimDate.FeeWeekEndDate > DATEADD(D, 0, DATEDIFF(D, 0, GETDATE())) AND DimDate.FeeWeekEndDate <...

How much data is the query returning?

Another option is to insert the results into temp table. Then do an insert where not exists. The good thing here is...

LutzM (5/4/2011)

---

I'm from around here, too. How come we never met? :-D:-P

Regarding the subject (but...

Yes but not because of missing ram. Most likely you hve a few plans that are bad in the bunch and slowing everything else down.

Things I'd check immediately... index...

ColdCoffee (5/4/2011)

---

Ninja's_RGR'us (5/4/2011)

---

WHERE (

DATEADD( DD , DATEDIFF(DD,0,DimDate.FeeWeekEndDate ),0) = @ThisDayLastYR

OR

...

I've had a lot of success doing 1 union all in a derived table to avoid the self join in a similar query.

BETWEEN OR BETWEEN in that case gave me...

HTH.

WHERE (

DATEADD( DD , DATEDIFF(DD,0,DimDate.FeeWeekEndDate ),0) = @ThisDayLastYR

OR

...

MostInterestingMan (5/4/2011)

---

Ninja's_RGR'us (5/4/2011)

---

MostInterestingMan (5/4/2011)

---

TheSQLGuru (5/4/2011)

---

Replication is a very complex topic. There are numerous tuning options you have if it isn't keeping up and that is causing the tlog growth....

SQLMyFriend (5/4/2011)

---

I see the report of schema change history, I see our report is huge, I export to excel to do some filtering.

If MS can add some filter on the...

That's the one : http://www.sqlservercentral.com/articles/Administration/procedurecache/591/

Looks nice too (still searching) : http://www.sqlservercentral.com/articles/T-SQL/62061/

I can't find the article I had in mind (really old, like sql 2000).

That one looks decent.

http://www.sqlservercentral.com/articles/Performance+Tuning/ospr/666/

MostInterestingMan (5/4/2011)

---

TheSQLGuru (5/4/2011)

---

Replication is a very complex topic. There are numerous tuning options you have if it isn't keeping up and that is causing the tlog growth. Probably...

Both.

I've seen it done elegantly with a calendar table with OR C.Y = @Year - 1 AND C.month = month and C.day = day.

Or redo the query with union all.

OR...