Be careful with this command in production as you 'break' the log chain if in full or bulk logged recovery models.
You can still use it specifying WITH COPY_ONLY though.

Jeff Moden (4/26/2016)

---

Thanks for the article, Raul. I especially like what I saw on the PerfMon chart in the "Results" section.

Not much to add because Kevin beat me too...

Gazareth (12/3/2015)

---

Nice article, cheers. Might be worth making the point clear that it's an Enterprise Edition feature, so readers can avoid the crushing disappointment I experienced when trialing it on...

Paul Randal (12/1/2015)

---

kosha5 (12/1/2015)

---

It's interesting but tricky. For SQL 2012. What if we drop Default constraint afterwards? It should not "delete" existing data, right? I mean since SQL server started...

kosha5 (12/1/2015)

---

It's interesting behaviour. And if we had to guess, we'd probably think SQL creates internally metadata substitution (Default Substitution), when we create Default Constraint. But this Default Substitution is...

rcerney 63319 (12/1/2015)

---

Very informative article, well done! Being somewhat of a newbie to much of this, my only question is around the update process. So the data gets...

kosha5 (12/1/2015)

---

It's interesting but tricky. For SQL 2012. What if we drop Default constraint afterwards? It should not "delete" existing data, right? I mean since SQL server started substitution of...

n.ryan (12/1/2015)

---

It's articles like this when you realise how much effort and smart the MS-SQL development team put in. I don't remember seeing this change in any headline features (which...

Joe Garrick (11/17/2015)

---

DROP and CREATE for an object works great until you run into one that has any kind of security assigned. If you drop and create, rights granted (or...