Sounds like you need to break down your update into smaller batches instead of one big update. Could you post your update query?

😎

This gets into basic BOOLEAN LOGIC. Your where clause is this:

That is equvilent to this:

For proof...

Read books and white papers is good, but you also need to get hands on experience as well. One thing you should also consider is purchasing SQL Server 2005...

Read BOL topics DDL Triggers and Event Notifications.

😎

Have you looked at the execution plan with this option on the query to see what is different?

😎

You also may need to update the statistics on the table, possibly using a fullscan.

😎

I suggested it a few months ago when I was getting ready to start a major project using it and thought a dedicated forum would be useful. Unfortunately, the...

Which comes back to limiting the number of rows queried from Tally. For example:

and t1.N <= datediff(mm, @startdate, @enddate) -- you might want to add a + 1 here...

FYI...

select dateadd(dd, 1000000, '2008-10-22')

returns: 4746-09-19

😎

Remember when I said there were 97199 months between 1900-01-01 and 9999-12-31? Well, if you multiply 97,199 by 365 you get 35,477,635. Your Tally table (and mine) has...

There is no restriction there on the number of rows being returned from Tally. That is why you should add a second condition to the where clause, such as:...

Answer, with out restricting the number of rows from the Tally table, SQL executes the dateadd function for every row in Tally until it errors.

😎

I get the same...

The number of months between 1900-01-01 and 9999-12-31 is 97199. Your query, even though it stops at '2013-08-25 00:00:00.000' still attempts to calculate dateadd through the entire Tally table....

I'd also recommend reading the following article:

http://www.sqlservercentral.com/articles/Best+Practices/61537/

It provides excellent guidelines on how to post a question to get the best response possible.

😎