SQL DB restore error

Business Central/NAV Technical Forum
1

Hi ALL,

I have problem. If i SQL database restored I have error. How can i fix this error? please help me? :frowning:

Regards,

2

Seems to be that you are having less spaceā€¦Check the space on the diskā€¦

3

Actually the error does not apear to be disck sapce, but that the SQL database file is too small for the restore.

The fact that it happened so early in the restore indiates that you were way off in calculating the size.

How big is your backup file and how big is your database. And what version of Navision.

4

You could always set the DB files to grow automatically - not sure on the performance implications, but could get you going at least.

5

What kind of backup procedure did you use & what method did you use to restore? did you restore into a separate instance with the same name? were there active logins on that server?

It looks like your backup was corrupted, or finished incompletely. You may need to recreate the backup.

Has your backup procedure been working for you in the past? I keep test copies of my databases where I back them up and restore them monthly to play around with. I do this for several reasons, but one of them is to make sure my backups are working properly with use.

6

What makes you think that?

7

I agree with Mr. Singleton.

Are you restoring a NAV backup into the database? If so, then you need a databse that is about twice (2x) the size of the backup files.

Good Luck,

[:)]

8

Well David you know Iā€™m a novice to NAV, but unrelated to NAV and directed more at SQL I reattached a database once that was missing an entire table after the restore. We didnā€™t know it was missing the table until the application shot us an error. We honestly donā€™t know how that happened, but it did. We recreated our backup from the other server and reattached it - and it worked. The weird thing is that the restore process completed successfully and there was no error with the backup. It was also a small database about 2GB, only had 200+ tables in it. Fishy right?

So speaking from an obscure experience - I mentioned it as a suggestion to give it a shotā€¦ It canā€™t hurt to try. - from what everyone else is saying it seems like this has to do with the ā€œsizeā€ of the database. I already made a note to myself to research the requirements of NAV backup & restore proceduresā€¦ but I thought iā€™d throw something out there that may be semi useful.

9

From a SQL perspective the error message is pretty specific here - the filegroup is too small for the db to be restored into. I canā€™t see all the error message for some reason, however my suggestions are:

  1. Avoid using the NAV backup/restore whenever possible. I have found in my experience (with version 3 something) it performed significantly worse the a SQL DB restore and also needed lots of space in the transaction log and tempdb. My experience here may not be typical and I could have overlooked something obvious, but its my experience none the lessā€¦ I should add Iā€™m a SQL person who happens to be working with a NAV installation, not the other way around.

  2. Check the settings for the database files - see if they are set to automatically grow. If you have lots of disk space its a quick and easy way to get it through.

  3. If you donā€™t like autogrow - manually add new files to the filegroup, or extend the ones you already have.

cheers, Mark