Timeline for Any different guidance for tempdb with Availability Groups?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 21, 2018 at 3:58 | history | edited | Aaron Bertrand | CC BY-SA 3.0 |
added 76 characters in body
|
| May 31, 2016 at 14:54 | comment | added | Learning_Learning | Got it Aaron,will plan it that way.I will leave 5% free space of total disk and enable the last data file for autogrowth by 100 MB.Thanks Aaron. | |
| May 31, 2016 at 14:36 | comment | added | Aaron Bertrand | No file growth at all? Well, that is a bit risky, allowing room for one file growth (and setting up alerts to detect it) might be the difference between an immediate outage and enough time to react to prevent one. | |
| May 31, 2016 at 14:17 | comment | added | Learning_Learning | Aaron,I split my TempDB in AOAG environment into 8 files with equal size. TempDB disk size is 200 GB (out of that I assigned 15-20% for templog file with NO file growth enabled and remaining space / 8 = 8 TempDB data files with NO filegrowth enabled ) and enabled flags 1117 and 1118. Now the disk is showing in Red but the TempDB files has 99% available space.So can you please tell me anything to worry in this case ? Thanks Aaron | |
| May 28, 2016 at 13:40 | vote | accept | Learning_Learning | ||
| May 28, 2016 at 13:40 | vote | accept | Learning_Learning | ||
| May 28, 2016 at 13:40 | |||||
| May 27, 2016 at 16:32 | history | edited | Aaron Bertrand | CC BY-SA 3.0 |
added 146 characters in body
|
| May 27, 2016 at 16:16 | history | answered | Aaron Bertrand | CC BY-SA 3.0 |