October 1, 2015 at 8:11 am
This will be my first installation of SQL Server 2014, and actually my first install since I did SQL Server 2000 some years ago. I have been reading the postings here and elsewhere and downloading "How to" documents from several authors. In past jobs, the system admins usually did the initial installation, then I go in and change configs, etc. as needed, or the engine was already installed by the time I got on board, so I have not done an install in some time. This time I will be doing the entire install, including downloading the "ISO" installation file. One question that comes to mind right away is what ID do I install from - is an ID that has admin privileges good enough, or do I need the actual admin ID?
My question is basically "any booby traps" to watch out for beyond the basic installation? I will be doing "Standard" on one box, and "Enterprise" in a week or so on another box. I have a good idea of what to install, but any thoughts on what to watch out for will be appreciated. From the articles and documents I read it looks pretty straight forward, but it has been some years since my last installation.
Thanks to everyone in advance!
October 1, 2015 at 8:23 am
you'll need local admin privileges to complete the install
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 1, 2015 at 2:49 pm
If you're doing 2014 on Server 2012, you'll need to install .NET 3.5 from the Server 2012 installation media, if it hasn't already been done.
Here's a link to the quick walkthrough:
http://www.sqlcoffee.com/Troubleshooting101.htm
When you install .NET you'll need to identify an alternate source for the files, use (assuming your DVD drive is D:) 'D:\Sources\sxs'
October 2, 2015 at 4:25 am
The install ought to be pretty straight forward. The hard part is getting the configuration right. Make sure you change a few defaults. For example, Set a Max Memory to allow some room for the OS in order to prevent competition between the OS & SQL Server. Set the Cost Threshold for Parallelism to a value much higher than the ridiculous 5 in the default. Set the Degree of Parallelism for the number of physical cores. There are probably others that aren't coming to mind right now. I'd suggest reading through a few articles at SQLSKILLS.COM. They have good information on this sort of thing.
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
October 7, 2015 at 6:19 am
Final follow-up. The only issue I had was understanding what to name the instance. The caveat is that you probably want to use the "Default Instance" radio button and leave the Name and Instance entries as "mssqlserver" unless you have more than one instance on the server on the Instance Configuration menu. I put in names on those two entries and used "Named instance" radio button, and this turned out to be not correct since application was not expecting a named instance. I ended up having to uninstall and then reinstall with the proper options chosen. Of course, your "mileage may vary". Thanks for those who gave me other suggestions.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply