SQL Server Design Strategy for maintaining version compatibility in a shared database


i wondering if there sources out there discuss strategies on keeping backward compatible database schema in shared database scenario when have application requires new schema changes previous version of application needs continue function on same data.  assume using schema namespaces on views , stored procs way achieve or creating new object new names in same schema. i'm not sure 1 different other.

one simplistic idea not make type database schema changes break older versions of application. pretty safe add new columns existing tables (if have default constraints), add new tables, etc. changing table name, changing data type, etc.  is not safe.  using views can this.

you can add new sps new version of application use, while leaving existing sps old version of applications.


http://glennberrysqlperformance.spaces.live.com/ please mark answer if post solved issue.


SQL Server  >  SQL Server Database Engine



Comments

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

job syspolicy_purge_history job fail in sqlserver 2008

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'