Timeline for Converting Data Type of a full Column/Field
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Nov 6, 2016 at 23:41 | comment | added | mendosi | @MSIS I'm sure those approaches you suggested would work, but they might be more effort, and more disruption, than the steps I described. | |
| Nov 6, 2016 at 22:33 | comment | added | MSIS | How about copying the t-sql code, dropping the old table and creating a new one with the new data type? I guess we need to check out the constraints. Does SQL automatically check the constraints, or are the constraints all parts of the DDL? Or maybe we can cut the whole database, modify the code and then create a new database with the old code? I just worry about whether the old data values inserted will be "orphaned" without a logical table? Sorry I can't upvote your comment, I don't have enough points. | |
| Nov 1, 2016 at 0:13 | history | edited | mendosi | CC BY-SA 3.0 |
further clarification for potentially confusing case
|
| Nov 1, 2016 at 0:07 | history | answered | mendosi | CC BY-SA 3.0 |