System Requirements

The following is provided as a general guideline on the

minimum system requirements.
Server (SQL)
Processor - Minimum: 1 GHz (x86 processor) or 1.4 GHz (x64 processor) or 1.0 GHz (IA64 processor)
Recommended: 2 GHz or faster (dual-core or quad-core will be much faster)
Limitations: SQL Server Express supports 1 physical processor, 1 GB memory, and 10 GB storage.
Memory - Minimum: 4 GB RAM 
Recommended: 8 GB RAM or Greater (more RAM up to 32 GB, better performance)
SQL Version- Microsoft SQL Server 2014 Express is provided with Miracle Service. 
Miracle Service SQL database is also compatible with: Microsoft SQL Server 2008 R2, Microsoft SQL
Server 2012 R2 and SQL Express 2012 R2. 
Microsoft does not recommended installing SQL Server on a domain controller (article)
Available Disk Space Minimum: 100 GB Free Disk Space on C: Drive
Other:
 Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server
2016. Or if dedicated PC acting as server: Windows 7 or 10 Professional (Minimum: 8 GB RAM)

 It is not recommended to install SQL Server on a domain controller.

 For any web portal we only support Internet Information Services (IIS) version 7.5 and later.
When running any Web Portal Applications on a 64 Bit operating system, the IIS Server must be
enabled for 32-bit applications. The IIS Server must also be on the same computer as the
database. We do not support MS Exchange or SharePoint on the same server as the web
portals or Customer Relationship Management (CRM) applications.

 The Customer Relationship Management (CRM) web portal requires Windows Server 2008

R2 (32-bit or 64-bit) and Internet Information Services (IIS) version 7.5 or later. When running
on a 64 Bit operating system, the IIS Server must be enabled for 32-bit applications.
Microsoft .NET Framework 4.0 or later and ASP.NET service for IIS are also required.
 For Document Manager and eForms applications running on the server we require Microsoft
.NET Framework 4.0 or later and ASP.NET services to be running in IIS. eForms can only be
installed with IIS 7.5 or later.

Client PC
Microsoft Windows 7 or 10 Pro versions.

Processor Minimum: 1 GHz (x86 processor or x64 processor) 

Recommended: 2 GHz or faster (dual-core or quad-core will be much faster)
Memory Minimum: 1 GB RAM for 32-bit system, 2 GB RAM for 64-bit systems 
Recommended: 2 GB RAM or greater
Available Disk Space Minimum: 16 GB for 32-bit systems, 20 GB for 64-bit systems 
Recommended: 40 GB or greater
Recommended Monitor Resolutions: 1920 x 1080 or 1366 x 768

Network
 Any Windows compatible network

Wireless Operating Systems

 iPhone & iPad: iOS11 or later
 Android: version 8.0.x (Oreo) or later
 Windows Mobile: 10.0
 Note: Signature Capture feature requires an HTML5 Compatible Browser.
 eForms Certificate Management module is supported on tablet devices only, and is
compatible with specific device specific PDF Readers as follows:
 iOS devices: PDF Expert Professional edition*
 Android: qPDF Notes Pro PDF Reader*
 Windows Mobile: Adobe Reader 10.X or Later (Not Mobile Edition)*
 *Note: these are third party products which may incur additional fees. We cannot
guarantee the compatibility with each new release and therefore recommend
customers test any new release prior to buying or installing multiple readers to
ensure the latest version remains compatible.

Web Browser
 For the Mobile Field Technician Console and Customer Self-Service Portal:  these web
modules are developed and tested to be compatible with the latest versions of Google
Chrome, Safari, Mozilla Firefox and Microsoft Edge. These modules support HTTP and HTTPS
protocols. HTTPS required for offline use.
 The Customer Relationship Manager (CRM) module is compatible with the latest version of
Google Chrome.

Technician Short Message Service/Text Feature

 Internet access and SMTP e-mail server access is required. Nexent will provide limited
support for third party SMTP servers as many security features can affect the operation of the
email and SMS services which are beyond Nexent's control.

Accounting Exporter
 QuickBooks: Compatible with 2011 or later versions of QuickBooks Desktop Pro, Premier
and Enterprise. Not compatible with Online version.
  Other Accounting Applications: Please check with us for compatibility with 20+ leading
accounting packages.

Regional Settings
Miracle Service is designed based on Regional Settings based on the most common international
notation standards. These are typically as follows:
 Currency formatting uses the comma thousand separator. (e.g. $1,572.34, €1,294.00)
 Date formatting uses either the dd/MM/yyyy or MM/dd/yyyy formatting.
 Number formatting uses the comma thousand separator. (e.g. 1,203, 10,965…etc.)
