Timeline for Moving data into an archive table and reducing the size of the original table
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 27, 2017 at 14:48 | history | edited | Paul White♦ | CC BY-SA 3.0 |
Incorporated comments; edited tags
|
| Feb 11, 2017 at 16:20 | answer | added | Matthew Sontum | timeline score: 0 | |
| Feb 11, 2017 at 13:11 | history | edited | MrVimes | CC BY-SA 3.0 |
added 10 characters in body
|
| Feb 11, 2017 at 4:57 | answer | added | RHaberle | timeline score: -1 | |
| S Feb 10, 2017 at 16:13 | history | suggested | Ian_H |
Generic tag added
|
|
| Feb 10, 2017 at 15:52 | review | Suggested edits | |||
| S Feb 10, 2017 at 16:13 | |||||
| Feb 10, 2017 at 14:43 | answer | added | Aaron Bertrand | timeline score: 2 | |
| Feb 10, 2017 at 14:29 | comment | added | Scott Hodgin - Retired | I'm assuming that exporting the data (bcp) to another drive, dropping and recreating the table with the better design is not an option? - Does your source table have a primary key or unique index? | |
| Feb 10, 2017 at 14:01 | comment | added | Stijn Wynants | To actually move the data & rework it you will probably need some more space in your tlog file & your database file. I would try to get a disk extension for log and an extra disk for your your database file. to temporarily store the data for your archive | |
| Feb 10, 2017 at 13:33 | history | asked | MrVimes | CC BY-SA 3.0 |