@
leyendo...
Tecnología

Instalando SQL Server 2016 Developer Edition en Windows 10 – Parte 4

Luego de un largo receso en esta serie, retomamos con un post sobre como instalar la base de datos de ejemplo de Microsoft AdventureWorks.

Ahora bien, si Microsoft ha hecho un esfuerzo importante en generar y en poner a disposición de todos, un nuevo conjunto de bases de datos de ejemplo, ¿por qué quisiera tener la anterior? Bueno, entre otros argumentos, compatibilidad, algunos scripts que tengo para generar escenarios en cuanto a desempeño y revisión de algunos comportamientos y para probar algunos escenarios mientras domino Wide World Importers, el nuevo conjunto de bases de ejemplo para SQL Server 2016.

Lo primero es visitar el sitio en Codeplex, https://msftdbprodsamples.codeplex.com/, para descargar las bases de datos de ejemplo, la OLTP y la DW.

Posteriormente dar clic en el link de descarga de AdventureWorks Databases – 2014. Aparecerá la siguiente página:

Adventure Works 2014 en Codeplex

Lo que voy a hacer, por el momento, es descargar los dos archivos que dicen “Adventure Works 2014 Full Database Backup.zip” y “Adventure Works DW 2014 Full Database Backup.zip”.

Luego de descargarlos, extráiganlos a su ubicación por defecto para copias de respaldo. En mi caso en particular, quedaron así:

Archivos de respaldo

En el mismo sitio Web de donde descargué los dos archivos, hay un documento, tanto en Word como en PDF, que da instrucciones para restaurar las bases de datos.

Se ubica la sección en el documento que dice como instalar la base de datos desde un respaldo y se copia el script para hacerlo, teniendo presente modificar las carpetas en las cuales residen los archivos. En mi caso, se aprecian de esta manera:

Instrucciones T-SQL para restaurar las bases de datos

Al ejecutar estas instrucciones, se obtienen los siguientes resultados:

Processed 24248 pages for database ‘AdventureWorks2014’, file ‘AdventureWorks2014_Data’ on file 1.

Processed 4 pages for database ‘AdventureWorks2014’, file ‘AdventureWorks2014_Log’ on file 1.

Converting database ‘AdventureWorks2014’ from version 782 to the current version 852.

Database ‘AdventureWorks2014’ running the upgrade step from version 782 to version 801.

Database ‘AdventureWorks2014’ running the upgrade step from version 801 to version 802.

Database ‘AdventureWorks2014’ running the upgrade step from version 802 to version 803.

Database ‘AdventureWorks2014’ running the upgrade step from version 803 to version 804.

Database ‘AdventureWorks2014’ running the upgrade step from version 804 to version 805.

Database ‘AdventureWorks2014’ running the upgrade step from version 805 to version 806.

Database ‘AdventureWorks2014’ running the upgrade step from version 806 to version 807.

Database ‘AdventureWorks2014’ running the upgrade step from version 807 to version 808.

Database ‘AdventureWorks2014’ running the upgrade step from version 808 to version 809.

Database ‘AdventureWorks2014’ running the upgrade step from version 809 to version 810.

Database ‘AdventureWorks2014’ running the upgrade step from version 810 to version 811.

Database ‘AdventureWorks2014’ running the upgrade step from version 811 to version 812.

Database ‘AdventureWorks2014’ running the upgrade step from version 812 to version 813.

Database ‘AdventureWorks2014’ running the upgrade step from version 813 to version 814.

Database ‘AdventureWorks2014’ running the upgrade step from version 814 to version 815.

Database ‘AdventureWorks2014’ running the upgrade step from version 815 to version 816.

Database ‘AdventureWorks2014’ running the upgrade step from version 816 to version 817.

Database ‘AdventureWorks2014’ running the upgrade step from version 817 to version 818.

Database ‘AdventureWorks2014’ running the upgrade step from version 818 to version 819.

Database ‘AdventureWorks2014’ running the upgrade step from version 819 to version 820.

Database ‘AdventureWorks2014’ running the upgrade step from version 820 to version 821.

Database ‘AdventureWorks2014’ running the upgrade step from version 821 to version 822.

Database ‘AdventureWorks2014’ running the upgrade step from version 822 to version 823.

Database ‘AdventureWorks2014’ running the upgrade step from version 823 to version 824.

Database ‘AdventureWorks2014’ running the upgrade step from version 824 to version 825.

Database ‘AdventureWorks2014’ running the upgrade step from version 825 to version 826.

Database ‘AdventureWorks2014’ running the upgrade step from version 826 to version 827.

Database ‘AdventureWorks2014’ running the upgrade step from version 827 to version 828.

Database ‘AdventureWorks2014’ running the upgrade step from version 828 to version 829.

Database ‘AdventureWorks2014’ running the upgrade step from version 829 to version 830.

Database ‘AdventureWorks2014’ running the upgrade step from version 830 to version 831.

Database ‘AdventureWorks2014’ running the upgrade step from version 831 to version 832.

