How to troubleshoot "3183" error when importing a database in SQLSERVER 2012

1

Good afternoon! To begin with, I warn you that I am a layman. I need to run a local bank on my machine to work on a project.

I installed the programs: SQLSERVER Express 2012 SQL Management Studio 2012

I use a Macbook Pro and squeeze a Win7 VM through Paralells.

The database they sent me has 8GB and the guidelines were to rename the file to .dmp and run the query:

RESTORE DATABASE meu_banco
    FROM DISK = N'C:\meu_banco.dmp'
WITH REPLACE,
MOVE 'vod_muzika' TO 'C:\sqlserver\meu_banco.mdf',
MOVE 'vod_muzika_log' TO 'C:\sqlserver\meu_banco.ldf'
GO

But I get the error:

  

Msg 3183, Level 16, State 2, Line 1 RESTORE detected an error on page   (8192: 536879104) in database "vod_muzika" as read from the backup set.   Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating   abnormally.

From what I researched on the internet, it looks like the bank is corrupted. Being that I already downloaded this bank 4x and other people downloaded the same bank and were able to import without problems. The error is only with me.

Is there any other possibility without being corrupted and how could I resolve it?

UPDATE

Following the tip of my friend Reginaldo, I did the following:

RESTORE DATABASE meu_banco 
FROM DISK = N'C:\meu_banco.dmp'
WITH CONTINUE_AFTER_ERROR, REPLACE,
MOVE 'meu_banco' TO 'C:\sqlserver\vod_muzika.mdf',
MOVE 'meu_banco_log' TO 'C:\sqlserver\vod_muzika.ldf';
GO

I tried WITH WITH RECOVERY too and I had the following error:

  

Location: gfh.cpp: 2911 Expression: rec.Size () < MAX_PROPERTY_ROW_LENGTH SPID: 52 Process ID: 1820 Msg 3013, Level   16, State 1, Line 2 RESTORE DATABASE is terminating abnormally. Msg   3624, Level 20, State 1, Line 2 A system assertion check has failed.   Check the SQL Server error log for details. Typically, an assertion   failure is caused by a software bug or data corruption. To check for   database corruption, consider running DBCC CHECKDB. If you agreed to   send dumps to Microsoft during setup, the mini dump will be sent to   Microsoft. An update might be available from Microsoft in the latest   Service Pack or in a QFE from Technical Support.

    
asked by anonymous 02.03.2017 / 17:10

1 answer

1

Yes it is corrupted. You must miss something. To continue the restore even after the error use

RECOVER DATABASE ... WITH CONTINUE_AFTER_ERROR

The bank will be in SUSPECT after the restore and you can try to repair it.

    
02.03.2017 / 17:15