POR QU ESCGGER SQL SERVER?

SQL Server provides several options for creating high availability for a server or
database. The high-availability options include the following:
AlwaysOn Failover Cluster Instances
As part of the SQL Server AlwaysOn offering, AlwaysOn Failover Cluster Instances
leverages Windows Server Failover Clustering (WSFC) functionality to provide
local high availability through redundancy at the server-instance levela failover
cluster instance (FCI). An FCI is a single instance of SQL Server that is installed
across Windows Server Failover Clustering (WSFC) nodes and, possibly, across
multiple subnets. On the network, an FCI appears to be an instance of SQL Server
running on a single computer, but the FCI provides failover from one WSFC node
to another if the current node becomes unavailable.
For more information, see AlwaysOn Failover Cluster Instances (SQL Server).
AlwaysOn Availability Groups
AlwaysOn Availability Groups is an enterprise-level high-availability and disaster
recovery solution introduced in SQL Server 2012 to enable you to maximize
availability for one or more user databases. AlwaysOn Availability Groups requires
that the SQL Server instances reside on Windows Server Failover Clustering
(WSFC) nodes. For more information, see AlwaysOn Availability Groups (SQL
Server).
Note Note
An FCI can leverage AlwaysOn Availability Groups to provide remote disaster
recovery at the database level. For more information, see Failover Clustering and
AlwaysOn Availability Groups (SQL Server).
Database mirroring
Note Note
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. We recommend that you use AlwaysOn Availability
Groups instead.
Database mirroring is a solution to increase database availability by supporting
almost instantaneous failover. Database mirroring can be used to maintain a single
standby database, or mirror database, for a corresponding production database

that is referred to as the principal database. For more information, see Database
Mirroring (SQL Server).
Log shipping
Like AlwaysOn Availability Groups and database mirroring, log shipping operates at
the database level. You can use log shipping to maintain one or more warm
standby databases (referred to as secondary databases) for a single production
database that is referred to as the primary database. For more information about
log shipping, see About Log Shipping (SQL Server).
Arrow icon used with Back to Top link [Top]
Recommended Solutions for Using SQL Server to Protect Data
Our recommendation for providing data protection for your SQL Server
environment are as follows:
For data protection through a third-party shared disk solution (a SAN), we
recommend that you use AlwaysOn Failover Cluster Instances.
For data protection through SQL Server, we recommend that you use AlwaysOn
Availability Groups.
Note Note
If you are running an edition of SQL Server that does not support AlwaysOn
Availability Groups, we recommend log shipping. For information about which
editions of SQL Server support AlwaysOn Availability Groups, see the "High
Availability (AlwaysOn)" section of Features Supported by the Editions of SQL
Server 2014.
Source:
Microsoft SQL Server Standard Edition 2005 32 Bit CD/DVD 5 Client
$1599
http://www.amazon.com/Microsoft-Server-S...

Microsoft SQL Server Developer Edition 2005 CD/DVD

$44.95
http://www.amazon.com/Microsoft-SQL-Serv...

Microsoft SQL Server Workgroup Edition 2005 32 Bit CD/DVD 5 Client

$709 ( Esta es la mas comun a usar)
http://www.amazon.com/Microsoft-Server-W...

Microsoft SQL Server Standard Edition 2005 64 Bit CD/DVD 5 Client

$1913
http://www.amazon.com/Microsoft-Server-S...
ecuring SQL Server can be viewed as a series of steps, involving four areas: the
platform, authentication, objects (including data), and applications that access the
system. The following topics will guide you through creating and implementing an
effective security plan.
You can find more information about SQL Server security at the SQL Server Web
site. This includes a best practice guide and a security checklist. This site also
contains the latest service pack information and downloads.
Platform and Network Security
The platform for SQL Server includes the physical hardware and networking
systems connecting clients to the database servers, and the binary files that are
used to process database requests.
Physical Security
Best practices for physical security strictly limit access to the physical server and
hardware components. For example, use locked rooms with restricted access for
the database server hardware and networking devices. In addition, limit access to
backup media by storing it at a secure offsite location.
Implementing physical network security starts with keeping unauthorized users off
the network. The following table contains more information about networking
security information.

