Slow SQL Server Processing, What did I do wrong in the install?

I think I selected some wrong options during the SQL Server install that led to some very slow processing.  Can anyone spot my errors and advise on correcting them?

I Installed SQL Server Developer 14 on my new desktop last night.  On paper the new unit is much quicker than my old unit.  The new one is an HP workstation with a zenon 6 core processor 32GRB of high speed memory, a 1TB spinner drive.  My builder added a high speed 1TB SSD drive.  They used a PCI card when installing the SSD to get (theoretically) the 6GB thruput on the SSD.

I am doing a very large one time conversion for a client.  The conversion ran for 17 hours on my old Desktop (i7, 16GB memory, 1TB spinner drive) and I was hoping to chop some time off of that with the new one.  The conversion consists of reading, 10's of millions of records from .txt and Excel fiels, possibly reformatting and writing then to the new SQL DB.
The conversion is running in MS Access, Id stored procedures are used they are invoked from Access.  The new computer only has Office 2013 professional install and McAfee, just like the old desktop.  I turn off McAfee prior to running the conversion.

Contrary to what I was hoping , the process ran for 27 hours on my new, theoretically much faster computer.  Given the specs, this makes no sense.  One issue I want to check is my SQL Server install.  I installed it myself and I am a novice so I'm wondering if my set up is the reason for the massive slow down.

My 1TB spinner drive is C: and the SSD is E:.  I wanted the data on the SSD so, as the prompts came up for locations of  files during the install I made them all in a directory called 'E:\SqlData'.
This is the general tab.  I suspect that the Root Directory should point to C:\Program File and this may be the one of the causes of my slow execution issue.

Propeties, 'General' tab
If that is the case, how do I change it?  I was just going to uninstall SQL and start again but when I looked in 'Programs' there a many entries for SQL Server, not all of them are version 14.0
Which of these do I have to uninstall to be able to do a new clean install of SQL Server?
SQL Server items in 'Programs'
Here are some other tabs from the Properties just in case there may be a problem here also.
More SLQ PropertiesEven more SQL Properties
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

ste5anSenior DeveloperCommented:
Well, one problem is Access. It cannot make really use of your workstation. So here you don't gain normally no performance benefits. Then check the performance counters for outstanding IO. Also check your tempdb database. It should consist of four files. Having that much cores can also mean, that you run into parallel wait states. Check the activity monitor in SSMS. When hyperthreading is active, then you should set the maximum degree of parallelism to 6 instead of 0.

Also run sp_Blitz from Brent Ozar to get some hints.

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
mlcktmguyAuthor Commented:
Ste5an:  thank you I will look into that product.  I am aware that MS Access is a limiting factor but both the old and new Machines have that in common.
That’s why I am looking into install/configuration issues.
Do you see anything there?
Nitin SontakkeDeveloperCommented:
With respect to tempdb part, you may please go through the following:

Notice what 2016 installation fixed and what author ideally expects towards at the end of the article. All of this must be done manually in 2014 as the installer doesn't automatically do anything.
David Johnson, CD, MVPOwnerCommented:
putting the data directories on the SSD drive is a good idea.. Preferably you'd like to have a separate spindle for each data directory but moving it off of the system drive is recommended. Considering the number of files involved it is well known that file open is a relatively expensive in time process
Vitor MontalvãoMSSQL Senior EngineerCommented:
Check how much amount of memory is reserved to SQL Server (max server memory).
What about the SQL Server database? It already exists and with data on it or you're creating a new database as part of the conversion process?
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.