MSSQL 2016 Setup Steps Needed

MSSQL 2016 - Setup  

I have a set of task to setup and need the steps.  I've attached an excel to breakdown the requirements.  
I also have a small 120GB database that grows very slow/small.  How would I best calculate the disk space needed for each drive?

Need disk space best practice for data, log, backups and sys db files (which includes tempdb )
System AdminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Aneesh RetnakaranDatabase AdministratorCommented:
Thats a lot of things to do, You can google and find the answers on how to do it. If you cant find any answers, you can post a separate question.

For the reindexing task, i suggest the solution from Ola hallegran
Vitor MontalvãoMSSQL Senior EngineerCommented:
I wouldn't change any default configuration (ad hoc, parallelism, ...) unless there is a good justification for that. SQL Server's default configuration values are based in decades of user feedbacks so it should be the right configuration for 90%-95% of the SQL Server installations.
Also do not work with percentages. For example, 10% for OS can be too much or to few (on a 8GB server only 800MB will be reserved to OS and in a 256GB server, OS will have 25,6GB of memory reserved). Usually a minimum of 4GB to a maximum of 16GB of memory should be reserved for a 64bit Windows Server. I would recommend you to work with 3 set of servers:
XS (from 8GB to 16GB) --> 4GB
S (from 16GB to 64GB) --> 8GB
M (from 64GB to 128GB) --> 12GB
L (more than 128GB) --> 16GB
It's also not a good idea to start with big file sizes as you can't shrink to less than the initial sizes. 1024MB and 512MB it's also a lot and can lead to performance issues because during the file growth the database will be locked. Do not use percentages for file growth but you should deal with this in a single database basis and based on the database needs. You should also take in consideration the VLFs when defining the autogrow value.
Since SQL Server 2016, that Microsoft provides an useful tempdb configuration during the setup. Follow that configuration and you should be fine.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
System AdminAuthor Commented:
Thank you and I will google and learn.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.