>>Which is why I have only two defaults (dflt_emptystring and dflt_zero) that I use for everything that's not nullable (including datetimes and bits). At least these take very little space and I guess very little processing power when doing mass inserts. When altering tables, I supply the literal defaults, then drop them (this time SQL doesn't complain, knock on wood :), and replace them with bound defaults. Ugly and detouring, but it works.
>
>The bound defaults are deprecated. Don't use them anymore in the production code.

Nice... I remembered it wrong, and didn't bother to re-check the BOL.

Well, I guess they have their reasons and, this being M$, I don't expect they'll ever bother to say why.