Check the following:

1. Total and Available disk space where your MDF and LDF reside.  Also check file system type.

2. Autogrow file property on both the data and log file for...

Jeff Moden asks a relevent question in his post.  If you answer his questions, you'll get the solution you're after without having to continue this post.  I will look for...

By the way, Sriram, your suggestion will not work either.  Did you try it?  It gives syntax errors.  If you truely want to go the Dynamic route (again, not suggested),...

Since you are concatenating your variables @fromdate and @todate to a string, you need to convert them to a string as well. 

And for the third time, you do not...

Again, this does not need to be dynamic sql.  You say that you are getting an error, what is the error?

I see a couple of things just by looking at it, but the most important thing here is that you do not need dynamic SQL to populate your temp table. ...

I was thinking about using the same approach as Lowel with regards to the derived table using UNION.  You did mention that your table is large so you will need...

How many columns are you talking here?  Are they all datetime datatype?

I would recommend running your test multiple times and clearing out the buffers and cache in between.  I get identical execution times (and execution plans) when I run both of...

You cannot reference a variable value as part of a DDL statement.  In order to accomplish what you are attempting, you must use Dynamic SQL.  Using your example,

declare @townID...

Can you post the exact error message along with the DDL for the tables involved in your SELECT?

It is generally not recommended to place triggers on the system tables in SQL Server 2000.  Therefore, managing stored procedure and DDL changes is a manual process.  I would recommend...

Can you post the function definition for your dbo.wordcount function?  Also, post an example of a function call that does not produce the results you are expecting. 

Ah, you are correct.  I appologize for the incorrect info, that's what I get for comming in early today!!

In addition, while you are in the process of re-writing this, you may want to consider changing your JOIN on the != operator to an ANSI OUTER JOIN as the...