If you ship your tables, databases, SP's, etc as scripts, everything should work as long as you don't use anything new in SQL Server 2005.

>We currently are using a SQL Server 2000 Database. We are looking at upgrading to SQL Server 2005. The problem is, many of our customers may not fork out the money to upgrade. Does anyone have any personal experience or some good articles on compatability issue between SQL Server 2000 and SQL Server 2005? Any information on the types of issues we may run into would be greatly appreciated. We develop the tables, stored procedures, functions etc here, and distribute to our customers. So the last thing we need is to change a stored procedure here on 2005 and send it to a SQL 2000 server and have it bomb. Thanks.