SQL Server Msg 1105, Level 17, State 2, Line 1

Dear (and mighty) all:

I backed up a database (SQL server 7.0) and tried to restore it on
another system (SQL Server 2000). This is not the first time I'm doing
this and never had a problem before:

-- in the source db
BACKUP db_icoaraci TO DISK = 'C:\TEMP\BACKUP-ICOARACI.DAT'

--in the destination db
RESTORE db_icoaraci FROM  DISK='E:\TEMP\BACKUP
-ICOARACI.DAT'
WITH MOVE='ICOARACI_DAT' TO 'E:\DB\ICOARACI.MDF',
MOVE='ICOARACI_LOG' TO 'E:\DB\ICOARACI.LDF'

Today, to my surprise, the destination SQL returned the following
error:

Processed 25592 pages for database 'db_icoaraci', file 'ICOARACI_DAT'
on file 1.
Processed 1 pages for database 'db_icoaraci', file 'ICOARACI_LOG' on
file 1.
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object '(SYSTEM table id: 6)' in database
'db_icoaraci' because the 'PRIMARY' filegroup is full.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.

I searched the list and a found a few posts refering to the same error,
but none in the exactly same scenario.

I tried to restore the database with NORECOVERY, and, before restoring
the log, increase its size (ALTER DATABASE ... etc), but SQL Server
says that the DB couldn't be open because it's in the middle of a
restore...

I'll appreciate any help.

Regards,

Branco.

Branco Medeiros (branco.medeiros@gmail.com)  writes:
> Today, to my surprise, the destination SQL returned the following
> error:
>
> Processed 25592 pages for database 'db_icoaraci', file 'ICOARACI_DAT'
> on file 1.
> Processed 1 pages for database 'db_icoaraci', file 'ICOARACI_LOG' on
> file 1.
> Server: Msg 1105, Level 17, State 2, Line 1
> Could not allocate space for object '(SYSTEM table id: 6)' in database
> 'db_icoaraci' because the 'PRIMARY' filegroup is full.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
> I searched the list and a found a few posts refering to the same error,
> but none in the exactly same scenario.

Looks like you have run out of disk space. Probably the database autogrows
as part of the upgrade to SQL 2000. For an autogrow to succeed there has to
be so much space available.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Erland Sommarskog wrote:
<snip>
Looks like you have run out of disk space.
<snip>

Nope, plenty of space. The backup file is 200 MB and the HD where it's
being restored to still has 19.7 GB of free space.

Thanks for the effort, though.

Regards,

Branco.

Branco Medeiros (branco.medeiros@gmail.com)  writes:
> Erland Sommarskog wrote:
><snip>
> Looks like you have run out of disk space.
><snip>
>
> Nope, plenty of space. The backup file is 200 MB and the HD where it's
> being restored to still has 19.7 GB of free space.

If you do an sp_helpdb on the database in SQL 7, what do you see for
autogrow?

If you comes as far so you can do sp_helpdb on the database in SQL 2000,
what do you see for autogrow there?

I would expect autogrow to be turned off completely, or possibly be set
to some completely wacko value like 20 GB.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx