Jav posted on Sunday, January 28, 2007

Has anyone tried using a finished product developed using CSLA 1.x (which was working with Sql2000 before), now with the same DB simply converted to say SQLExpress 2005?

Area there any caveats? It looks like MS is no longer selling Sql 2000 version upgrades - like going from MSDE to SQL Server 2000 Enterprise etc. Everywhere the slogan is - Go from MSDE to SqlExpress.

Jav

ajj3085 replied on Monday, January 29, 2007

Probably the easiest thing is to go ahead and try it. IIRC, the Sql Server 2005 upgrade will set the Compatability level to 80 (Sql 2000) for any existing databases. I would do an upgrade, then run your unit tests against the Sql server 2005 database. If they all pass, you could be reasonably sure that your application will run.

Change the Compat level to 90 (Sql 2005) and run the tests again. You may have to fix things at this point, but you'll be able to take advantage of the newer features.

Jav replied on Monday, January 29, 2007

Thanks for your comments. After posting that message I did go ahead with it. So far I have not come accross any significant problems. I assume it is running at the Compatibility level of 80.

pelinville replied on Tuesday, January 30, 2007

Did all development and testing in sql server 2000. Then realized the production servers had 2005. Actually one had 2000 and the other 2005. Have not had a single problem 6 months after going live. (And upgrading the 2000 to 2005 production sql server was fast and without a single problem.)