Creating & Maintaining Demo Database

I would like to create a demo database. Here are the specifications.
1. I need an easy way to store the sample data so that the database can
be refreshed after use and put back to its original data.
2. I am constantly making changes to the production database that this
demo is based off of. I would like to have a simple way of keeping the
demo database (table structures and stored procedures) in sync with the
production database without affecting the data (see #1). I worry about
making changes to the production database and forgetting to make the
change in the demo database.
I have some ideas but would love to hear how others have done this sort
of thing.
Thanks in advance,
Debbie
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!1. Back it up and restore it whenever you need to...
2. Every shop handles this type of thing differently, but my personal core
rules are: Never make changes on a production database via Enterprise
Manager, Query Analyzer's UI options, or any other database frontend UI.
Instead, script all changes and check them in to a source control system
(e.g. Visual Source Safe). This keeps a very good audit trail and allows
you to easily roll changes to other databases without scratching your head
and wondering what has changed between versions. Another option is to use a
product like Red Gate's SQL Compare, but I highly recommend you get into the
habit of scripting changes and storing them instead of relying on software
to find the changes after you make them (in other words, be proactive rather
than reactive!)
"Debbie" <anonymous@.email.com> wrote in message
news:ukvh7#K$DHA.1548@.TK2MSFTNGP12.phx.gbl...
> I would like to create a demo database. Here are the specifications.
> 1. I need an easy way to store the sample data so that the database can
> be refreshed after use and put back to its original data.
> 2. I am constantly making changes to the production database that this
> demo is based off of. I would like to have a simple way of keeping the
> demo database (table structures and stored procedures) in sync with the
> production database without affecting the data (see #1). I worry about
> making changes to the production database and forgetting to make the
> change in the demo database.
> I have some ideas but would love to hear how others have done this sort
> of thing.
> Thanks in advance,
> Debbie
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!|||Thanks for the response.
On the backup/restore solution, I am concerned that when we make changes
to the database, the restore will overwrite any of our changes with the
old version.
Any other ideas will be welcome, I really want to think this through
before turning something over to my sales department.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Yes, it will overwrite any changes. So restore, apply your changes, then
back up the new version
"Debbie" <anonymous@.email.com> wrote in message
news:efdRKVL$DHA.268@.TK2MSFTNGP10.phx.gbl...
> Thanks for the response.
> On the backup/restore solution, I am concerned that when we make changes
> to the database, the restore will overwrite any of our changes with the
> old version.
> Any other ideas will be welcome, I really want to think this through
> before turning something over to my sales department.
>
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!