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

ERROR: must be owner of database databaseName - postgres error

Hi everyone! Today's post is about Postgres SQL. In my environment we are using Postgres SQL as one option for the backend of AWS (Amazon Web Services). That's right. We also have another option - MySQL. This post however will focus on the Postgres SQL error: "ERROR: must be owner of database databaseName" Scenario : I encountered this error when I was trying to drop a database from an AWS cluster. Amazon allows you to group databases inside of containers. These containers still have the same logic as SQL schemas which hold our database in SQL server. You can read more about AWS clusters here . Solution : This is very easy. It's in the error. All I have to do is make myself the owner of the database so I can delete the database. I. If your user account does not already have read/write privileges, then you will need to sign in to the Postgres cluster with an admin account so you can grant read/write access to your user account. II. If your ...
Post a Comment
Read more

How to export SQL agent jobs from your SQL Server instance

Hi everyone! As a database administrator, you always need a copy of your data and data processes for: migrating servers disaster recovery backup procedures/best practices This post covers a simple Powershell script. The script is to take a backup of all the SQL agent jobs on your SQL server instance. If you ever needed to recreate all the jobs on another server, all you would have to do is execute the SQL script. I. In SSMS (SQL Server Management Studio), create an empty .SQL file and save it with this naming convention: I.e. SqlAgentJobs_PROD01.sql } This file will represent all the SQL agent jobs on the primary production SQL server. II. Copy the "SqlAgentJobs_PROD01.sql" file from above to a network share. III. Run the Powershell script below in  Powershell ISE as administrator: ##migrating jobs from one server to another with the replace command $SqlConnection = New-Object System.Data.SqlClient.SqlConnection $SqlConnection.ConnectionStrin...
Post a Comment
Read more