I have a 2-part question.
1. I'm looking for a good strategy to save my data that I use for testing.
I made a set of good test data, and backed it up. I write my programs,
enter test trx, and then I want to start fresh again, so I restore from my
test data backup. This works fine.
For kicks, I tried to export the data to a new database. That worked fine.
But if I try to export data from the new database into my existing database,
I get lots duplicate key errors. I even tried setting the option to Delete
data, but that doesn't work because of foreign key constraints setup on some
of the tables.
Just curious what the recommened strategy for restoring test data is to
start anew!
2. When I make a change to the database, my collegues may have their own
test data and don't want to restore the test data that I have, but need the
database changes. What is the best way to do this? Should I just generate
the scripts for the tables I have changed?
Thanks for you help.If you want to start a fresh, then why not just drop the tables in the right
order, recreate the tables, and repopulate them with data?
This way, you will get to have scripts for both strucutres of the tables,
and data. So, if you only want structure, just run those CREATE TABLE
scripts.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Nancy De Cecco" <smiling.nancy@.verizon.net> wrote in message
news:#T0Iy5g2DHA.2620@.TK2MSFTNGP09.phx.gbl...
I have a 2-part question.
1. I'm looking for a good strategy to save my data that I use for testing.
I made a set of good test data, and backed it up. I write my programs,
enter test trx, and then I want to start fresh again, so I restore from my
test data backup. This works fine.
For kicks, I tried to export the data to a new database. That worked fine.
But if I try to export data from the new database into my existing database,
I get lots duplicate key errors. I even tried setting the option to Delete
data, but that doesn't work because of foreign key constraints setup on some
of the tables.
Just curious what the recommened strategy for restoring test data is to
start anew!
2. When I make a change to the database, my collegues may have their own
test data and don't want to restore the test data that I have, but need the
database changes. What is the best way to do this? Should I just generate
the scripts for the tables I have changed?
Thanks for you help.
Showing posts with label backed. Show all posts
Showing posts with label backed. Show all posts
Monday, March 26, 2012
Restoring test data
I have a 2-part question.
1. I'm looking for a good strategy to save my data that I use for testing.
I made a set of good test data, and backed it up. I write my programs,
enter test trx, and then I want to start fresh again, so I restore from my
test data backup. This works fine.
For kicks, I tried to export the data to a new database. That worked fine.
But if I try to export data from the new database into my existing database,
I get lots duplicate key errors. I even tried setting the option to Delete
data, but that doesn't work because of foreign key constraints setup on some
of the tables.
Just curious what the recommened strategy for restoring test data is to
start anew!
2. When I make a change to the database, my collegues may have their own
test data and don't want to restore the test data that I have, but need the
database changes. What is the best way to do this? Should I just generate
the scripts for the tables I have changed?
Thanks for you help.If you want to start a fresh, then why not just drop the tables in the right
order, recreate the tables, and repopulate them with data?
This way, you will get to have scripts for both strucutres of the tables,
and data. So, if you only want structure, just run those CREATE TABLE
scripts.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Nancy De Cecco" <smiling.nancy@.verizon.net> wrote in message
news:#T0Iy5g2DHA.2620@.TK2MSFTNGP09.phx.gbl...
I have a 2-part question.
1. I'm looking for a good strategy to save my data that I use for testing.
I made a set of good test data, and backed it up. I write my programs,
enter test trx, and then I want to start fresh again, so I restore from my
test data backup. This works fine.
For kicks, I tried to export the data to a new database. That worked fine.
But if I try to export data from the new database into my existing database,
I get lots duplicate key errors. I even tried setting the option to Delete
data, but that doesn't work because of foreign key constraints setup on some
of the tables.
Just curious what the recommened strategy for restoring test data is to
start anew!
2. When I make a change to the database, my collegues may have their own
test data and don't want to restore the test data that I have, but need the
database changes. What is the best way to do this? Should I just generate
the scripts for the tables I have changed?
Thanks for you help.|||check out DB Ghost @. www.dbghost.com for an excellent SQL
source code change management.
Building databases, migrating data, schema changes, static
data changes etc...
regards,
Mark Baekdal
>--Original Message--
>I have a 2-part question.
>1. I'm looking for a good strategy to save my data that
I use for testing.
>I made a set of good test data, and backed it up. I
write my programs,
>enter test trx, and then I want to start fresh again, so
I restore from my
>test data backup. This works fine.
>For kicks, I tried to export the data to a new database.
That worked fine.
>But if I try to export data from the new database into my
existing database,
>I get lots duplicate key errors. I even tried setting
the option to Delete
>data, but that doesn't work because of foreign key
constraints setup on some
>of the tables.
>Just curious what the recommened strategy for restoring
test data is to
>start anew!
>2. When I make a change to the database, my collegues
may have their own
>test data and don't want to restore the test data that I
have, but need the
>database changes. What is the best way to do this?
Should I just generate
>the scripts for the tables I have changed?
>Thanks for you help.
>
>.
>
1. I'm looking for a good strategy to save my data that I use for testing.
I made a set of good test data, and backed it up. I write my programs,
enter test trx, and then I want to start fresh again, so I restore from my
test data backup. This works fine.
For kicks, I tried to export the data to a new database. That worked fine.
But if I try to export data from the new database into my existing database,
I get lots duplicate key errors. I even tried setting the option to Delete
data, but that doesn't work because of foreign key constraints setup on some
of the tables.
Just curious what the recommened strategy for restoring test data is to
start anew!
2. When I make a change to the database, my collegues may have their own
test data and don't want to restore the test data that I have, but need the
database changes. What is the best way to do this? Should I just generate
the scripts for the tables I have changed?
Thanks for you help.If you want to start a fresh, then why not just drop the tables in the right
order, recreate the tables, and repopulate them with data?
This way, you will get to have scripts for both strucutres of the tables,
and data. So, if you only want structure, just run those CREATE TABLE
scripts.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Nancy De Cecco" <smiling.nancy@.verizon.net> wrote in message
news:#T0Iy5g2DHA.2620@.TK2MSFTNGP09.phx.gbl...
I have a 2-part question.
1. I'm looking for a good strategy to save my data that I use for testing.
I made a set of good test data, and backed it up. I write my programs,
enter test trx, and then I want to start fresh again, so I restore from my
test data backup. This works fine.
For kicks, I tried to export the data to a new database. That worked fine.
But if I try to export data from the new database into my existing database,
I get lots duplicate key errors. I even tried setting the option to Delete
data, but that doesn't work because of foreign key constraints setup on some
of the tables.
Just curious what the recommened strategy for restoring test data is to
start anew!
2. When I make a change to the database, my collegues may have their own
test data and don't want to restore the test data that I have, but need the
database changes. What is the best way to do this? Should I just generate
the scripts for the tables I have changed?
Thanks for you help.|||check out DB Ghost @. www.dbghost.com for an excellent SQL
source code change management.
Building databases, migrating data, schema changes, static
data changes etc...
regards,
Mark Baekdal
>--Original Message--
>I have a 2-part question.
>1. I'm looking for a good strategy to save my data that
I use for testing.
>I made a set of good test data, and backed it up. I
write my programs,
>enter test trx, and then I want to start fresh again, so
I restore from my
>test data backup. This works fine.
>For kicks, I tried to export the data to a new database.
That worked fine.
>But if I try to export data from the new database into my
existing database,
>I get lots duplicate key errors. I even tried setting
the option to Delete
>data, but that doesn't work because of foreign key
constraints setup on some
>of the tables.
>Just curious what the recommened strategy for restoring
test data is to
>start anew!
>2. When I make a change to the database, my collegues
may have their own
>test data and don't want to restore the test data that I
have, but need the
>database changes. What is the best way to do this?
Should I just generate
>the scripts for the tables I have changed?
>Thanks for you help.
>
>.
>
restoring system databases
I've been testing a new 2005 server. After the install, I backed up the
system databases. I've done a lot of junk testing stuff since then, and
now I'm wondering if I should do a restore of the system databases before I
put the machine into production. If so, which ones?If you want a clean start, consider running rebuildmaster - rerun setup with
rebuild flag.
e.g.
setup.exe REBUILDDATABASE=1
-oj
"HK" <replywithingroup@.notreal.com> wrote in message
news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
> I've been testing a new 2005 server. After the install, I backed up the
> system databases. I've done a lot of junk testing stuff since then, and
> now I'm wondering if I should do a restore of the system databases before
> I
> put the machine into production. If so, which ones?
>|||Does that put it into the same state as just after an install?
If I had a test database still showing, for example, would that disappear?
"oj" <nospam_ojngo@.home.com> wrote in message
news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
> If you want a clean start, consider running rebuildmaster - rerun setup
with
> rebuild flag.
> e.g.
> setup.exe REBUILDDATABASE=1
>
> --
> -oj
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
the[vbcol=seagreen]
and[vbcol=seagreen]
before[vbcol=seagreen]
>|||Correct. The system would look as if it's just installed.
Since the setup does not touch your user database, you can just reattach it
after the rebuild.
-oj
"HK" <replywithingroup@.notreal.com> wrote in message
news:0SnXf.18403$WK1.7806@.tornado.socal.rr.com...
> Does that put it into the same state as just after an install?
> If I had a test database still showing, for example, would that disappear?
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
> with
> the
> and
> before
>|||That's a neat trick. Thanks.
"oj" <nospam_ojngo@.home.com> wrote in message
news:OgXKirUVGHA.5900@.tk2msftngp13.phx.gbl...
> Correct. The system would look as if it's just installed.
> Since the setup does not touch your user database, you can just reattach
it
> after the rebuild.
> --
> -oj
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:0SnXf.18403$WK1.7806@.tornado.socal.rr.com...
disappear?[vbcol=seagreen]
>sql
system databases. I've done a lot of junk testing stuff since then, and
now I'm wondering if I should do a restore of the system databases before I
put the machine into production. If so, which ones?If you want a clean start, consider running rebuildmaster - rerun setup with
rebuild flag.
e.g.
setup.exe REBUILDDATABASE=1
-oj
"HK" <replywithingroup@.notreal.com> wrote in message
news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
> I've been testing a new 2005 server. After the install, I backed up the
> system databases. I've done a lot of junk testing stuff since then, and
> now I'm wondering if I should do a restore of the system databases before
> I
> put the machine into production. If so, which ones?
>|||Does that put it into the same state as just after an install?
If I had a test database still showing, for example, would that disappear?
"oj" <nospam_ojngo@.home.com> wrote in message
news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
> If you want a clean start, consider running rebuildmaster - rerun setup
with
> rebuild flag.
> e.g.
> setup.exe REBUILDDATABASE=1
>
> --
> -oj
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
the[vbcol=seagreen]
and[vbcol=seagreen]
before[vbcol=seagreen]
>|||Correct. The system would look as if it's just installed.
Since the setup does not touch your user database, you can just reattach it
after the rebuild.
-oj
"HK" <replywithingroup@.notreal.com> wrote in message
news:0SnXf.18403$WK1.7806@.tornado.socal.rr.com...
> Does that put it into the same state as just after an install?
> If I had a test database still showing, for example, would that disappear?
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
> with
> the
> and
> before
>|||That's a neat trick. Thanks.
"oj" <nospam_ojngo@.home.com> wrote in message
news:OgXKirUVGHA.5900@.tk2msftngp13.phx.gbl...
> Correct. The system would look as if it's just installed.
> Since the setup does not touch your user database, you can just reattach
it
> after the rebuild.
> --
> -oj
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:0SnXf.18403$WK1.7806@.tornado.socal.rr.com...
disappear?[vbcol=seagreen]
>sql
restoring system databases
I've been testing a new 2005 server. After the install, I backed up the
system databases. I've done a lot of junk testing stuff since then, and
now I'm wondering if I should do a restore of the system databases before I
put the machine into production. If so, which ones?
If you want a clean start, consider running rebuildmaster - rerun setup with
rebuild flag.
e.g.
setup.exe REBUILDDATABASE=1
-oj
"HK" <replywithingroup@.notreal.com> wrote in message
news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
> I've been testing a new 2005 server. After the install, I backed up the
> system databases. I've done a lot of junk testing stuff since then, and
> now I'm wondering if I should do a restore of the system databases before
> I
> put the machine into production. If so, which ones?
>
|||Does that put it into the same state as just after an install?
If I had a test database still showing, for example, would that disappear?
"oj" <nospam_ojngo@.home.com> wrote in message
news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
> If you want a clean start, consider running rebuildmaster - rerun setup
with[vbcol=seagreen]
> rebuild flag.
> e.g.
> setup.exe REBUILDDATABASE=1
>
> --
> -oj
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
the[vbcol=seagreen]
and[vbcol=seagreen]
before
>
|||Correct. The system would look as if it's just installed.
Since the setup does not touch your user database, you can just reattach it
after the rebuild.
-oj
"HK" <replywithingroup@.notreal.com> wrote in message
news:0SnXf.18403$WK1.7806@.tornado.socal.rr.com...
> Does that put it into the same state as just after an install?
> If I had a test database still showing, for example, would that disappear?
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
> with
> the
> and
> before
>
|||That's a neat trick. Thanks.
"oj" <nospam_ojngo@.home.com> wrote in message
news:OgXKirUVGHA.5900@.tk2msftngp13.phx.gbl...
> Correct. The system would look as if it's just installed.
> Since the setup does not touch your user database, you can just reattach
it[vbcol=seagreen]
> after the rebuild.
> --
> -oj
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:0SnXf.18403$WK1.7806@.tornado.socal.rr.com...
disappear?
>
system databases. I've done a lot of junk testing stuff since then, and
now I'm wondering if I should do a restore of the system databases before I
put the machine into production. If so, which ones?
If you want a clean start, consider running rebuildmaster - rerun setup with
rebuild flag.
e.g.
setup.exe REBUILDDATABASE=1
-oj
"HK" <replywithingroup@.notreal.com> wrote in message
news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
> I've been testing a new 2005 server. After the install, I backed up the
> system databases. I've done a lot of junk testing stuff since then, and
> now I'm wondering if I should do a restore of the system databases before
> I
> put the machine into production. If so, which ones?
>
|||Does that put it into the same state as just after an install?
If I had a test database still showing, for example, would that disappear?
"oj" <nospam_ojngo@.home.com> wrote in message
news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
> If you want a clean start, consider running rebuildmaster - rerun setup
with[vbcol=seagreen]
> rebuild flag.
> e.g.
> setup.exe REBUILDDATABASE=1
>
> --
> -oj
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
the[vbcol=seagreen]
and[vbcol=seagreen]
before
>
|||Correct. The system would look as if it's just installed.
Since the setup does not touch your user database, you can just reattach it
after the rebuild.
-oj
"HK" <replywithingroup@.notreal.com> wrote in message
news:0SnXf.18403$WK1.7806@.tornado.socal.rr.com...
> Does that put it into the same state as just after an install?
> If I had a test database still showing, for example, would that disappear?
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
> with
> the
> and
> before
>
|||That's a neat trick. Thanks.
"oj" <nospam_ojngo@.home.com> wrote in message
news:OgXKirUVGHA.5900@.tk2msftngp13.phx.gbl...
> Correct. The system would look as if it's just installed.
> Since the setup does not touch your user database, you can just reattach
it[vbcol=seagreen]
> after the rebuild.
> --
> -oj
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:0SnXf.18403$WK1.7806@.tornado.socal.rr.com...
disappear?
>
restoring system databases
I've been testing a new 2005 server. After the install, I backed up the
system databases. I've done a lot of junk testing stuff since then, and
now I'm wondering if I should do a restore of the system databases before I
put the machine into production. If so, which ones?If you want a clean start, consider running rebuildmaster - rerun setup with
rebuild flag.
e.g.
setup.exe REBUILDDATABASE=1
-oj
"HK" <replywithingroup@.notreal.com> wrote in message
news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
> I've been testing a new 2005 server. After the install, I backed up the
> system databases. I've done a lot of junk testing stuff since then, and
> now I'm wondering if I should do a restore of the system databases before
> I
> put the machine into production. If so, which ones?
>|||Does that put it into the same state as just after an install?
If I had a test database still showing, for example, would that disappear?
"oj" <nospam_ojngo@.home.com> wrote in message
news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
> If you want a clean start, consider running rebuildmaster - rerun setup
with
> rebuild flag.
> e.g.
> setup.exe REBUILDDATABASE=1
>
> --
> -oj
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
> > I've been testing a new 2005 server. After the install, I backed up
the
> > system databases. I've done a lot of junk testing stuff since then,
and
> > now I'm wondering if I should do a restore of the system databases
before
> > I
> > put the machine into production. If so, which ones?
> >
> >
>|||Correct. The system would look as if it's just installed.
Since the setup does not touch your user database, you can just reattach it
after the rebuild.
--
-oj
"HK" <replywithingroup@.notreal.com> wrote in message
news:0SnXf.18403$WK1.7806@.tornado.socal.rr.com...
> Does that put it into the same state as just after an install?
> If I had a test database still showing, for example, would that disappear?
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
>> If you want a clean start, consider running rebuildmaster - rerun setup
> with
>> rebuild flag.
>> e.g.
>> setup.exe REBUILDDATABASE=1
>>
>> --
>> -oj
>>
>> "HK" <replywithingroup@.notreal.com> wrote in message
>> news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
>> > I've been testing a new 2005 server. After the install, I backed up
> the
>> > system databases. I've done a lot of junk testing stuff since then,
> and
>> > now I'm wondering if I should do a restore of the system databases
> before
>> > I
>> > put the machine into production. If so, which ones?
>> >
>> >
>>
>|||That's a neat trick. Thanks.
"oj" <nospam_ojngo@.home.com> wrote in message
news:OgXKirUVGHA.5900@.tk2msftngp13.phx.gbl...
> Correct. The system would look as if it's just installed.
> Since the setup does not touch your user database, you can just reattach
it
> after the rebuild.
> --
> -oj
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:0SnXf.18403$WK1.7806@.tornado.socal.rr.com...
> > Does that put it into the same state as just after an install?
> >
> > If I had a test database still showing, for example, would that
disappear?
> >
> >
> > "oj" <nospam_ojngo@.home.com> wrote in message
> > news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
> >> If you want a clean start, consider running rebuildmaster - rerun setup
> > with
> >> rebuild flag.
> >>
> >> e.g.
> >> setup.exe REBUILDDATABASE=1
> >>
> >>
> >>
> >> --
> >> -oj
> >>
> >>
> >>
> >> "HK" <replywithingroup@.notreal.com> wrote in message
> >> news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
> >> > I've been testing a new 2005 server. After the install, I backed up
> > the
> >> > system databases. I've done a lot of junk testing stuff since then,
> > and
> >> > now I'm wondering if I should do a restore of the system databases
> > before
> >> > I
> >> > put the machine into production. If so, which ones?
> >> >
> >> >
> >>
> >>
> >
> >
>
system databases. I've done a lot of junk testing stuff since then, and
now I'm wondering if I should do a restore of the system databases before I
put the machine into production. If so, which ones?If you want a clean start, consider running rebuildmaster - rerun setup with
rebuild flag.
e.g.
setup.exe REBUILDDATABASE=1
-oj
"HK" <replywithingroup@.notreal.com> wrote in message
news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
> I've been testing a new 2005 server. After the install, I backed up the
> system databases. I've done a lot of junk testing stuff since then, and
> now I'm wondering if I should do a restore of the system databases before
> I
> put the machine into production. If so, which ones?
>|||Does that put it into the same state as just after an install?
If I had a test database still showing, for example, would that disappear?
"oj" <nospam_ojngo@.home.com> wrote in message
news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
> If you want a clean start, consider running rebuildmaster - rerun setup
with
> rebuild flag.
> e.g.
> setup.exe REBUILDDATABASE=1
>
> --
> -oj
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
> > I've been testing a new 2005 server. After the install, I backed up
the
> > system databases. I've done a lot of junk testing stuff since then,
and
> > now I'm wondering if I should do a restore of the system databases
before
> > I
> > put the machine into production. If so, which ones?
> >
> >
>|||Correct. The system would look as if it's just installed.
Since the setup does not touch your user database, you can just reattach it
after the rebuild.
--
-oj
"HK" <replywithingroup@.notreal.com> wrote in message
news:0SnXf.18403$WK1.7806@.tornado.socal.rr.com...
> Does that put it into the same state as just after an install?
> If I had a test database still showing, for example, would that disappear?
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
>> If you want a clean start, consider running rebuildmaster - rerun setup
> with
>> rebuild flag.
>> e.g.
>> setup.exe REBUILDDATABASE=1
>>
>> --
>> -oj
>>
>> "HK" <replywithingroup@.notreal.com> wrote in message
>> news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
>> > I've been testing a new 2005 server. After the install, I backed up
> the
>> > system databases. I've done a lot of junk testing stuff since then,
> and
>> > now I'm wondering if I should do a restore of the system databases
> before
>> > I
>> > put the machine into production. If so, which ones?
>> >
>> >
>>
>|||That's a neat trick. Thanks.
"oj" <nospam_ojngo@.home.com> wrote in message
news:OgXKirUVGHA.5900@.tk2msftngp13.phx.gbl...
> Correct. The system would look as if it's just installed.
> Since the setup does not touch your user database, you can just reattach
it
> after the rebuild.
> --
> -oj
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:0SnXf.18403$WK1.7806@.tornado.socal.rr.com...
> > Does that put it into the same state as just after an install?
> >
> > If I had a test database still showing, for example, would that
disappear?
> >
> >
> > "oj" <nospam_ojngo@.home.com> wrote in message
> > news:e2GjwiUVGHA.5364@.tk2msftngp13.phx.gbl...
> >> If you want a clean start, consider running rebuildmaster - rerun setup
> > with
> >> rebuild flag.
> >>
> >> e.g.
> >> setup.exe REBUILDDATABASE=1
> >>
> >>
> >>
> >> --
> >> -oj
> >>
> >>
> >>
> >> "HK" <replywithingroup@.notreal.com> wrote in message
> >> news:BceXf.17733$WK1.10563@.tornado.socal.rr.com...
> >> > I've been testing a new 2005 server. After the install, I backed up
> > the
> >> > system databases. I've done a lot of junk testing stuff since then,
> > and
> >> > now I'm wondering if I should do a restore of the system databases
> > before
> >> > I
> >> > put the machine into production. If so, which ones?
> >> >
> >> >
> >>
> >>
> >
> >
>
Friday, March 23, 2012
Restoring SQL Server 2005 backup to SQL server 2000
I have a sql 2005 backup that I am trying to restore in sql 2000. I get the following error..
Error:3169 The backed up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. Restore filelist is terminating abnormally.
Is there a workaround for this?
Vyanki
No, there is no workaround. SQL Server 2005 does not support downgrades or restores to SQL Server 2000.
|||thanks.
what way can be come true the case.
|||There is no "Restore" functionality, but there is a workaround to copy 2005 databases to 2000:Right-click on DB -> tasks -> generate scripts
select DB and click "script all objects...", hit next
select any options you want, specifically changing "script for server version" to SQL Server 2000
next through and run the script
Now just export data from the 2005 database to the newly-created 2000 database.
Right-click on DB -> tasks -> export...
set source and hit next
set destination and hit next
select "copy data from one or more tables", hit next
select all, check "optimize for many tables" and "run in a transaction"
you may have to edit each table mapping and check "enable identity insert"
next through to finish
|||
Jonathan Fife wrote:
There is no "Restore" functionality, but there is a workaround to copy 2005 databases to 2000: Right-click on DB -> tasks -> generate scripts
select DB and click "script all objects...", hit next
select any options you want, specifically changing "script for server version" to SQL Server 2000
next through and run the scriptNow just export data from the 2005 database to the newly-created 2000 database.
Right-click on DB -> tasks -> export...
set source and hit next
set destination and hit next
select "copy data from one or more tables", hit next
select all, check "optimize for many tables" and "run in a transaction"
you may have to edit each table mapping and check "enable identity insert"
next through to finish
... Then what do we do once we have the DB on the SQL 2000 server but still cant import or attach it? I've received a 2005 database from my web designer and need to import it into my 2000 server.
Thanks!
Chris
|||Unfortunately, you cannot restore a SQL Server 2005 backup to SQL Server 2000. In your situation, I would install a named instance of SQL Server 2005 (alongside your default 2000 instance). Then you could restore the 2005 backup there and use it directly, or you could use SSIS to copy the data to SQL Server 2000.sqlRestoring SQL Server 2005 backup to SQL server 2000
I have a sql 2005 backup that I am trying to restore in sql 2000. I get the following error..
Error:3169 The backed up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. Restore filelist is terminating abnormally.
Is there a workaround for this?
Vyanki
No, there is no workaround. SQL Server 2005 does not support downgrades or restores to SQL Server 2000.
|||thanks.
what way can be come true the case.
|||There is no "Restore" functionality, but there is a workaround to copy 2005 databases to 2000:Right-click on DB -> tasks -> generate scripts
select DB and click "script all objects...", hit next
select any options you want, specifically changing "script for server version" to SQL Server 2000
next through and run the script
Now just export data from the 2005 database to the newly-created 2000 database.
Right-click on DB -> tasks -> export...
set source and hit next
set destination and hit next
select "copy data from one or more tables", hit next
select all, check "optimize for many tables" and "run in a transaction"
you may have to edit each table mapping and check "enable identity insert"
next through to finish|||
Jonathan Fife wrote:
There is no "Restore" functionality, but there is a workaround to copy 2005 databases to 2000: Right-click on DB -> tasks -> generate scripts
select DB and click "script all objects...", hit next
select any options you want, specifically changing "script for server version" to SQL Server 2000
next through and run the scriptNow just export data from the 2005 database to the newly-created 2000 database.
Right-click on DB -> tasks -> export...
set source and hit next
set destination and hit next
select "copy data from one or more tables", hit next
select all, check "optimize for many tables" and "run in a transaction"
you may have to edit each table mapping and check "enable identity insert"
next through to finish
... Then what do we do once we have the DB on the SQL 2000 server but still cant import or attach it? I've received a 2005 database from my web designer and need to import it into my 2000 server.
Thanks!
Chris
|||Unfortunately, you cannot restore a SQL Server 2005 backup to SQL Server 2000. In your situation, I would install a named instance of SQL Server 2005 (alongside your default 2000 instance). Then you could restore the 2005 backup there and use it directly, or you could use SSIS to copy the data to SQL Server 2000.Restoring SQL Server 2005 backup to SQL server 2000
I have a sql 2005 backup that I am trying to restore in sql 2000. I get the following error..
Error:3169 The backed up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. Restore filelist is terminating abnormally.
Is there a workaround for this?
Vyanki
No, there is no workaround. SQL Server 2005 does not support downgrades or restores to SQL Server 2000.
|||thanks.
what way can be come true the case.
|||There is no "Restore" functionality, but there is a workaround to copy 2005 databases to 2000:Right-click on DB -> tasks -> generate scripts
select DB and click "script all objects...", hit next
select any options you want, specifically changing "script for server version" to SQL Server 2000
next through and run the script
Now just export data from the 2005 database to the newly-created 2000 database.
Right-click on DB -> tasks -> export...
set source and hit next
set destination and hit next
select "copy data from one or more tables", hit next
select all, check "optimize for many tables" and "run in a transaction"
you may have to edit each table mapping and check "enable identity insert"
next through to finish
|||
There is no "Restore" functionality, but there is a workaround to copy 2005 databases to 2000: Right-click on DB -> tasks -> generate scripts
select DB and click "script all objects...", hit next
select any options you want, specifically changing "script for server version" to SQL Server 2000
next through and run the scriptNow just export data from the 2005 database to the newly-created 2000 database.
Right-click on DB -> tasks -> export...
set source and hit next
set destination and hit next
select "copy data from one or more tables", hit next
select all, check "optimize for many tables" and "run in a transaction"
you may have to edit each table mapping and check "enable identity insert"
next through to finish
... Then what do we do once we have the DB on the SQL 2000 server but still cant import or attach it? I've received a 2005 database from my web designer and need to import it into my 2000 server.
Thanks!
Chris
|||Unfortunately, you cannot restore a SQL Server 2005 backup to SQL Server 2000. In your situation, I would install a named instance of SQL Server 2005 (alongside your default 2000 instance). Then you could restore the 2005 backup there and use it directly, or you could use SSIS to copy the data to SQL Server 2000.Restoring SQL Server 2005 backup to SQL server 2000
I have a sql 2005 backup that I am trying to restore in sql 2000. I get the following error..
Error:3169 The backed up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. Restore filelist is terminating abnormally.
Is there a workaround for this?
Vyanki
No, there is no workaround. SQL Server 2005 does not support downgrades or restores to SQL Server 2000.
|||thanks.
what way can be come true the case.
|||There is no "Restore" functionality, but there is a workaround to copy 2005 databases to 2000:Right-click on DB -> tasks -> generate scripts
select DB and click "script all objects...", hit next
select any options you want, specifically changing "script for server version" to SQL Server 2000
next through and run the script
Now just export data from the 2005 database to the newly-created 2000 database.
Right-click on DB -> tasks -> export...
set source and hit next
set destination and hit next
select "copy data from one or more tables", hit next
select all, check "optimize for many tables" and "run in a transaction"
you may have to edit each table mapping and check "enable identity insert"
next through to finish|||
There is no "Restore" functionality, but there is a workaround to copy 2005 databases to 2000: Right-click on DB -> tasks -> generate scripts
select DB and click "script all objects...", hit next
select any options you want, specifically changing "script for server version" to SQL Server 2000
next through and run the scriptNow just export data from the 2005 database to the newly-created 2000 database.
Right-click on DB -> tasks -> export...
set source and hit next
set destination and hit next
select "copy data from one or more tables", hit next
select all, check "optimize for many tables" and "run in a transaction"
you may have to edit each table mapping and check "enable identity insert"
next through to finish
... Then what do we do once we have the DB on the SQL 2000 server but still cant import or attach it? I've received a 2005 database from my web designer and need to import it into my 2000 server.
Thanks!
Chris
|||Unfortunately, you cannot restore a SQL Server 2005 backup to SQL Server 2000. In your situation, I would install a named instance of SQL Server 2005 (alongside your default 2000 instance). Then you could restore the 2005 backup there and use it directly, or you could use SSIS to copy the data to SQL Server 2000.Tuesday, March 20, 2012
Restoring multiple TRN files to another computer
I have a backup process that does full backups
periodically with transaction logs backed up every 5
minutes. In the event that I need to restore the backup
and apply a large number of TRN files on another computer
(for example if the server dies), is there an easy way?
If I do the restore on the original server, the interface
is easy because it knows about all the recent backups,
but when I do the restore to another server, the backups
are not listed in the interface so it seems I have to
choose "restore from device" and then select the backup
file and each TRN file individually which is very tedious.
Rick Harrison.In EM 2000, you can generate backup history from the contents of the backup
device. I've never used it (I prefer to do RESTORE though TSQL command), but
my guess that the feature was put there for this type of situations.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"rick@.knowware.com" <anonymous@.discussions.microsoft.com> wrote in message
news:0bd901c3bb52$2cbc0da0$a501280a@.phx.gbl...
> I have a backup process that does full backups
> periodically with transaction logs backed up every 5
> minutes. In the event that I need to restore the backup
> and apply a large number of TRN files on another computer
> (for example if the server dies), is there an easy way?
> If I do the restore on the original server, the interface
> is easy because it knows about all the recent backups,
> but when I do the restore to another server, the backups
> are not listed in the interface so it seems I have to
> choose "restore from device" and then select the backup
> file and each TRN file individually which is very tedious.
> Rick Harrison.|||We recently recovered from a total disk array failure to
another SQL server. We were fortunate enough to have all
the .BAK & .TRN files on tape. But without a little
program I wrote to automate the restore, it would have
taken an unreasonable amount of time to apply each TLog
using the GUI.
If you're interested, I can send you some VB code. It
uses the SQL DMO objects to restore DB's & files. I still
need to finalize some things, because I had to step
through the code & make minor adjustments to restore
everything. But I'm supposed to finalize the tool soon.
If you have VB knowledge, or someone at your company does,
you could take what I have now & make alterations to suit
your needs. Just let me know,
Gene Daigle
>--Original Message--
>I have a backup process that does full backups
>periodically with transaction logs backed up every 5
>minutes. In the event that I need to restore the backup
>and apply a large number of TRN files on another computer
>(for example if the server dies), is there an easy way?
>If I do the restore on the original server, the interface
>is easy because it knows about all the recent backups,
>but when I do the restore to another server, the backups
>are not listed in the interface so it seems I have to
>choose "restore from device" and then select the backup
>file and each TRN file individually which is very tedious.
> Rick Harrison.
>.
>
periodically with transaction logs backed up every 5
minutes. In the event that I need to restore the backup
and apply a large number of TRN files on another computer
(for example if the server dies), is there an easy way?
If I do the restore on the original server, the interface
is easy because it knows about all the recent backups,
but when I do the restore to another server, the backups
are not listed in the interface so it seems I have to
choose "restore from device" and then select the backup
file and each TRN file individually which is very tedious.
Rick Harrison.In EM 2000, you can generate backup history from the contents of the backup
device. I've never used it (I prefer to do RESTORE though TSQL command), but
my guess that the feature was put there for this type of situations.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"rick@.knowware.com" <anonymous@.discussions.microsoft.com> wrote in message
news:0bd901c3bb52$2cbc0da0$a501280a@.phx.gbl...
> I have a backup process that does full backups
> periodically with transaction logs backed up every 5
> minutes. In the event that I need to restore the backup
> and apply a large number of TRN files on another computer
> (for example if the server dies), is there an easy way?
> If I do the restore on the original server, the interface
> is easy because it knows about all the recent backups,
> but when I do the restore to another server, the backups
> are not listed in the interface so it seems I have to
> choose "restore from device" and then select the backup
> file and each TRN file individually which is very tedious.
> Rick Harrison.|||We recently recovered from a total disk array failure to
another SQL server. We were fortunate enough to have all
the .BAK & .TRN files on tape. But without a little
program I wrote to automate the restore, it would have
taken an unreasonable amount of time to apply each TLog
using the GUI.
If you're interested, I can send you some VB code. It
uses the SQL DMO objects to restore DB's & files. I still
need to finalize some things, because I had to step
through the code & make minor adjustments to restore
everything. But I'm supposed to finalize the tool soon.
If you have VB knowledge, or someone at your company does,
you could take what I have now & make alterations to suit
your needs. Just let me know,
Gene Daigle
>--Original Message--
>I have a backup process that does full backups
>periodically with transaction logs backed up every 5
>minutes. In the event that I need to restore the backup
>and apply a large number of TRN files on another computer
>(for example if the server dies), is there an easy way?
>If I do the restore on the original server, the interface
>is easy because it knows about all the recent backups,
>but when I do the restore to another server, the backups
>are not listed in the interface so it seems I have to
>choose "restore from device" and then select the backup
>file and each TRN file individually which is very tedious.
> Rick Harrison.
>.
>
Friday, March 9, 2012
Restoring in SQL 2005
Hi ,
I am trying to restore database , which is backed up from SQL 2005 ver 9.00.1399.06
to anothere machine have SQL 2005 ver 9.00.1399.00.
When I try to do a restore I am getting the following error!
Too many backup devices specified for backup or restore ; only 64 are allowed.
RESTORE HEADER ONLY is terminating abnormally . (Microsoft SQL Server, Error:3205)
Please give me some solution for this.
Did you got a solution. I am having the same problem when I move the backup from 1 server to another and try to restore|||Yes. I guess I was restoring on the wrong server. It was not 2005. Make sure you are on the right server. We cannot restore 2005 database in 2000. My was a user error
|||that fixed it for me too....I got fooled by a 2005 upgrade issue and was actually trying to restore a 2005 db to a 2000 db server.|||that fixed it for me too.... I was trying to restore backup from 2005 to a another machine with SQL server 2005, but we found that Management Studio was showing only sql server 2000. I Confirmed it by looking at the version Number. For 2005 it was 9.0.1399 and for 2000 it was 8.0.194|||Hi, I' m having the same problem, Im trying to restore a 2005 bkp into a another 2005, but i recive the same error have you resolve this?
thank very much and sorry about my english
|||I'm getting this same error going from 2005 to 2005. Definatly both 2005 versions - i installed them both myself.
Anyone have any ideas?
|||This is not an SSIS issue. Moving to the SQL Server Database Engine forum.|||the solution has already been discussed in the earlier post. You may be using SQLServer 2005Management studio but... the backup you have is from 2005 and u r trying to restore it in 2000 instance which is not possible.
Madhu
|||
the solution has already been discussed in the earlier post. You may be using SQLServer 2005Management studio but... the backup you have is from 2005 and u r trying to restore it in 2000 instance which is not possible.
Madhu
I wish it was that simple.
I installed 2005 on a server at work and created the database in question. Then took a backup.
Then I installed 2005 on my laptop (using the same install program) and get this error when trying to restore the backup into a database on the laptop.
|||Actually, my bad. Didn't notice that the install program did not upgrade the existing sql default instance.|||http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.0760&EvtSrc=MSSQLServer&EvtID=3205&LinkId=20476|||ProdName=Microsoft+SQL+Server&ProdVer=08.00.0760&EvtSrc=MSSQLServer&EvtID=3205&LinkId=20476Restoring in SQL 2005
Hi ,
I am trying to restore database , which is backed up from SQL 2005 ver 9.00.1399.06
to anothere machine have SQL 2005 ver 9.00.1399.00.
When I try to do a restore I am getting the following error!
Too many backup devices specified for backup or restore ; only 64 are allowed.
RESTORE HEADER ONLY is terminating abnormally . (Microsoft SQL Server, Error:3205)
Please give me some solution for this.
Did you got a solution. I am having the same problem when I move the backup from 1 server to another and try to restore|||Yes. I guess I was restoring on the wrong server. It was not 2005. Make sure you are on the right server. We cannot restore 2005 database in 2000. My was a user error
|||that fixed it for me too....I got fooled by a 2005 upgrade issue and was actually trying to restore a 2005 db to a 2000 db server.|||that fixed it for me too.... I was trying to restore backup from 2005 to a another machine with SQL server 2005, but we found that Management Studio was showing only sql server 2000. I Confirmed it by looking at the version Number. For 2005 it was 9.0.1399 and for 2000 it was 8.0.194|||Hi, I' m having the same problem, Im trying to restore a 2005 bkp into a another 2005, but i recive the same error have you resolve this?
thank very much and sorry about my english
|||I'm getting this same error going from 2005 to 2005. Definatly both 2005 versions - i installed them both myself.
Anyone have any ideas?
|||This is not an SSIS issue. Moving to the SQL Server Database Engine forum.|||the solution has already been discussed in the earlier post. You may be using SQLServer 2005Management studio but... the backup you have is from 2005 and u r trying to restore it in 2000 instance which is not possible.
Madhu
|||
the solution has already been discussed in the earlier post. You may be using SQLServer 2005Management studio but... the backup you have is from 2005 and u r trying to restore it in 2000 instance which is not possible.
Madhu
I wish it was that simple.
I installed 2005 on a server at work and created the database in question. Then took a backup.
Then I installed 2005 on my laptop (using the same install program) and get this error when trying to restore the backup into a database on the laptop.
|||Actually, my bad. Didn't notice that the install program did not upgrade the existing sql default instance.|||http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.0760&EvtSrc=MSSQLServer&EvtID=3205&LinkId=20476|||
ProdName=Microsoft+SQL+Server&ProdVer=08.00.0760&EvtSrc=MSSQLServer&EvtID=3205&LinkId=20476
Restoring in SQL 2005
Hi ,
I am trying to restore database , which is backed up from SQL 2005 ver 9.00.1399.06
to anothere machine have SQL 2005 ver 9.00.1399.00.
When I try to do a restore I am getting the following error!
Too many backup devices specified for backup or restore ; only 64 are allowed.
RESTORE HEADER ONLY is terminating abnormally . (Microsoft SQL Server, Error:3205)
Please give me some solution for this.
Did you got a solution. I am having the same problem when I move the backup from 1 server to another and try to restore|||Yes. I guess I was restoring on the wrong server. It was not 2005. Make sure you are on the right server. We cannot restore 2005 database in 2000. My was a user error
|||that fixed it for me too....I got fooled by a 2005 upgrade issue and was actually trying to restore a 2005 db to a 2000 db server.|||that fixed it for me too.... I was trying to restore backup from 2005 to a another machine with SQL server 2005, but we found that Management Studio was showing only sql server 2000. I Confirmed it by looking at the version Number. For 2005 it was 9.0.1399 and for 2000 it was 8.0.194|||Hi, I' m having the same problem, Im trying to restore a 2005 bkp into a another 2005, but i recive the same error have you resolve this?
thank very much and sorry about my english
|||I'm getting this same error going from 2005 to 2005. Definatly both 2005 versions - i installed them both myself.
Anyone have any ideas?
|||This is not an SSIS issue. Moving to the SQL Server Database Engine forum.|||the solution has already been discussed in the earlier post. You may be using SQLServer 2005Management studio but... the backup you have is from 2005 and u r trying to restore it in 2000 instance which is not possible.
Madhu
|||
the solution has already been discussed in the earlier post. You may be using SQLServer 2005Management studio but... the backup you have is from 2005 and u r trying to restore it in 2000 instance which is not possible.
Madhu
I wish it was that simple.
I installed 2005 on a server at work and created the database in question. Then took a backup.
Then I installed 2005 on my laptop (using the same install program) and get this error when trying to restore the backup into a database on the laptop.
|||Actually, my bad. Didn't notice that the install program did not upgrade the existing sql default instance.|||http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.0760&EvtSrc=MSSQLServer&EvtID=3205&LinkId=20476|||ProdName=Microsoft+SQL+Server&ProdVer=08.00.0760&EvtSrc=MSSQLServer&EvtID=3205&LinkId=20476Restoring in SQL 2005
Hi ,
I am trying to restore database , which is backed up from SQL 2005 ver 9.00.1399.06
to anothere machine have SQL 2005 ver 9.00.1399.00.
When I try to do a restore I am getting the following error!
Too many backup devices specified for backup or restore ; only 64 are allowed.
RESTORE HEADER ONLY is terminating abnormally . (Microsoft SQL Server, Error:3205)
Please give me some solution for this.
Did you got a solution. I am having the same problem when I move the backup from 1 server to another and try to restore|||Yes. I guess I was restoring on the wrong server. It was not 2005. Make sure you are on the right server. We cannot restore 2005 database in 2000. My was a user error
|||that fixed it for me too....I got fooled by a 2005 upgrade issue and was actually trying to restore a 2005 db to a 2000 db server.|||that fixed it for me too.... I was trying to restore backup from 2005 to a another machine with SQL server 2005, but we found that Management Studio was showing only sql server 2000. I Confirmed it by looking at the version Number. For 2005 it was 9.0.1399 and for 2000 it was 8.0.194|||Hi, I' m having the same problem, Im trying to restore a 2005 bkp into a another 2005, but i recive the same error have you resolve this?
thank very much and sorry about my english
|||I'm getting this same error going from 2005 to 2005. Definatly both 2005 versions - i installed them both myself.
Anyone have any ideas?
|||This is not an SSIS issue. Moving to the SQL Server Database Engine forum.|||the solution has already been discussed in the earlier post. You may be using SQLServer 2005Management studio but... the backup you have is from 2005 and u r trying to restore it in 2000 instance which is not possible.
Madhu
|||
the solution has already been discussed in the earlier post. You may be using SQLServer 2005Management studio but... the backup you have is from 2005 and u r trying to restore it in 2000 instance which is not possible.
Madhu
I wish it was that simple.
I installed 2005 on a server at work and created the database in question. Then took a backup.
Then I installed 2005 on my laptop (using the same install program) and get this error when trying to restore the backup into a database on the laptop.
|||Actually, my bad. Didn't notice that the install program did not upgrade the existing sql default instance.|||http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.0760&EvtSrc=MSSQLServer&EvtID=3205&LinkId=20476|||
ProdName=Microsoft+SQL+Server&ProdVer=08.00.0760&EvtSrc=MSSQLServer&EvtID=3205&LinkId=20476
Restoring in SQL 2005
Hi ,
I am trying to restore database , which is backed up from SQL 2005 ver 9.00.1399.06
to anothere machine have SQL 2005 ver 9.00.1399.00.
When I try to do a restore I am getting the following error!
Too many backup devices specified for backup or restore ; only 64 are allowed.
RESTORE HEADER ONLY is terminating abnormally . (Microsoft SQL Server, Error:3205)
Please give me some solution for this.
Did you got a solution. I am having the same problem when I move the backup from 1 server to another and try to restore|||Yes. I guess I was restoring on the wrong server. It was not 2005. Make sure you are on the right server. We cannot restore 2005 database in 2000. My was a user error
|||that fixed it for me too....I got fooled by a 2005 upgrade issue and was actually trying to restore a 2005 db to a 2000 db server.|||that fixed it for me too.... I was trying to restore backup from 2005 to a another machine with SQL server 2005, but we found that Management Studio was showing only sql server 2000. I Confirmed it by looking at the version Number. For 2005 it was 9.0.1399 and for 2000 it was 8.0.194|||Hi, I' m having the same problem, Im trying to restore a 2005 bkp into a another 2005, but i recive the same error have you resolve this?
thank very much and sorry about my english
|||I'm getting this same error going from 2005 to 2005. Definatly both 2005 versions - i installed them both myself.
Anyone have any ideas?
|||This is not an SSIS issue. Moving to the SQL Server Database Engine forum.|||the solution has already been discussed in the earlier post. You may be using SQLServer 2005Management studio but... the backup you have is from 2005 and u r trying to restore it in 2000 instance which is not possible.
Madhu
|||
the solution has already been discussed in the earlier post. You may be using SQLServer 2005Management studio but... the backup you have is from 2005 and u r trying to restore it in 2000 instance which is not possible.
Madhu
I wish it was that simple.
I installed 2005 on a server at work and created the database in question. Then took a backup.
Then I installed 2005 on my laptop (using the same install program) and get this error when trying to restore the backup into a database on the laptop.
|||Actually, my bad. Didn't notice that the install program did not upgrade the existing sql default instance.|||http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.0760&EvtSrc=MSSQLServer&EvtID=3205&LinkId=20476|||
ProdName=Microsoft+SQL+Server&ProdVer=08.00.0760&EvtSrc=MSSQLServer&EvtID=3205&LinkId=20476
Wednesday, March 7, 2012
Restoring from a CD
There are two SQL 2000 servers, Server A and Server B. I backed up all the databases on Server A and then burned the backups to a CD. Now I am trying to restore one of the databases from Server A on Server B but I am having problems and getting error messages.
How do I restore a database backup file (*.bak) from a CD if the database backup is from another SQL Server?What problem are you having, specifically?
Don't forget to go into the options tab and change the file paths for the
physical file names -- in my experience that's the most common thing people
forget about when restoring databases from other servers.
"Evan" <anonymous@.discussions.microsoft.com> wrote in message
news:01075679-9221-4095-ABAF-0DB0C4CED06C@.microsoft.com...
> There are two SQL 2000 servers, Server A and Server B. I backed up all the
databases on Server A and then burned the backups to a CD. Now I am trying
to restore one of the databases from Server A on Server B but I am having
problems and getting error messages.
> How do I restore a database backup file (*.bak) from a CD if the database
backup is from another SQL Server?
>|||I'm not sure how to restore the backup so I tried a couple different methods but none of them worked. I'd like directions on how to restore the databases.
Evan
-- Adam Machanic wrote: --
What problem are you having, specifically?
Don't forget to go into the options tab and change the file paths for the
physical file names -- in my experience that's the most common thing people
forget about when restoring databases from other servers.
"Evan" <anonymous@.discussions.microsoft.com> wrote in message
news:01075679-9221-4095-ABAF-0DB0C4CED06C@.microsoft.com...
> There are two SQL 2000 servers, Server A and Server B. I backed up all the
databases on Server A and then burned the backups to a CD. Now I am trying
to restore one of the databases from Server A on Server B but I am having
problems and getting error messages.
>> How do I restore a database backup file (*.bak) from a CD if the database
backup is from another SQL Server?
>|||In Enterprise Manager:
Create a new database with whatever name you want.
Right-click on it. Click "All Tasks" -> "Restore Database".
Select "From device".
Click "Select Device", then "Add..." and browse the file you want to
restore.
Click "OK" twice. Then click the "Options" tab. Select "Force restore over
existing database". Make sure the paths in "Move to physical file name"
exist on your server. Edit the paths if necessary.
Click "OK". At this point it should restore...
"Evan" <anonymous@.discussions.microsoft.com> wrote in message
news:29FAAB9A-E962-40D2-8733-F476D8650F7B@.microsoft.com...
> I'm not sure how to restore the backup so I tried a couple different
methods but none of them worked. I'd like directions on how to restore the
databases.
> Evan
>
> -- Adam Machanic wrote: --
> What problem are you having, specifically?
> Don't forget to go into the options tab and change the file paths for
the
> physical file names -- in my experience that's the most common thing
people
> forget about when restoring databases from other servers.
>
> "Evan" <anonymous@.discussions.microsoft.com> wrote in message
> news:01075679-9221-4095-ABAF-0DB0C4CED06C@.microsoft.com...
> > There are two SQL 2000 servers, Server A and Server B. I backed up
all the
> databases on Server A and then burned the backups to a CD. Now I am
trying
> to restore one of the databases from Server A on Server B but I am
having
> problems and getting error messages.
> >> How do I restore a database backup file (*.bak) from a CD if the
database
> backup is from another SQL Server?
> >|||It worked! Thanks a million.
I tried that procedure before but it didn't work - the file paths are a gotcha.
Evan
-- Adam Machanic wrote: --
In Enterprise Manager:
Create a new database with whatever name you want.
Right-click on it. Click "All Tasks" -> "Restore Database".
Select "From device".
Click "Select Device", then "Add..." and browse the file you want to
restore.
Click "OK" twice. Then click the "Options" tab. Select "Force restore over
existing database". Make sure the paths in "Move to physical file name"
exist on your server. Edit the paths if necessary.
Click "OK". At this point it should restore...
"Evan" <anonymous@.discussions.microsoft.com> wrote in message
news:29FAAB9A-E962-40D2-8733-F476D8650F7B@.microsoft.com...
> I'm not sure how to restore the backup so I tried a couple different
methods but none of them worked. I'd like directions on how to restore the
databases.
>> Evan
>> -- Adam Machanic wrote: --
>> What problem are you having, specifically?
>> Don't forget to go into the options tab and change the file paths for
the
> physical file names -- in my experience that's the most common thing
people
> forget about when restoring databases from other servers.
>> "Evan" <anonymous@.discussions.microsoft.com> wrote in message
> news:01075679-9221-4095-ABAF-0DB0C4CED06C@.microsoft.com...
>> There are two SQL 2000 servers, Server A and Server B. I backed up
all the
> databases on Server A and then burned the backups to a CD. Now I am
trying
> to restore one of the databases from Server A on Server B but I am
having
> problems and getting error messages.
>> How do I restore a database backup file (*.bak) from a CD if the
database
> backup is from another SQL Server?
>>
How do I restore a database backup file (*.bak) from a CD if the database backup is from another SQL Server?What problem are you having, specifically?
Don't forget to go into the options tab and change the file paths for the
physical file names -- in my experience that's the most common thing people
forget about when restoring databases from other servers.
"Evan" <anonymous@.discussions.microsoft.com> wrote in message
news:01075679-9221-4095-ABAF-0DB0C4CED06C@.microsoft.com...
> There are two SQL 2000 servers, Server A and Server B. I backed up all the
databases on Server A and then burned the backups to a CD. Now I am trying
to restore one of the databases from Server A on Server B but I am having
problems and getting error messages.
> How do I restore a database backup file (*.bak) from a CD if the database
backup is from another SQL Server?
>|||I'm not sure how to restore the backup so I tried a couple different methods but none of them worked. I'd like directions on how to restore the databases.
Evan
-- Adam Machanic wrote: --
What problem are you having, specifically?
Don't forget to go into the options tab and change the file paths for the
physical file names -- in my experience that's the most common thing people
forget about when restoring databases from other servers.
"Evan" <anonymous@.discussions.microsoft.com> wrote in message
news:01075679-9221-4095-ABAF-0DB0C4CED06C@.microsoft.com...
> There are two SQL 2000 servers, Server A and Server B. I backed up all the
databases on Server A and then burned the backups to a CD. Now I am trying
to restore one of the databases from Server A on Server B but I am having
problems and getting error messages.
>> How do I restore a database backup file (*.bak) from a CD if the database
backup is from another SQL Server?
>|||In Enterprise Manager:
Create a new database with whatever name you want.
Right-click on it. Click "All Tasks" -> "Restore Database".
Select "From device".
Click "Select Device", then "Add..." and browse the file you want to
restore.
Click "OK" twice. Then click the "Options" tab. Select "Force restore over
existing database". Make sure the paths in "Move to physical file name"
exist on your server. Edit the paths if necessary.
Click "OK". At this point it should restore...
"Evan" <anonymous@.discussions.microsoft.com> wrote in message
news:29FAAB9A-E962-40D2-8733-F476D8650F7B@.microsoft.com...
> I'm not sure how to restore the backup so I tried a couple different
methods but none of them worked. I'd like directions on how to restore the
databases.
> Evan
>
> -- Adam Machanic wrote: --
> What problem are you having, specifically?
> Don't forget to go into the options tab and change the file paths for
the
> physical file names -- in my experience that's the most common thing
people
> forget about when restoring databases from other servers.
>
> "Evan" <anonymous@.discussions.microsoft.com> wrote in message
> news:01075679-9221-4095-ABAF-0DB0C4CED06C@.microsoft.com...
> > There are two SQL 2000 servers, Server A and Server B. I backed up
all the
> databases on Server A and then burned the backups to a CD. Now I am
trying
> to restore one of the databases from Server A on Server B but I am
having
> problems and getting error messages.
> >> How do I restore a database backup file (*.bak) from a CD if the
database
> backup is from another SQL Server?
> >|||It worked! Thanks a million.
I tried that procedure before but it didn't work - the file paths are a gotcha.
Evan
-- Adam Machanic wrote: --
In Enterprise Manager:
Create a new database with whatever name you want.
Right-click on it. Click "All Tasks" -> "Restore Database".
Select "From device".
Click "Select Device", then "Add..." and browse the file you want to
restore.
Click "OK" twice. Then click the "Options" tab. Select "Force restore over
existing database". Make sure the paths in "Move to physical file name"
exist on your server. Edit the paths if necessary.
Click "OK". At this point it should restore...
"Evan" <anonymous@.discussions.microsoft.com> wrote in message
news:29FAAB9A-E962-40D2-8733-F476D8650F7B@.microsoft.com...
> I'm not sure how to restore the backup so I tried a couple different
methods but none of them worked. I'd like directions on how to restore the
databases.
>> Evan
>> -- Adam Machanic wrote: --
>> What problem are you having, specifically?
>> Don't forget to go into the options tab and change the file paths for
the
> physical file names -- in my experience that's the most common thing
people
> forget about when restoring databases from other servers.
>> "Evan" <anonymous@.discussions.microsoft.com> wrote in message
> news:01075679-9221-4095-ABAF-0DB0C4CED06C@.microsoft.com...
>> There are two SQL 2000 servers, Server A and Server B. I backed up
all the
> databases on Server A and then burned the backups to a CD. Now I am
trying
> to restore one of the databases from Server A on Server B but I am
having
> problems and getting error messages.
>> How do I restore a database backup file (*.bak) from a CD if the
database
> backup is from another SQL Server?
>>
Subscribe to:
Posts (Atom)