While we have customers using a variety of regional settings, we are aware there are some regional
settings which are incompatible with Miracle Service. In cases where a user's Regional Settings are
incompatible with Miracle Service, users will need to set-up a virtual computer (such as OracleBox™,
Virtual PC™ or other virtualized desktop or server software) so they can set-up a separate
environment compatible with Miracle Service.

Other
We recommend 100 Mbps Ethernet adapters for small networked installations and 1 GBps for sites
with a heavy workload.

While these are the minimum requirements, as with any software application, the faster the
computer and the more memory it has, the faster the software will run.

The number of concurrent users and/or the amount of data your business gathers define workload.

Nexent Innovations Inc. cannot support any operating system issues relating to usage, network
errors, disk errors or hardware issues.
Hardware and Software Requirements
for Installing SQL Server 2014
 07/10/2018
 22 minutes to read

o

o +2

 Try SQL Server 2016 by installing the Free Developer edition!

Considerations
  We recommend running SQL Server 2014 on computers with the NTFS file
format. FAT32 file system is supported but not recommended as it is less secure
than the NTFS file system.
 You cannot install on read-only, mapped, or compressed drives.
 To allow the Visual Studio component to install correctly, SQL Server requires you
to install an update. SQL Server Setup checks for the presence of this update then
requires you to download and install that update before you can continue with the
SQL Server installation. To avoid the interruption during SQL Server Setup,
download and install the update before running SQL Server Setup as described
below (or install all the updates for .NET 3.5 SP1 available on Windows Update):
o For Windows Server 2008 SP2, get the required update here.
o For any other supported operating system, this update is included.
 Launching SQL Server Setup through Terminal Services Client is not supported.
Installation fails if you launch setup through Terminal Services Client.
 SQL Server Setup installs the following software components required by the
product:
o SQL Server Native Client
o SQL Server Setup support files
 For minimum version requirements to install SQL Server on Windows Server 2012
