1

Topic: Basis contents at recovery differ

Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64)
Oct 28 2016 6:17:30 PM
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows 10 Pro 6.3 <X64> (Build 15063:) (Hypervisor)
If through the menu in studio those contents of the table one, if through a scratch that another.

use master
go
RESTORE DATABASE
ADM5600
FROM
DISK = ' o:\JIRA\RIS-5600\ADM_v271EU.bak'
WITH
MOVE ' ADM_v271EU_dat ' TO ' o:\db\ADM5600.mdf ',
MOVE ' ADM_v271EU_log ' TO ' o:\log\ADM5600_log. LDF'

Where to run and what to do?

2

Re: Basis contents at recovery differ

Processed 704 pages for database ' ADM5600 ', file ' ADM_v271EU_dat ' on file 1.
Processed 5 pages for database ' ADM5600 ', file ' ADM_v271EU_log ' on file 1.
Converting database ' ADM5600 ' from version 782 to the current version 852.
Database ' ADM5600 ' running the upgrade step from version 782 to version 801.
Database ' ADM5600 ' running the upgrade step from version 801 to version 802.
Database ' ADM5600 ' running the upgrade step from version 802 to version 803.
Database ' ADM5600 ' running the upgrade step from version 803 to version 804.
Database ' ADM5600 ' running the upgrade step from version 804 to version 805.
Database ' ADM5600 ' running the upgrade step from version 805 to version 806.
Database ' ADM5600 ' running the upgrade step from version 806 to version 807.
Database ' ADM5600 ' running the upgrade step from version 807 to version 808.
Database ' ADM5600 ' running the upgrade step from version 808 to version 809.
Database ' ADM5600 ' running the upgrade step from version 809 to version 810.
Database ' ADM5600 ' running the upgrade step from version 810 to version 811.
Database ' ADM5600 ' running the upgrade step from version 811 to version 812.
Database ' ADM5600 ' running the upgrade step from version 812 to version 813.
Database ' ADM5600 ' running the upgrade step from version 813 to version 814.
Database ' ADM5600 ' running the upgrade step from version 814 to version 815.
Database ' ADM5600 ' running the upgrade step from version 815 to version 816.
Database ' ADM5600 ' running the upgrade step from version 816 to version 817.
Database ' ADM5600 ' running the upgrade step from version 817 to version 818.
Database ' ADM5600 ' running the upgrade step from version 818 to version 819.
Database ' ADM5600 ' running the upgrade step from version 819 to version 820.
Database ' ADM5600 ' running the upgrade step from version 820 to version 821.
Database ' ADM5600 ' running the upgrade step from version 821 to version 822.
Database ' ADM5600 ' running the upgrade step from version 822 to version 823.
Database ' ADM5600 ' running the upgrade step from version 823 to version 824.
Database ' ADM5600 ' running the upgrade step from version 824 to version 825.
Database ' ADM5600 ' running the upgrade step from version 825 to version 826.
Database ' ADM5600 ' running the upgrade step from version 826 to version 827.
Database ' ADM5600 ' running the upgrade step from version 827 to version 828.
Database ' ADM5600 ' running the upgrade step from version 828 to version 829.
Database ' ADM5600 ' running the upgrade step from version 829 to version 830.
Database ' ADM5600 ' running the upgrade step from version 830 to version 831.
Database ' ADM5600 ' running the upgrade step from version 831 to version 832.
Database ' ADM5600 ' running the upgrade step from version 832 to version 833.
Database ' ADM5600 ' running the upgrade step from version 833 to version 834.
Database ' ADM5600 ' running the upgrade step from version 834 to version 835.
Database ' ADM5600 ' running the upgrade step from version 835 to version 836.
Database ' ADM5600 ' running the upgrade step from version 836 to version 837.
Database ' ADM5600 ' running the upgrade step from version 837 to version 838.
Database ' ADM5600 ' running the upgrade step from version 838 to version 839.
Database ' ADM5600 ' running the upgrade step from version 839 to version 840.
Database ' ADM5600 ' running the upgrade step from version 840 to version 841.
Database ' ADM5600 ' running the upgrade step from version 841 to version 842.
Database ' ADM5600 ' running the upgrade step from version 842 to version 843.
Database ' ADM5600 ' running the upgrade step from version 843 to version 844.
Database ' ADM5600 ' running the upgrade step from version 844 to version 845.
Database ' ADM5600 ' running the upgrade step from version 845 to version 846.
Database ' ADM5600 ' running the upgrade step from version 846 to version 847.
Database ' ADM5600 ' running the upgrade step from version 847 to version 848.
Database ' ADM5600 ' running the upgrade step from version 848 to version 849.
Database ' ADM5600 ' running the upgrade step from version 849 to version 850.
Database ' ADM5600 ' running the upgrade step from version 850 to version 851.
Database ' ADM5600 ' running the upgrade step from version 851 to version 852.
RESTORE DATABASE successfully processed 709 pages in 0.542 seconds (10.219 MB/sec).
The file name ' ADM5600DATA ' has been set.
The file name ' ADM5600_log ' has been set.

3

Re: Basis contents at recovery differ

And what for to throw out here exhaust contents ?
It is necessary 2 commands ,  and  studio.

4

Re: Basis contents at recovery differ

It appeared that WITH File=3 solve a problem but how to understand that 3 instead of 5 or 10?

5

Re: Basis contents at recovery differ

Lepsik wrote:

It appeared that WITH File=3 solve a problem but how to understand that 3 instead of 5 or 10?

it is not necessary to add  in one file. Then such problems will not be.

6

Re: Basis contents at recovery differ

It to me is sent QA by me I try to automate result.

7

Re: Basis contents at recovery differ

Lepsik wrote:

it to me is sent QA by me I try to automate result.

result "restore headeronly from disk =..." In temporary barracks, analyze result and be recovered from necessary

8

Re: Basis contents at recovery differ

Thanks I already in  looked whence 3 undertook, there it was valid 3