Installing Micosoft SQL Server 2016

-

Installing Microsoft SQL Server 2016

Installation Standards and Prerequisites

1. Hardware and Software Requirement

Component

Requirement

.NET Framework

SQL Server 2016 (13.x) RC1 and later require .NET Framework 4.6 for the Database Engine, Master Data Services, or Replication. 

Network Software

Supported operating systems for SQL Server have built-in network software. Named and default instances of a stand-alone installation support the following network protocols: Shared memory, Named Pipes, TCP/IP and VIA.

Hard Disk

SQL Server requires a minimum of 6 GB of available hard-disk space.

 

2. Processor, Memory, and Operating System Requirements

Component

Requirement

Memory

At least 4 GB and should be increased as database size increases to ensure optimal performance.

Processor Speed

Minimum: x64 Processor: 1.4 GHz

Recommended: 2.0 GHz or faster

Processor Type

x64 Processor: AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T support, Intel Pentium IV with EM64T support

 

3. Disk Requirement

Drive

Requirement

D:\MSSQL

SQL Binary Directory

M:\MSSQL\Data

Data File Directory

N:\MSSQL\Log

Log File Directory

O:\MSSQL\Tempdb

Tempdb data and log

T:\Dump

Database Backup Directory

Installation

1. Mount the SQL server Binary Disk image or copy the installation iso file into server 
 

2. Double Click Setup




3. Click Installation 


4.  Select New SQL Server Stand-alone installation and double click.


5.Provide Product Key.  For SQL Developer, it is free and no license key is needed


6.check term and condition and click Next>



7. click Next>





8.Ignore Windows Firewall warning message , click Next>






9.Select basic features as below.  Change instance root directory and point to D:\.  Click Next>   





10.Set instance name and click Next>



Or Named Instance 


11.Click Next>





12.Setup database engine configuration.  Select Mixed Mode > Enter password for ‘sa’ > Add admin AD group if any  as part of the SQL Server Administrator.






13.Click Next



14.Upon completion, you may check system configuration report for installation details




You can learn more about Sql Server database from below book:

========================================================================
Location: Singapore

Comments

  1. SatyaNovember 18, 2021 at 11:20 AM

    Nice screenshots ,and good

    ReplyDelete
    Replies
    1. Database SolutionsNovember 18, 2021 at 11:11 PM

      Thanks .. Please visit our other blogs as well.
      Do let us know any specific topic if you want use to create Blogs on specific topic.

      Please do follow us on Social Media to get latest update on database related blogs.

      Regards
      All Database Solutions Team
      https://www.linkedin.com/in/all-database-solutions-633091225/
      https://twitter.com/database_all

      Delete

Post a Comment

Please do not enter any spam link in comment Section suggestions are Always Appreciated. Thanks.. !

Popular posts from this blog

Restore MySQL Database from mysqlbackup

-
Image
 Restore MySQL Database from mysqlbackup  In todays world, One of the most common activity is to perform database restore using old backup or performing PIT recovery for database.  In this blog , We will show you how to perform restore and recovery of the MySQL database using backup taken via mysqlbackup. In order to restore Mysql database from MySQL backup , We will follow below steps: 1) Shut down MySQL Database Server/Service Check the status of the mysql service using command : systemctl status mysql Shut down mysql service using command : systemctl stop mysql 2) Delete all existing file of MySQL Server Delete all files inside the server's data directory. Also delete all files inside the directories specified by the --innodb_data_home_dir, --innodb_log_group_home_dir, and --innodb_undo_directory options for restore, if the directories are different from the data directory. 3) Restore full Backup mysqlbackup  --defaults-file=/etc/mysql/mysql.conf.d/mysqld.cnf --d...
Read more

Oracle Database 19C Installation on Windows Server 2016

-
Image
Oracle Database 19C Installation on Windows Server 2016 In Database world, Its important to be on the latest version of the database flavor. Though Oracle have release 21c Database as well but by far Oracle 19C is most stable version.( You also check our similar blog for  Installation of Microsoft SQL Server 2016 ) Please do also check out blog for  Oracle 19c New Features to know about Oracle 19c features.  In this blog, We will be installing Oracle 19C DB on Windows Server. 1) Create required directory for Oracle Home and Oracle Base. Oracle Base: E:\app\oracle Oracle Home: E:\app\oracle\db\19.0.0\dbhome_1 2) Move the binary to E:\app\oracle\product\19.0.0 directory and unzip 3) Check unzipped directory. 4)Right Click on setup and  Run Setup as Administrator: 5)   On Configuration Screen, Select Set up software only 6)   On Database Installation Option page, Select Single instance Database installation for stand alone database server. 7)  O...
Read more

MySQL InnoDB Cluster Restore/Create Issue : - Dba.createCluster: Group Replication failed to start: MySQL Error 3094 (HY000)

-
Image
MySQL InnoDB Cluster Restore Issue : - Dba.createCluster: Group Replication failed to start: MySQL Error 3094 (HY000) Recently ,We have been restoring and recreating MySQL InnoDB Cluster and faced below issue after firing : MySQL mysqlhost01:3306 ssl JS > var cluster = dba.createCluster('testdbCluster') .. ..... ... Creating InnoDB cluster 'testdbCluster' on 'mysqlhost01:3306'... Adding Seed Instance... ERROR: Unable to start Group Replication for instance 'mysqlhost01:3306'. Please check the MySQL server error log for more information. Dba.createCluster: Group Replication failed to start: MySQL Error 3094 (HY000): mysqlhost01:3306: The START GROUP_REPLICATION command failed as the applier module failed to start. (RuntimeError) MySQL mysqlhost01:3306 ssl JS > Below is full command output with error message: Below are the message in MySQL error log: This issue is Caused by the old(original server) relay log information exiting in metadata tables ....
Read more