Timeline for Azure TempDB and Log files
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 28, 2015 at 15:33 | comment | added | Dave | Perfect, thanks! I missed that aspect of the article obviously. It doesn't help that we keep changing our service tier selection. I asked this on server fault but do you know how to achieve the column and 256k recommended striping? serverfault.com/questions/732078/… | |
| Oct 28, 2015 at 15:32 | vote | accept | Dave | ||
| Oct 28, 2015 at 15:26 | comment | added | Namrehs | Actually, in the article linked above, they do mention it's okay to put the TempDB and Buffer Pool Extensions on the temp disk and even link to an article explaining how to do it properly. | |
| Oct 28, 2015 at 15:25 | comment | added | Jonathan Fite | Not to put anything permanent on the drive certainly. SQL Server will rebuild the tempdb files if they are not present when it starts up. The script I reference to run on startup would create any folder structures you need and assign the SQL Service account permissions to the folder so that it can create the files it needs. Of course, if the SQL Service account is a local administrator and you just put the tempdb at the root of the drive then you won't have any problems. | |
| Oct 28, 2015 at 15:23 | comment | added | Dave | I like this idea but Microsoft specifically says not to put anything on D:\ as it is a throw away disk.... I assume you're accounting for that by suggesting a script to ensure its integrity on restart. What would a script like that look like? Thanks! | |
| Oct 28, 2015 at 13:39 | history | answered | Jonathan Fite | CC BY-SA 3.0 |