Operating System Security

Operating system service packs and upgrades include important security
enhancements. Apply all updates and upgrades to the operating system after you
test them with the database applications.
Firewalls also provide effective ways to implement security. Logically, a firewall is a
separator or restrictor of network traffic, which can be configured to enforce your

organization's data security policy. If you use a firewall, you will increase security at
the operating system level by providing a chokepoint where your security
measures can be focused. The following table contains more information about
how to use a firewall with SQL Server.
If your SQL Server system uses Internet Information Services (IIS), additional steps
are required to help secure the surface of the platform. The following table contains
information about SQL Server and Internet Information Services
SQL Server Operating System Files Security
SQL Server uses operating system files for operation and data storage. Best
practices for file security requires that you restrict access to these files. The
following table contains information about these files.

SQL Server Database Engine object

Maximum sizes/numbers SQL Server (32-bit)

Batch size1

65,536 * Network Packet Size

Bytes per short string column

8,000

Bytes per GROUP BY, ORDER BY

8,060

Bytes per index key2

900

Bytes per foreign key

900

Bytes per primary key

900

Bytes per row8

8,060

Bytes per row in memory-optimized tables

Not supported

Bytes in source text of a stored procedure

Lesser of batch size or 250 MB

Bytes
per varchar(max),varbinary(max), xml,
text, orimage column

2^31-1

Characters
per ntext ornvarchar(max) column

2^30-1

Clustered indexes per table

Columns in GROUP BY, ORDER BY

Limited only by number of bytes

Columns or expressions in a GROUP BY

WITH CUBE or WITH ROLLUP statement

10

Columns per index key7

16

Columns per foreign key

16

Columns per primary key

16

Columns per nonwide table

1,024

Columns per wide table

30,000

Columns per SELECT statement

4,096

Columns per INSERT statement

4096

Connections per client

Maximum value of configured connections

Database size

524,272 terabytes

Databases per instance of SQL Server

32,767

Filegroups per database

32,767

Filegroups per database for memoryoptimized data

Not supported

Files per database

32,767

File size (data)

16 terabytes

File size (log)

2 terabytes

Data files for memory-optimized data per

database

Not supported

Delta file per data file for memoryoptimized data

Not supported

Foreign key table references per table4

253

Identifier length (in characters)

128

Instances per computer

50 instances on a stand-alone server for all SQL Server ed

SQL Server supports 25 instances on a failover cluster wh
cluster disk as the stored option for you cluster installatio
supports 50 instances on a failover cluster if you choose S
the storage option for your cluster installation For more in
seeHardware and Software Requirements for Installing SQ

Indexes per memory-optimized table

Not supported

Length of a string containing SQL

statements (batch size)1

65,536 * Network packet size

Locks per connection

Maximum locks per server

Locks per instance of SQL Server5

Up to 2,147,483,647

Nested stored procedure levels6

32

Nested subqueries

32

Nested trigger levels

32

Nonclustered indexes per table

999

Number of distinct expressions in the

32

GROUP BY clause when any of the following

are present: CUBE, ROLLUP, GROUPING
SETS, WITH CUBE, WITH ROLLUP
Number of grouping sets generated by
operators in the GROUP BY clause

4,096

Parameters per stored procedure

2,100

Parameters per user-defined function

2,100

REFERENCES per table

253

Rows per table

Limited by available storage

Tables per database3

Limited by number of objects in a database

Partitions per partitioned table or index

1,000

Important

Creating a table or index with more than 1,000 partitions is

on a 32-bit system, but is not supported.
Statistics on non-indexed columns

30,000

Tables per SELECT statement

Limited only by available resources

Triggers per table3

Limited by number of objects in a database

Columns per UPDATE statement (Wide

Tables)

