Timeline for Make queries and BCP faster on a very large table
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2020 at 22:23 | history | edited | CommunityBot |
added [query-performance] to 2412 questions - Shog9 (Id=1924)
|
|
| Jan 7, 2020 at 22:22 | history | edited | CommunityBot |
added [performance-tuning] to 516 questions - Shog9 (Id=1924)
|
|
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
| Feb 1, 2016 at 8:08 | answer | added | Remus Rusanu | timeline score: 1 | |
| Feb 1, 2016 at 7:16 | history | edited | Paul White♦ | CC BY-SA 3.0 |
Incorporated comments
|
| Feb 1, 2016 at 4:14 | answer | added | Lawrage | timeline score: 1 | |
| Feb 1, 2016 at 0:39 | answer | added | Anti-weakpasswords | timeline score: 0 | |
| Jan 27, 2016 at 21:49 | history | tweeted | twitter.com/StackDBAs/status/692464537551933440 | ||
| Jan 27, 2016 at 19:16 | comment | added | Julien Vavasseur | if you can bcp only minutes within 1 partition, this is best. If you can't no problem. You BCP you file to the staging table. Then you loop through each half hour in the staging table, switch the partition from main table to table 2, add data from staging to table 2 and switch the partition back to main table. and so on for each half hour. Then you truncate the staging table. | |
| Jan 27, 2016 at 18:44 | comment | added | Brandon | I'm trying to understand your approach.. Are you saying use bcp to fill a partition for a particular half hour and then simply do a switch to the current (empty) half hour in production? I wouldn't be able to use bcp alone for that as it's possible that data can be received for a time in the past, which makes it so that I'd have to switch into a non-empty partition. | |
| Jan 27, 2016 at 18:29 | comment | added | Julien Vavasseur | Something I would try: bcp to a staging table. Create a 2nd table with the same design and partitions as you main table. Work 1 partition at a time and switch them. They will be temporary missing from your main table. Move data from staging table to table 2 and switch partition back. Add a CI and partition it. Staging table could be on another DB with bulk recovery model. If you DB uses simple recovery switch to bulk. | |
| Jan 27, 2016 at 18:04 | history | edited | Brandon | CC BY-SA 3.0 |
added 284 characters in body
|
| Jan 27, 2016 at 17:58 | history | edited | Hannah Vernon♦ |
edited tags
|
|
| Jan 27, 2016 at 17:41 | history | asked | Brandon | CC BY-SA 3.0 |