Question about restoring a database

All,
I have many DTS packages pulling data from production
servers to reporting servers. This is going to be changed
so that the production servers push the data to the
reporting servers.
The production server DBA wants to periodically make a
full backup of the databases, "zip" them, and FTP them to
the reporting servers. On the reporting servers, the "zip"
files will be un-zipped and the databases will be
restored. The databases are scattered over half the US.
Most of the tables, triggers, stored procedures, views,
users, etc. in the copied databases are not needed for our
reporting. I would like to be able to drop these objects
from the reporting server databases immediately after they
are restored. Doing so will free up significant amounts of
hard drive space.
My biggest concern is that dropping objects from a
database will cause problems when attempting a restore? Is
this concern valid?
TIA,
Mike> My biggest concern is that dropping objects from a
> database will cause problems when attempting a restore? Is
> this concern valid?
You mean that next time you will restore the database? No, that will not
cause problems. One thing, though. Top free up space after dropping the
object you need to shrink the files. Because of this, before the next
restore, you either need to delete the database first, or use the REPLACE
parameter in the RESTORE command.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:057001c3a97b$cec6ea40$a401280a@.phx.gbl...
> All,
> I have many DTS packages pulling data from production
> servers to reporting servers. This is going to be changed
> so that the production servers push the data to the
> reporting servers.
> The production server DBA wants to periodically make a
> full backup of the databases, "zip" them, and FTP them to
> the reporting servers. On the reporting servers, the "zip"
> files will be un-zipped and the databases will be
> restored. The databases are scattered over half the US.
> Most of the tables, triggers, stored procedures, views,
> users, etc. in the copied databases are not needed for our
> reporting. I would like to be able to drop these objects
> from the reporting server databases immediately after they
> are restored. Doing so will free up significant amounts of
> hard drive space.
> My biggest concern is that dropping objects from a
> database will cause problems when attempting a restore? Is
> this concern valid?
> TIA,
> Mike
>
>sql