There seems to be some problems with SQL Server 2005. Its driving me nuts. And what I can figure out till now is if there is a change in the table definition(added a column) then you need to recompile the view dependent on that table (if you are using select *), otherwise you will witness bizarre problems. (column not found even though it was there). I added a column in the fact table and ran the update query (didn't rcompile the view), this query updated 4 million records and set all the values to 0 (it took more than half an hour). And then instead of using the view I changed it to fact, it ran in couple of seconds updated 22k records and set the right value.And factLeverage also failed. I spent half an hour but couldn't find any reason. It was showing PK duplication error though there were no duplicate records in the recordset (I have even ran the select distinct * from #tmp statement to check the count). Though finally it worked after adding distinct clause (thatâ€™s redundant). I am not sure whether the problem is related to using "select *" in the views, though I believe it used to run fine in 2000. If you define the column names then you have to recompile anyway.Now, I am little afraid whether its updating the data properly esp. where we have modified the table definitions. Anybody has got any clues about this or heard of something related to this?Anyway I am going to modify my all the views and use the column names.