Skip to main content

How to install SQL Server 2014

Hi guys!

 Today's post is on how to install SQL Server.

 In this demonstration I will be installing the Developer edition of SQL Server onto a DEV server.

 Let's get started.


  1. I have already copied my install file to the DEV server.
  2. I also went ahead and created my install directories on the different drives:
    I.e. D:\Data5, L:\Log5, T:\Temp5 and V:\Backup5.
    Note: My directory ends with the number 5 because I already have other instances installed on this server. When installing a new stand alone instance on a server with existing instances, you need to create a new directory for each instance AND make sure that your directories are on different drives as well.


  3. Go back to your installation file > rt click the file > Mount

  4. Run the setup file as administrator.


    Perform a New Stand Alone Installation.



    Skip auto updates.



    Perform a new installation.


    Enter the product Key and Accept the License Terms.



    SQL Server Feature Installation


    Add SQL Server Replication (under Database Engine services)
    Note: Leave the default root directory as is.



    Name your instance.


    Server configuration settings leave the defaults.


    Use Windows Authentication mode and the local 'Administrator' as well as the 'current user' which is yourself.


    On the Data Directories tab, point to the directories created in step 2 and then hit 'Next'.



    Now hit the 'Install' button.



    Installation is complete.


  5. Go back and install the 2 service packs from step 1 in this order:
    a) SQLServer2014SP2-KB3171021-x64-ENU
    b) SQLServer2014-KB4459860-x64
  6. Enable Named Pipes and Configure the TCP/IP to use the next available port (in this example the next available port # was 1437):


    Note: Port 1434 is reserved for UDP and should not be used for SQL Server instances. In addition, updating the port and memory will require restarting the instance.
  7. Open the instance in SSMS and rt clk the instance > Properties > Memory page > set the minimum memory to 2048 and the max memory to 4096.
    Finally, while still under the instance properties, go to the Security page > select  SQL Server and Windows Authentication mode.

    Note: These changes will also require you to restart your instance.
If you have any questions related to this post, please put them below.


Thank you and Happy reading,

-marshé hutchinson
#learnSQLwithme
Labels:

Comments

Post a Comment

Popular posts from this blog

event id 101 task start failed - task scheduler event id 101 launch failure

Hello again. This post is related to automating SQL server tasks with Task Scheduler. In this example I was tasked with exporting SQL server agent jobs twice a month. To achieve this, I setup a task scheduler task that ran a PowerShell script that: establishes a local connection to the SQL server. cleans the file before writing to the .sql file to avoid adding on (appending) results on subsequent runs of the task scheduler task. when a connection is established, export the SQL agent jobs on the server to a .sql file on a remote server. sends a confirmation email via the SQL server database mail profile that the SQL agent jobs were exported to the specified remote server path. That was a mouthful. Now that you know my task scheduler task is calling a PowerShell script, let's get back to why it is failing.  The good news is this error is not related to the script. The error launch failure means the task could not even run. This is most likely due to a permissi
Post a Comment
Read more

Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 199 The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).

Hi guys! Here's another quick and easy post. Scenario I was trying to copy a SQL agent job from one server to another by just copying the script of that SQL job. You can copy any script by right clicking a job > Script job as > create to > new query window. I pasted the job on a different server and tried to execute it and received this error: Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 199 The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]). This error message is simply saying for the variable '@owner_login_name', the user account associated with the variable is incorrect because it does not exist. Fix Simply update the variable for '@owner_login_name' to a valid user account for the current SQL instance. Now when you execute the script again to create the SQL agent job your results will be: Command(s) completed successfully. If you have any furt
2 comments
Read more

Executed as user: . Incorrect syntax near ''. [SQLSTATE 42000] (Error 102). The step failed.

Hi everyone! Today's post is about an all too common problem... syntax issues. Whether you fat-finger your keyboard or are always in a rush, chances are you have already encountered many syntax errors. But if you are a newbie,  your syntax error is just around the corner. No worries, this is an easy fix. Syntax errors just let you know part of your code or script is incorrect. Scenario I have a SQL agent job that is using the SQL command line to perform index maintenance, but it is failing. Here's my code : sqlcmd -E -S $(ESCAPE_SQUOTE(SRVR)) -d master -Q "EXECUTE dbo.IndexOptimize @Databases = ' databaseName ', @FragmentationLow = NULL, @FragmentationMedium = 'INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE', @FragmentationHigh = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE', @FragmentationLevel1 = 5, @FragmentationLevel2 = 30, @UpdateStatistics = 'ALL',@WaitAtLowPriorityMaxDuration = 180, @WaitAtLowPriorityAbortA
Post a Comment
Read more