Restoring sql server 7.0 database into sql server 2005 express - problem!

Hi!

I'm a beginner w ith SQL Express and am having some problems. I am using 2005 SP1 and installed the SQL Server Management Studio Express as well. I have a backup from a SQL Server 7.0 database that I am trying to restore into my database using the management studio. When I try to restore from the file into my database, I get the error,

System.Data.SqlClient.SqlError: The backup of the system database on the device D:\GMBeta2Local.bak cannot be restored because it was created by a different version of the server (7.00.1063) than this server (9.00.3033). (Microsoft.SqlServer.Express.Smo)

Is this true? Is there any way for me to get this data into my SQL Server 2005 express on my laptop?

hi,

thi message is usually raised when a system database is tried to be restored across different SQL Server versions, as reported in http://support.microsoft.com/kb/264474/en-us..

you should only "upgrade" user's databases..

regards

Restoring databases on SQL Server 2000 while trying not to restore to the wrong database

Experts,
Running Windows Server 2003 SP1 with SQL Server 2000 SP4. I have a couple
of development teams using databases on the same SQL Server. While they can
backup their databases, they cannot restore their own databases. I have
noticed that the SQL server role overwrite the DB roles on each user
database. Users have to have DB creator permission in order to restore the
existing database. However, this role also grants users to ability to
restore DB to other users database's. Is there any way around this, so that
I could give my development users rights to restore THEIR OWN database but
not right to restore database created by someone else?
--
SpinHi
You could do this by letting them have their own instance, but then you may
as well get copies of developer edition for them!
Why do you not trust them?
John
"Spin" wrote:
> Experts,
> Running Windows Server 2003 SP1 with SQL Server 2000 SP4. I have a couple
> of development teams using databases on the same SQL Server. While they can
> backup their databases, they cannot restore their own databases. I have
> noticed that the SQL server role overwrite the DB roles on each user
> database. Users have to have DB creator permission in order to restore the
> existing database. However, this role also grants users to ability to
> restore DB to other users database's. Is there any way around this, so that
> I could give my development users rights to restore THEIR OWN database but
> not right to restore database created by someone else?
> --
> Spin
>
>|||I do not want them accidentally restoring onto someone else's database.
--
Spin
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:30C46FD5-B979-4B35-AEAE-0B6885F9EA57@.microsoft.com...
> Hi
> You could do this by letting them have their own instance, but then you
> may
> as well get copies of developer edition for them!
> Why do you not trust them?
> John
>
> "Spin" wrote:
>> Experts,
>> Running Windows Server 2003 SP1 with SQL Server 2000 SP4. I have a
>> couple
>> of development teams using databases on the same SQL Server. While they
>> can
>> backup their databases, they cannot restore their own databases. I have
>> noticed that the SQL server role overwrite the DB roles on each user
>> database. Users have to have DB creator permission in order to restore
>> the
>> existing database. However, this role also grants users to ability to
>> restore DB to other users database's. Is there any way around this, so
>> that
>> I could give my development users rights to restore THEIR OWN database
>> but
>> not right to restore database created by someone else?
>> --
>> Spin
>>|||Hi
Proper use of a source code contol system, and a regular backup regime for
you development server would reduce the potential for loss if this does
occur. Maybe you should allocate the privileges to more senior members of the
team only?
John
"Spin" wrote:
> I do not want them accidentally restoring onto someone else's database.
> --
> Spin
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:30C46FD5-B979-4B35-AEAE-0B6885F9EA57@.microsoft.com...
> > Hi
> >
> > You could do this by letting them have their own instance, but then you
> > may
> > as well get copies of developer edition for them!
> >
> > Why do you not trust them?
> >
> > John
> >
> >
> > "Spin" wrote:
> >
> >> Experts,
> >>
> >> Running Windows Server 2003 SP1 with SQL Server 2000 SP4. I have a
> >> couple
> >> of development teams using databases on the same SQL Server. While they
> >> can
> >> backup their databases, they cannot restore their own databases. I have
> >> noticed that the SQL server role overwrite the DB roles on each user
> >> database. Users have to have DB creator permission in order to restore
> >> the
> >> existing database. However, this role also grants users to ability to
> >> restore DB to other users database's. Is there any way around this, so
> >> that
> >> I could give my development users rights to restore THEIR OWN database
> >> but
> >> not right to restore database created by someone else?
> >>
> >> --
> >> Spin
> >>
> >>
> >>
>
>