Discussion:
Load database
(too old to reply)
unknown
2006-09-08 14:39:09 UTC
Permalink
is there any special command or procedure that can be used
to load into a smaller database than the database in which
the dump was taken.
2006-09-08 17:16:43 UTC
Permalink
no way. The target DB sud be same or bigger the size of the source.

or you can do bcp out and in

thanks
Post by unknown
is there any special command or procedure that can be used
to load into a smaller database than the database in which
the dump was taken.
A.M.
2006-09-08 20:34:05 UTC
Permalink
Post by unknown
is there any special command or procedure that can be used
to load into a smaller database than the database in which
the dump was taken.
Unfortunately, no. The load will complain since it
need to match the original database's size. You can
only load into the same size or larger. You also
need to watch the version of the target since databases
can't be downgraded.

If you don't need to do this on a regular basis, you
can create a new db and use select into to copy tables
or use bcp. This approach isn't ideal for regular copies.

Alternately, consider replication.

-am © MMVI
Mark A. Parsons
2006-09-08 23:06:02 UTC
Permalink
And with 12.5.4 there is the new archive database feature where, in
essence, the dump files (must be on disk) are mounted to an 'archive'
database but not actually loaded ... thus allowing you to 'load' a database
into a smaller database, eg, you could 'load' a 100GB database into a 100MB
database.

The dump files are then, for the most part, accessible as a *read only*
database.

There are a few caveats in regards to needing some space for dbcc fix's and
recovery page manipulation, issues with compressed dumps, and of course
you're not going to get great performance from said database.

The objective would be to load (ie, mount) the databae dump files and then
pull the desired data out of said dump files into permanent tables
elsewhere on the dataserver.
Post by A.M.
Post by unknown
is there any special command or procedure that can be used
to load into a smaller database than the database in which
the dump was taken.
Unfortunately, no. The load will complain since it
need to match the original database's size. You can
only load into the same size or larger. You also
need to watch the version of the target since databases
can't be downgraded.
If you don't need to do this on a regular basis, you
can create a new db and use select into to copy tables
or use bcp. This approach isn't ideal for regular copies.
Alternately, consider replication.
-am © MMVI
2006-09-09 16:46:47 UTC
Permalink
Its an excellent feature. We use for various tasks on this archivedb...
earlier we use to run on productions db's

regards
Post by Mark A. Parsons
And with 12.5.4 there is the new archive database feature where, in
essence, the dump files (must be on disk) are mounted to an 'archive'
database but not actually loaded ... thus allowing you to 'load' a
database into a smaller database, eg, you could 'load' a 100GB database
into a 100MB database.
The dump files are then, for the most part, accessible as a *read only*
database.
There are a few caveats in regards to needing some space for dbcc fix's
and recovery page manipulation, issues with compressed dumps, and of
course you're not going to get great performance from said database.
The objective would be to load (ie, mount) the databae dump files and then
pull the desired data out of said dump files into permanent tables
elsewhere on the dataserver.
Post by A.M.
Post by unknown
is there any special command or procedure that can be used
to load into a smaller database than the database in which
the dump was taken.
Unfortunately, no. The load will complain since it
need to match the original database's size. You can
only load into the same size or larger. You also
need to watch the version of the target since databases
can't be downgraded.
If you don't need to do this on a regular basis, you
can create a new db and use select into to copy tables
or use bcp. This approach isn't ideal for regular copies.
Alternately, consider replication.
-am © MMVI
unknown
2006-09-11 06:03:44 UTC
Permalink
Thanks all for your response,

Mark, i would like to learn more on this new feature of
12.5.4, is it also available in 15.0, and any reference??

EDWARD
Post by Mark A. Parsons
And with 12.5.4 there is the new archive database feature
where, in essence, the dump files (must be on disk) are
mounted to an 'archive' database but not actually loaded
.. thus allowing you to 'load' a database into a smaller
database, eg, you could 'load' a 100GB database into a
100MB database.
The dump files are then, for the most part, accessible as
a *read only* database.
There are a few caveats in regards to needing some space
for dbcc fix's and recovery page manipulation, issues
with compressed dumps, and of course you're not going to
get great performance from said database.
The objective would be to load (ie, mount) the databae
dump files and then pull the desired data out of said
dump files into permanent tables elsewhere on the
dataserver.
Post by A.M.
Post by unknown
is there any special command or procedure that can be
used >>to load into a smaller database than the database
in which >>the dump was taken.
Post by A.M.
Unfortunately, no. The load will complain since it
need to match the original database's size. You can
only load into the same size or larger. You also
need to watch the version of the target since
databases can't be downgraded.
If you don't need to do this on a regular basis, you
can create a new db and use select into to copy
tables or use bcp. This approach isn't ideal for
regular copies.
Alternately, consider replication.
-am © MMVI
Paul Dow
2006-09-11 09:19:09 UTC
Permalink
It should be in 15.0.2.

