+1

Jeff Moden (6/11/2015)

---

You just have to remember to be a bit careful with...

Alvin Ramard (6/12/2015)

---

Ed Wagner (6/12/2015)

---

Yeah, and it's been going on...

DanMcClain (6/12/2015)

---

I think its great that Microsft does the early (not always perfect) for us early adopters. We have SQL 2014 in production utilizing Column store index, filetables, and In-memory....

Bill Talada (6/12/2015)

---

After reading all posts, I see everyone is doing what is right for their environment. Personally I would only work for a company that strives for clarity...

tom.w.brannon (6/12/2015)

---

I had a situation where in older tables a column was named CNTRY_CODE due to column name length limitations at the time. When the name length restriction went away...

Dan Guzman-481633 (6/12/2015)

---

Yes, I sometimes rename objects and columns. Our development process is Agile with Continuous Integration. Database changes checked into source control are deployed to QA every...

How often?

Ed Elliott (6/11/2015)

---

Hi,

Renaming is vital when maintaining a database as it means you can refactor it to improve the quality of it. The areas I mean are having consistent naming,...

Agree with the above. You might also keep a few placeholders around: https://voiceofthedba.wordpress.com/2014/11/24/placeholders-for-emergencies/

jwbart06 (6/11/2015)

---

Last night at our PASS Chapter user group we had a gentleman that has moved many of his servers to 2014 and he did a great talk on the...

just the clustered index

Arrrgg, apologies. That's what I get for trying to fix things quickly.

Question corrected to disable the PK, and not the clustered index.

Thanks for the final note and good luck with all of this.

Eric M Russell (6/11/2015)

---

However, for most SQL Server users, it's confusing when attempting to keep tabs on all the limitations and asterisks surrounding things like: Heckaton's compiled procedures can only...