or Windows 8, see Installing SQL Server on Windows Server 2012 or Windows
8(https://support.microsoft.com/kb/2681562).

This topic contains the following sections:

 Hardware and Software Requirements

 Processor, Memory, and Operating System Requirements
 Cross-Language Support
 Extended System Support
 Hard Disk Space Requirements (32-Bit and 64 Bit)
 Storage Types for Data Files
 Installing SQL Server on a Domain Controller
Hardware and Software Requirements
The following requirements apply to all SQL Server 2014 installations:
Component Requirement

.NET .NET 3.5 SP1 is a requirement for SQL Server 2014 when you select Database
Framework Engine, Reporting Services, Master Data Services, Data Quality Services,
Replication, or SQL Server Management Studio, and it is no longer installed by
Component Requirement

SQL Server Setup. 

-If you run Setup and you do not have .NET 3.5 SP1, SQL Server Setup requires
you to download and install .NET 3.5 SP1 before you can continue with the SQL
Server installation. (Install .NET 3.5 SP1 from Microsoft .NET Framework 3.5
Service Pack 1.) The error message includes a link to the download center, or you
can download .NET 3.5 SP1 from Windows Update. To avoid interruption during
SQL Server Setup, you can download and install .NET 3.5 SP1 before you run
SQL Server Setup.
-If you run Setup on a computer with Windows Server 2008 R2 SP1 or Windows
8, you must enable .NET Framework 3.5 SP1 before you install SQL Server 2014.
-If there is no internet access, you must download and install .NET Framework
3.5 SP1 before you run Setup to install any of the above mentioned components.
For more information about the recommendations and guidance on how to acquire
and enable .NET Framework 3.5 on Windows 8 and Windows Server 2012,
see Microsoft .NET Framework 3.5 Deployment
Considerations(https://msdn.microsoft.com/library/windows/hardware/hh975396)
.

.NET 4.0 is a requirement for SQL Server 2014. SQL Server installs .NET 4.0
during the feature installation step.
-If you are installing the SQL Server Express editions, ensure that an Internet
connection is available on the computer. SQL Server Setup downloads and
installs the .NET Framework 4 because it is not included in the SQL Server
Express media.
-SQL Server Express does not install .NET 4.0 on the Server Core mode of
Windows Server 2008 R2 SP1 or Windows Server 2012. You must install .NET
4.0 before you install SQL Server Express on a Server Core installation of
Windows Server 2008 R2 SP1 or Windows Server 2012.

Windows SQL Server 2014 does not install or enable Windows PowerShell 2.0; however
PowerShell Windows PowerShell 2.0 is an installation prerequisite for Database Engine
components and SQL Server Management Studio. If Setup reports that Windows
PowerShell 2.0 is not present, you can install or enable it by following the
instructions on the Windows Management Framework page.

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

Note: VIA protocol is not supported on failover clusters. Clients or applications

running on the same node of the failover cluster as the SQL Server instance, can
use Shared Memory protocol to connect to SQL Server using its local pipe
Component Requirement

address. However this type of connection is not cluster-aware and will fail after an
instance failover. It is therefore not recommended and should only be used in very
specific scenarios. The VIA protocol is deprecated. This feature will be removed
in a future version of Microsoft SQL Server. Avoid using this feature in new
development work, and plan to modify applications that currently use this feature.

For more information about Network Protocols and Network Libraries,

see Network Protocols and Network Libraries.

Virtualizatio SQL Server 2014 is supported in virtual machine environments running on the
n Hyper-V role in:
-
Windows Server 2008 SP2 Standard, Enterprise and Datacenter editions
-Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter editions.
-
Windows Server 2012 Datacenter and Standard editions.

In addition to resources required by the parent partition, each virtual machine

(child partition) must be provided with sufficient processor resources, memory,
and disk resources for its SQL Server 2014 instance. Requirements are listed later
in this topic.*

Within the Hyper-V role on Windows Server 2008 SP2 or Windows Server 2008
R2 SP1, a maximum of 4 (four) virtual processors can be allocated to virtual
machines running Windows Server 2008 SP2 32-bit/64-bit or Windows Server
2008 R2 SP1 64-bit or Windows Server 2012 64-bit editions.

Within the Hyper-V role on Windows Server 2012:

A maximum of 8 (eight) virtual processors can be allocated to virtual machines
running Windows Server 2008 SP2 32-bit/64-bit.
A maximum of 64 (sixty-four) virtual processors can be allocated to virtual
machines running Windows Server 2008 R2 SP1 64-bit or Windows Server 2012
64-bit editions.

For more information on compute capacity limits for different editions of SQL
Server 2014 and how they differ in physical and virtualized environments with
hyperthreaded processors, see Compute Capacity Limits by Edition of SQL
Server. For more information about the Hyper-V role, see the Windows Server
2008 Web site.

** Important ** Guest failover clustering is supported in SQL Server 2014. For

more information about the supported versions of SQL Server and operating
 Component Requirement

systems for guest failover clustering, and the support for virtualization,
see Support policy for Microsoft SQL Server products running in a hardware
virtual environment.

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

Disk space requirements will vary with the SQL Server 2014 components you
install. For more information, see Hard Disk Space Requirements (32-Bit and 64
Bit) later in this topic. For information on supported storage types for data files,
see Storage Types for Data Files.

Drive A DVD drive, as appropriate, is required for installation from disc.

Monitor SQL Server 2014 requires Super-VGA (800x600) or higher resolution monitor.

Internet Internet functionality requires Internet access (fees may apply).

*Running SQL Server 2014 on a virtual machine will be slower than running natively
because of the overhead of virtualization.
Processor, Memory, and Operating System
Requirements
The following memory and processor requirements apply to all editions of SQL Server
2014:
Component Requirement

Memory [1]
Minimum:

Express Editions: 512 MB

All other editions: 1 GB

Recommended:

Express Editions: 1 GB

All other editions: At least 4 GB and should be increased as database size

increases to ensure optimal performance.
 Component Requirement

Processor Minimum:
Speed
x86 Processor: 1.0 GHz

x64 Processor: 1.4 GHz

Recommended: 2.0 GHz or faster

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

x86 Processor: Pentium III-compatible processor or faster

The minimum memory required for installing the Data Quality Server component in
[1]

Data Quality Services (DQS) is 2 GB of RAM, which is different from the SQL Server 2014
minimum memory requirement. For information about installing DQS, see Install Data
Quality Services.
Performance improvements in SQL
Server 2014
March 18, 2014 · Klaus Aschenbrenner · 2 Comments

(Be sure to checkout the FREE SQLpassion Performance Tuning

Training Plan - you get a weekly email packed with all the essential
knowledge you need to know about performance tuning on SQL Server.)
SQL Server 2014 will be an amazing release regarding all the various
performance enhancements that are part of this new release. Over the last
months I have already done a huge amount of work and tests on the latest
CTP version of SQL Server 2014, and I have already blogged about my
experience. In this blog posting I want to give you an overview about the
various performance related enhancements that are introduced.

If you are interested in a more personal face-2-face training about

performance enhancements in SQL Server 2014, I’m also running in May &
June around Europe my one-day long SQL Server 2014 Performance
Tuning Day, where you will learn the nifty details about this various
enhancements.

Buffer Pool Extensions

The idea about Buffer Pool Extensions is very easy: expand the Buffer Pool
with a paging file that is stored on very fast storage, like SSD drives. The
Buffer Pool Extensions are coming quite handy, if you don’t have the ability
to physically add more additional RAM to your database server.

Resource Governor
Resource Governor was introduced first back with SQL Server 2008, but
wasn’t really a mature technology, because you had no possibility to govern
I/O operations on the storage level, and you also had no chance to limit the
size of the Buffer Pool for a specific workload group. With SQL Server 2014
things are changing, because you can now throttle I/O operations. Limiting
Buffer Pool usage is still not possible, but hey who knows what comes in
SQL Server 2016 ;-).

Lock Priorities
As you might know, SQL Server gives you in the Enterprise Edition Online
operations, or as I call them “Almost Online Operations”. They are almost
online, because internally SQL Server still has to acquire some locks, which
can lead to blocking situations. For that reason SQL Server 2014
introduces Lock Priorities, where you can control how SQL Server should
react, if such a blocking situation occurs.

Clustered ColumnStore Indexes

One of the hottest enhancements in SQL Server 2014 is the introduction
of Clustered ColumnStore Indexes, which is an amazingly new way
concept how to deal with ColumnStore data in SQL Server. And in addition
the Clustered ColumnStore Index can be also changed directly – without
using tricks like Partition Switching.

In-Memory OLTP
With In-Memory OLTP Microsoft claims that the performance of your
workload can be improved up to 100x. Awesome! Everything is now stored
directly in the memory, without touching your physical storage anymore
(besides the transaction log, if you want). And in addition In-Memory OLTP
is based on so-called Lock Free Data Structures, means locking, blocking,
latching, and spinlocking is just gone. Of course, there are side-effects and
even limitations with this promising approach…

Delayed Transactions
It doesn’t matter how good the throughput of your workload is, the final
barrier and bottleneck is almost every time the transaction log. Because of the
Write-Ahead Logging mechanism used by SQL Server, a transaction must be
always written physically to the transaction log, before the transaction is
committed. When your transaction log is on slow storage, your performance
and throughput will suffer. For that reason SQL Server 2014 implements so-
called Delayed Transactions…

Cardinality Estimation
Cardinality Estimation is the most important thing in a relational database,
because these estimations are feeded into the Query Optimizer, whose job it
is to produce a good-enough execution plan. With SQL Server 2014
Microsoft has rewritten the cardinality estimator completely from scratch to
overcome some limitations based on the history of this very important
component.
What’s New in SQL Server 2014 since SQL
Server 2012
PERFORMANCE & SCALE
o        In-Memory OLTP

o        Enhanced In-Memory ColumnStore for DW

o        Buffer Pool Extension to SSDs

o        Enhanced Query Processing

o        Resource Governor adds IO governance

o        SysPrep at cluster level

o        Predictable performance with tiering of compute, network, and storage with Windows Server 2012 R2

HIGH AVAILABILITY
o        Enhanced AlwaysOn, with 8 secondaries and Replica Wizard

o        Delayed Durability

o        Clustered Shared Volume support, VHDX support (Windows Server 2012 R2)

o        Manage on-premises and cloud apps (System Center 2012 R2)

SECURITY
o        Enhanced separation of duty

o        CC certification at High Assurance Level for 2014

o        Backup encryption support

PROGRAMMABILITY
o        Query optimization enhancements

EASY ACCESS TO DATA, BIG & SMALL

o        Power Query

o        Windows Azure HDInsight Service

o        Analytics Platform System (PDW V2)

POWERFUL INSIGHTS WITH FAMILIAR TOOLS

o        Power BI in Office 365

o        Power Map for Excel

o        Mobile interfaces for Power BI

 
HYBRID CLOUD SOLUTIONS
o        Simplified backup to Windows Azure

o        Support for backup of previous versions of SQL Server to Windows Azure

o        Cloud back-up encryption support

o        Simplified cloud Disaster Recovery with AlwaysOn replicas in Windows Azure VMs

EASY ON-RAMP TO THE CLOUD

o        New Windows Azure Deployment UI 
for SQL Server

o        Larger SQL Server VMs and memory sizes now available in Windows Azure