4096

User connections

32,767

XML indexes

249

instrucciones Transact-SQL.

Objeto SQL Server Motor de base de datos

Tamaos o cifras mximas SQL Server (32

Tamao de lote1

65.536 * Tamao de paquete de red

Bytes por columna de cadenas cortas

8,000

Bytes por GROUP BY y ORDER BY

8,060

Bytes por clave de ndice2

900

Bytes por clave externa

900

Bytes por clave principal

900

Bytes por fila8

8,060

Bytes por fila en tablas con optimizacin para memoria9

No compatible

Bytes en texto de origen de un procedimiento almacenado

El menor del tamao del lote o 250 MB

Bytes por
columnavarchar(max),varbinary(max), xml, text oimage

2^31-1

Caracteres por columnantext o nvarchar(max)

2^30-1

ndices clster por tabla

Columnas en GROUP BY y ORDER BY

Limitado solo por el nmero de bytes

Columnas o expresiones en una instruccin GROUP BY

WITH CUBE o WITH ROLLUP

10

Columnas por clave de ndice7

16

Columnas por clave externa

16

Columnas por clave principal

16

Columnas por tabla no ancha

1,024

Columnas por tabla ancha

30,000

Columnas por instruccin SELECT

4,096

Columnas por instruccin INSERT

4096

Conexiones por cliente

Valor mximo de conexiones configuradas

Tamao de la base de datos

524.272 terabytes

Bases de datos por instancia de SQL Server

32.767

Grupos de archivos por base de datos

32.767

Grupos de archivo por base de datos para datos con

optimizacin para memoria.

No compatible

Archivos por base de datos

32.767

Tamao de archivo (datos)

16 terabytes

Tamao de archivo (registro)

2 terabytes

Archivos de datos para datos con optimizacin para

memoria por base de datos

No compatible

Archivo delta por archivo de datos para datos con

optimizacin para memoria

No compatible

Referencias de tabla de claves externas por tabla4

253

Longitud del identificador (en caracteres)

128

Instancias por equipo

50 instancias en un servidor independiente par

SQL Server.

SQL Server admite 25 instancias en un clster

cuando se usa un disco de clster compartido
almacenamiento para la instalacin del clster
instancias en un clster de conmutacin por er
compartidos de archivos SMB como opcin d
instalacin del clster. Para obtener ms inform
hardware y software para instalar SQL Server

ndices por tabla con optimizacin para memoria

No compatible

Longitud de una cadena que contiene instrucciones SQL

(tamao de lote)1

65.536 * Tamao de paquete de red

Bloqueos por conexin

Mximo de bloqueos por servidor

Bloqueos por instancia de SQL Server5

Hasta 2.147.483.647

Niveles de procedimientos almacenados anidados6

32

Subconsultas anidadas

32

Niveles de desencadenadores anidados

32

ndices no clster por tabla

999

El nmero de expresiones distintas en la clusula BY

GROUP cuando cualquiera de los elementos siguientes est
presente: CUBE, ROLLUP, GROUPING SETS, WITH
CUBE, WITH ROLLUP

32

El nmero de conjuntos de agrupamiento generados por los

operadores de la clusula BY GROUP

4,096

Parmetros por procedimiento almacenado

2,100

Parmetros por funcin definida por el usuario

2,100

REFERENCES por tabla

253

Filas por tabla

Limitado por el espacio de almacenamiento di

Tablas por base de datos3

Limitado por el nmero de objetos de la base d

Particiones por tabla o ndice con particiones

1,000
Importante

Es posible crear una tabla o un ndice con m

en un sistema de 32 bits, pero no se admite.
Estadsticas en columnas no indizadas

30,000

Tablas por instruccin SELECT

Limitado solo por los recursos disponibles

Desencadenadores por tabla3

Limitado por el nmero de objetos de la base d

Columnas por instruccin UPDATE (tablas anchas)

4096

Conexiones de usuario

32.767

ndices XML

249