Hi
Is there a way to backup many tables in a SQL Server database to a text
file all at once? I know this can be done individually using the
import/export wizard, but I have many tables that need to be backed up
often and still have the ability to restore them all at once as well.
Basically we use 1 database for many tests and after each test we want
to backup the data in certain tables, not backup the entire database.
Thanks
LauraYou could move all of the tables that you wish to back up, including their
indexes, into a secondary file, in a secondary filegroup. You could then
backup only that filegroup.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
<Laura.X.Kennedy@.JPMorgan.com> wrote in message
news:1166478797.830720.145090@.79g2000cws.googlegroups.com...
> Hi
> Is there a way to backup many tables in a SQL Server database to a text
> file all at once? I know this can be done individually using the
> import/export wizard, but I have many tables that need to be backed up
> often and still have the ability to restore them all at once as well.
> Basically we use 1 database for many tests and after each test we want
> to backup the data in certain tables, not backup the entire database.
> Thanks
> Laura
>|||DTS?
<Laura.X.Kennedy@.JPMorgan.com> wrote in message
news:1166478797.830720.145090@.79g2000cws.googlegroups.com...
> Hi
> Is there a way to backup many tables in a SQL Server database to a text
> file all at once? I know this can be done individually using the
> import/export wizard, but I have many tables that need to be backed up
> often and still have the ability to restore them all at once as well.
> Basically we use 1 database for many tests and after each test we want
> to backup the data in certain tables, not backup the entire database.
> Thanks
> Laura
>|||Just be aware that restore is a bit tricky to restore in this scenario. You
can't just restore into
the production database without rolling forward all transaction logs up to c
urrent date and time.
You can restore into a new database assuming that you backuped up the primar
y filegroup as well (in
fact, possibly the backup need to be of the whole database - you need to tes
t), using the partial
option. You can then export the needed data into the production database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Arnie Rowland" <arnie@.1568.com> wrote in message news:OvFNuAvIHHA.1248@.TK2MSFTNGP03.phx.gbl
..
> You could move all of the tables that you wish to back up, including their
indexes, into a
> secondary file, in a secondary filegroup. You could then backup only that
filegroup.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to th
e top yourself.
> - H. Norman Schwarzkopf
>
> <Laura.X.Kennedy@.JPMorgan.com> wrote in message
> news:1166478797.830720.145090@.79g2000cws.googlegroups.com...
>
No comments:
Post a Comment