Timeline for azure sql - create index, does DB have to be offline?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 22, 2018 at 21:37 | comment | added | Joe W | The 30 minutes for index creation still exists and in fact it probably takes longer to create since there will be new data to be indexed as it goes along. All this does is spread the time to create it over a longer period of time which will either take manual work to do (to manually start and stop it) or the creation of a script to do it. Either way the index is still going to take the same amount of processing time to complete and overall it is going to take a significant longer amount of time to complete which can defeat the purpose of adding an index if you don't get it built speedily | |
| Oct 22, 2018 at 20:33 | comment | added | Joe W | But it creates manual work that needs to be done in order to get the index fully built (and it will take longer to get completed and the index could be critical to operation) and this solution does not address the question about if the database can be online or not during the index build. From the way I read the question performance of the index build is not an issue at the current time and it was just a question of can it be done with the database online. | |
| Oct 22, 2018 at 20:00 | history | edited | Alberto Morillo | CC BY-SA 4.0 |
added 1 character in body
|
| Oct 22, 2018 at 19:59 | comment | added | Joe W | How does this help in this case? The index will still take the same amount of time to build and this would be manual work to stop and start it. Also from what I am reading this is for when you have database issues such as a failure or a lack of resources rather then just taking a long time to complete. | |
| Oct 22, 2018 at 19:57 | history | edited | Alberto Morillo | CC BY-SA 4.0 |
added 15 characters in body
|
| Oct 22, 2018 at 19:52 | history | answered | Alberto Morillo | CC BY-SA 4.0 |