Database ‘AdventureWorks2014’ running the upgrade step from version 832 to version 833.

Database ‘AdventureWorks2014’ running the upgrade step from version 833 to version 834.

Database ‘AdventureWorks2014’ running the upgrade step from version 834 to version 835.

Database ‘AdventureWorks2014’ running the upgrade step from version 835 to version 836.

Database ‘AdventureWorks2014’ running the upgrade step from version 836 to version 837.

Database ‘AdventureWorks2014’ running the upgrade step from version 837 to version 838.

Database ‘AdventureWorks2014’ running the upgrade step from version 838 to version 839.

Database ‘AdventureWorks2014’ running the upgrade step from version 839 to version 840.

Database ‘AdventureWorks2014’ running the upgrade step from version 840 to version 841.

Database ‘AdventureWorks2014’ running the upgrade step from version 841 to version 842.

Database ‘AdventureWorks2014’ running the upgrade step from version 842 to version 843.

Database ‘AdventureWorks2014’ running the upgrade step from version 843 to version 844.

Database ‘AdventureWorks2014’ running the upgrade step from version 844 to version 845.

Database ‘AdventureWorks2014’ running the upgrade step from version 845 to version 846.

Database ‘AdventureWorks2014’ running the upgrade step from version 846 to version 847.

Database ‘AdventureWorks2014’ running the upgrade step from version 847 to version 848.

Database ‘AdventureWorks2014’ running the upgrade step from version 848 to version 849.

Database ‘AdventureWorks2014’ running the upgrade step from version 849 to version 850.

Database ‘AdventureWorks2014’ running the upgrade step from version 850 to version 851.

Database ‘AdventureWorks2014’ running the upgrade step from version 851 to version 852.

RESTORE DATABASE successfully processed 24252 pages in 4.051 seconds (46.769 MB/sec).

Processed 11696 pages for database ‘AdventureWorksDW2014’, file ‘AdventureWorksDW2014_Data’ on file 1.

Processed 4 pages for database ‘AdventureWorksDW2014’, file ‘AdventureWorksDW2014_Log’ on file 1.

Converting database ‘AdventureWorksDW2014’ from version 782 to the current version 852.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 782 to version 801.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 801 to version 802.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 802 to version 803.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 803 to version 804.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 804 to version 805.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 805 to version 806.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 806 to version 807.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 807 to version 808.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 808 to version 809.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 809 to version 810.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 810 to version 811.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 811 to version 812.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 812 to version 813.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 813 to version 814.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 814 to version 815.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 815 to version 816.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 816 to version 817.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 817 to version 818.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 818 to version 819.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 819 to version 820.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 820 to version 821.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 821 to version 822.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 822 to version 823.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 823 to version 824.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 824 to version 825.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 825 to version 826.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 826 to version 827.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 827 to version 828.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 828 to version 829.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 829 to version 830.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 830 to version 831.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 831 to version 832.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 832 to version 833.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 833 to version 834.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 834 to version 835.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 835 to version 836.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 836 to version 837.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 837 to version 838.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 838 to version 839.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 839 to version 840.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 840 to version 841.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 841 to version 842.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 842 to version 843.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 843 to version 844.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 844 to version 845.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 845 to version 846.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 846 to version 847.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 847 to version 848.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 848 to version 849.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 849 to version 850.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 850 to version 851.

Database ‘AdventureWorksDW2014’ running the upgrade step from version 851 to version 852.

RESTORE DATABASE successfully processed 11700 pages in 1.961 seconds (46.612 MB/sec).

Lo que significa, si ven los valores resaltados en amarillo, es que la operación de restauración hace un esfuerzo para llevar la versión de la base de datos, en este caso desde la 782, que es el número interno de versión que define SQL Server y que corresponde a SQL Server 2014, hacia la versión interna 852, que corresponde a SQL Server 2016.

Revisando estos resultados con el historial de SP, CU y FIX por versión, pareciera que hay relación entre dichos números de versiones internas con esto. Mirando en http://sqlserverbuilds.blogspot.com/#sql2014, es probable, aunque no encontré un documento o una posición oficial de Microsoft sobre que esto es así.

Ahora bien, si revisamos las propiedades de una de esas bases de datos para ver el nivel de compatibilidad, se aprecia lo siguiente:

Base de datos en Compatibility Level 2014

Es decir, la operación de RESTORE puso la base de datos en formato SQL Server 2016, pero mantiene el nivel de compatibilidad en el cual la base de datos fue creada. Esto es normal al restaurar desde una versión inferior hacia una superior. Se debe tener presente que el nivel de compatibilidad solo dice que características anteriores se quieren mantener; es decir, la base de datos quedó en 2016, pero con nivel de compatibilidad 2014. Si yo hago un backup de esta base de datos y trato de restaurarlo en 2014, no va a funcionar.

Todo por el momento. En otros posts revisaremos aspectos de esta base de datos, así como de la flamante Wide World Importers.

Saludos.

Anuncios

Comentarios

Los comentarios están cerrados.

Categorías

Archivos

A %d blogueros les gusta esto: