When did you upgrade the database to SQL Server 2005 and compatibility mode 90?

I just did some testing on a SQL Server 2000 instance, a database in compatibility mode 80...

Probably need it to look like this: WHILE @date <= @Enddate

Your problem is right here: WHILE @date @Enddate

I'd verify that all the databases are set to compatibility level 90.

Haven't looked at your code, but a good article on computing running balances is referenced below in my signature block. It is worth a read if you haven't yet.

I was being cautious, datediff(mm, '2008-11-30', '2008-12-01') returns 1. Since it looks like you are going back over 10 months, not too much to worry about (I hope).

I guess we really could use the DDL for your tables, some sample data, and the expected results based on the sample data. To see how you should post...

I think I like my solution better. You seem to be making it harder than it really is. You can extract the date from the end of the...

I have to ask, what edition of SQL Server 2005 are you using?

I can think of one reason. We restore the one of our databases as a previous year database that is read only. We shrink the database prior to making...

Made a few slight changes. If you have a test server, you might give the following a spin:

-- Declare variables to store database name returned by FETCH and the...

Charles Kincaid (12/1/2008)

Jeff Moden (11/29/2008)

Some folks store unknown or "open" dates as 99991231 so they don't have to check for null to see if an enddate has occurred in the...

To really help, we would need to see the structure for the table, view, and the code for the function(s) used in the view. Also some test data might...

After looking at the RESTORE DATABASE statement in BOL, I have to say no. You have to restore then shrink the database if you don't want the extra space.

I have to focus on the above, does this mean you don't have regular backups being taken...