G
Guest
I have a potential customer who I demonstrated my software to that seems
interested in buying. But, my software is using SQL 2005 Express and this
client already has a full version of SQL Server 2000 installed and would
rather use that than 2005. I told them I was 99.9% sure there would be no
problems installing our SQL2005 database to their SQL2000 server.
Our database is a very simplete database. What I mean by simple is that its
not like a banking system that processes massive volumes of data, or its not
a database that really uses any of the tools provided by SQL Server. What I
mean by this is I've basically just created tables, stored procedures, views
and functions and have an Access database that connects to it.
With this is mind, would my SQL2005 database be able to be restored to a SQL
2000 Server? If so, are there any special things I must do to make by
database compatiable with 2000?
Plus, if we do this, and I end up sending out an update script in the future
to add new tables, fields, stored procedures, etc to our database, would
these work fine in 2000 if they were developed in 2005?
Again, remember, my database is a simple database and I'm not using all the
fancy features of SQL Server to manage my database.
Thanks,
Greg
interested in buying. But, my software is using SQL 2005 Express and this
client already has a full version of SQL Server 2000 installed and would
rather use that than 2005. I told them I was 99.9% sure there would be no
problems installing our SQL2005 database to their SQL2000 server.
Our database is a very simplete database. What I mean by simple is that its
not like a banking system that processes massive volumes of data, or its not
a database that really uses any of the tools provided by SQL Server. What I
mean by this is I've basically just created tables, stored procedures, views
and functions and have an Access database that connects to it.
With this is mind, would my SQL2005 database be able to be restored to a SQL
2000 Server? If so, are there any special things I must do to make by
database compatiable with 2000?
Plus, if we do this, and I end up sending out an update script in the future
to add new tables, fields, stored procedures, etc to our database, would
these work fine in 2000 if they were developed in 2005?
Again, remember, my database is a simple database and I'm not using all the
fancy features of SQL Server to manage my database.
Thanks,
Greg