- Paul
Post by unknown
Thanks all for your response,
Mark, i would like to learn more on this new feature of
12.5.4, is it also available in 15.0, and any reference??
EDWARD
Post by Mark A. Parsons
And with 12.5.4 there is the new archive database feature
where, in essence, the dump files (must be on disk) are
mounted to an 'archive' database but not actually loaded
.. thus allowing you to 'load' a database into a smaller
database, eg, you could 'load' a 100GB database into a
100MB database.
The dump files are then, for the most part, accessible as
a *read only* database.
There are a few caveats in regards to needing some space
for dbcc fix's and recovery page manipulation, issues
with compressed dumps, and of course you're not going to
get great performance from said database.
The objective would be to load (ie, mount) the databae
dump files and then pull the desired data out of said
dump files into permanent tables elsewhere on the
dataserver.
Post by A.M.
Post by unknown
is there any special command or procedure that can be
used >>to load into a smaller database than the database
in which >>the dump was taken.
Post by A.M.
Unfortunately, no. The load will complain since it
need to match the original database's size. You can
only load into the same size or larger. You also
need to watch the version of the target since
databases can't be downgraded.
If you don't need to do this on a regular basis, you
can create a new db and use select into to copy
tables or use bcp. This approach isn't ideal for
regular copies.
Alternately, consider replication.
-am © MMVI
Mark A. Parsons
2006-09-11 22:48:02 UTC
Permalink
re: 12.5.4 - see the New Features guide for details on using the 'archive
database' feature
Post by unknown
Thanks all for your response,
Mark, i would like to learn more on this new feature of
12.5.4, is it also available in 15.0, and any reference??
EDWARD
Post by Mark A. Parsons
And with 12.5.4 there is the new archive database feature
where, in essence, the dump files (must be on disk) are
mounted to an 'archive' database but not actually loaded
.. thus allowing you to 'load' a database into a smaller
database, eg, you could 'load' a 100GB database into a
100MB database.
The dump files are then, for the most part, accessible as
a *read only* database.
There are a few caveats in regards to needing some space
for dbcc fix's and recovery page manipulation, issues
with compressed dumps, and of course you're not going to
get great performance from said database.
The objective would be to load (ie, mount) the databae
dump files and then pull the desired data out of said
dump files into permanent tables elsewhere on the
dataserver.
Post by A.M.
Post by unknown
is there any special command or procedure that can be
used >>to load into a smaller database than the database
in which >>the dump was taken.
Post by A.M.
Unfortunately, no. The load will complain since it
need to match the original database's size. You can
only load into the same size or larger. You also
need to watch the version of the target since
databases can't be downgraded.
If you don't need to do this on a regular basis, you
can create a new db and use select into to copy
tables or use bcp. This approach isn't ideal for
regular copies.
Alternately, consider replication.
-am © MMVI
r***@gmail.com
2006-10-14 07:17:44 UTC
Permalink
Post by Mark A. Parsons
And with 12.5.4 there is the new archive database feature
where, in essence, the dump files (must be on disk) are
mounted to an 'archive' database but not actually loaded
.. thus allowing you to 'load' a database into a smaller
database, eg, you could 'load' a 100GB database into a
100MB database.
GOOOOOOOOOD IDEA
Post by Mark A. Parsons
The dump files are then, for the most part, accessible as
a *read only* database.
There are a few caveats in regards to needing some space
for dbcc fix's and recovery page manipulation, issues
with compressed dumps, and of course you're not going to
get great performance from said database.
The objective would be to load (ie, mount) the databae
dump files and then pull the desired data out of said
dump files into permanent tables elsewhere on the
dataserver.
Post by A.M.
Post by unknown
is there any special command or procedure that can be
used >>to load into a smaller database than the database
in which >>the dump was taken.
Post by A.M.
Unfortunately, no. The load will complain since it
need to match the original database's size. You can
only load into the same size or larger. You also
need to watch the version of the target since
databases can't be downgraded.
If you don't need to do this on a regular basis, you
can create a new db and use select into to copy
tables or use bcp. This approach isn't ideal for
regular copies.
Alternately, consider replication.
-am © MMVI
Loading...