Spending a little time planning and researching can often extend a products economically sustainable lifespan by a substantial amount. Let’s take a quick look at this from a SQL perspective in this fictional example:
Project A comes along and you need to maximise the lifespan of the application and provide a clear upgrade path to future versions of SQL. No problem! So you’ve done your design and want to put together a proof of concept. Your design requires a few Defaults, so you open SSMS, expand the Programmability Section of your POC database, right click Defaults to add new and … you get ‘Refresh’…
The point here is not to argue the validity of using Defaults (ditto Rules), or the tool for implementing the POC. The point is that for some reason, Defaults are no longer ‘easily’ programmable via the GUI. Why not? Well, it looks like this behaviour represents Microsoft’s way of gently pushing you away from a concept to use in your designs… After a bit of searching I tracked down this link: Deprecated Database Engine Features in SQL Server 2005.
I think the MSDN page is missing a crucial column, and that’s one to illustrate the purpose for deprecating the feature, perhaps with links to further discussions on the subject. Some features are easy enough to comprehend, but others are not.
So, if maximum lifespan is a requirement of your product, start by looking for the deprecation lists and roadmaps for the technologies you plan to implement…FTD