Sql 2017/2019 unattended installs tempdb files

Question

Post reply

Sql 2017/2019 unattended installs tempdb files

craig.fullen

SSC-Addicted

Points: 473
More actions
December 4, 2018 at 7:26 pm

#373185

Trying to verify that what I am seeing is intended behavior not something I have messed up. When installing 2017 or 2019 and selecting to have tempdb data files and tempdb log file on different drives than the install drive the files are first created on the install drive and then moved to the drive in the config file.
EXAMPLE:
The install appears to create the files on Z: first and try to grow them. Z: is not large enough to handle the growth so install fails. I would have expected the files to be placed on T and U first and then grow. Is this expected or am I missing something.
CONFIG FILE
INSTANCEDIR="Z:\Program Files\Microsoft SQL Server"
SQLTEMPDBDIR="T:\data"
SQLTEMPDBFILECOUNT="8"
SQLTEMPDBFILESIZE="37888"
SQLTEMPDBFILEGROWTH="1024"
SQLTEMPDBLOGDIR="U:\log"
SQLTEMPDBLOGFILESIZE="76800"
SQLTEMPDBLOGFILEGROWTH="1024"

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

G K SSC Enthusiast Points: 142 More actions · Answer 1

craig it seems this is the default behaviour of sql 2017/19 you need not worry.

Jeff Moden SSC Guru Points: 1003861 More actions · Answer 2

gksingh005 - Tuesday, December 4, 2018 9:55 PM
craig it seems this is the default behaviour of sql 2017/19 you need not worry.

Wow... seriously? The install fails due to an erroneous default behavior? Heh... and then you say "you need not worry"??? :blink: What is your work around for this problem?

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Eirikur Eiriksson SSC Guru Points: 182882 More actions · Answer 3

Cannot help it, is the Z: drive an USB stick (that's the last time I saw this error)
😎
Set up hundreds of instances on those version without any such problem, you may wan't to check your model db though!

craig.fullen SSC-Addicted Points: 473 More actions · Answer 4

No the z drive is 100gb drive but our tempdb is is close to 200 gb for data and 100 gb for log. Seems really dumb for MS to add this functionality in the install but not move the files first. I guess most people run small sql databases that are not very busy.

craig.fullen SSC-Addicted Points: 473 More actions · Answer 5

Eirikur Eiriksson - Wednesday, December 5, 2018 10:14 AM
Cannot help it, is the Z: drive an USB stick (that's the last time I saw this error)
😎
Set up hundreds of instances on those version without any such problem, you may wan't to check your model db though!

Curios how you have not seen this is the drive you install too that large? or your tempdb is normally pretty small?