Hi Folks, We have a product comprised of desktop apps (.NET and native) that talk to SQL Server 2008.
The database and apps get installed at client sites that we have no ongoing control over. We use a table in the database to track schema versions and our database creation / upgrade script uses this to migrate the schema from one version to the next. The data is mostly accessed and modified through stored procedures as we have to manage both native and .NET code. >From our apps we can check the schema version to ensure that the database is compatible with the app, but I'd also like to deal with the scenario where the database is upgraded such that it breaks compatibility with existing apps. I'm thinking that the database needs to store a minimum version number for such apps, then when the app connects it can check if its version is lower than the database requires and exit. I'm interested to know if / how others handle this scenario. Cheers, Matt.
