| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 3 months |
| seen | Feb 29 '12 at 11:08 | |
| stats | profile views | 10 |
|
Jul 8 |
comment |
Restoring a SQL database in a production environment as an update mechanism I will check out the tools you mention as well, thanks. |
|
Jul 8 |
comment |
Restoring a SQL database in a production environment as an update mechanism Thanks Robert, I had a meeting with the dev team yesterday and we have agreed that I will have complete responsibility for database restores. Turns out the DB is read only apart from a handful of tables so we're going to split those out to a separate database (they do not need to be restored to update them). This will not even require cross database queries apparently. |
|
Jul 5 |
comment |
Restoring a SQL database in a production environment as an update mechanism Hmmm ... I'm not sure if they do mirror it back but I will check. I think data loss will be my angle when I approach the dev team. Is there anything else that could go wrong during a restore? Or any other drawbacks to the approach that you can think of aside from data loss? |
|
Jul 5 |
comment |
Restoring a SQL database in a production environment as an update mechanism Unfortunately we cannot snapshot as the edition is SQL Standard. The database is not read-only either! But the services (web servers mainly) that read and write to the DB are shutdown prior to the restore, as you might expect. |