Showing posts with label recover. Show all posts
Showing posts with label recover. Show all posts

Monday, March 26, 2012

Model database recovery planning

I cannot think of any reason, in our environment, why I would recover the model database. Change framework has all databases coming from DEV & QA before landing on PROD. We have never used the model database as framework of new databases either.

So, if I discontinued backup of the database, what is my recovery method if it become corrupt? Since mine is not used, can I simply copy it from another server?

Just keep either a BACKUP or a copy of the mdf/ldf files in safe storage.|||Just use the create script in your \install folder to recreate your model db.|||

Just be aware that it is an ESSENTIAL database in your system. There is one circumstance under which you do use it automatically for creating a database, and that is the initialisation of your tempdb every time you start the SQL Server service.

My understanding is that if model is not available then tempdb cannot be initialised and SQL Server will not start.

Monday, March 12, 2012

Missing Triggers

Hi,
I had a problem with a 12GB Database, where a failure on
the disks damaged the datafiles, leaving the database in
Suspect mode.
I managed to recover most of the data, with some data
missing from where the Data Pages where damaged.
No backups on this one (as usual), they where failing for
2 months
Then i created a new database, optimized for that size (5
datafiles top size=3.5GB) and moved the data.
And there it whnt online for users access
But somewhere on the process i forgot to activate the
triggers, when i detected my mistake the DB had already 1
week on prodution.
My question is: is there any way to force the Triggers to
execute (Insert) on data alread on a table?
> My question is: is there any way to force the Triggers to
> execute (Insert) on data alread on a table?
No, but depending on what your trigger code did, you could probably run a
manual update/insert process ...
http://www.aspfaq.com/
(Reverse address to reply.)
|||>No, but depending on what your trigger code did, you=20
could probably run a
>manual update/insert process ...
Hi, thanks for your reply
Yes i've tried to retransfer data using the export data,=20
but it seems that it disables the triggers before=20
inserting data.
I also tried to do a "insert into" a copy of the db but=20
some of the tables have a timestamp field that doesn=B4t=20
allow inserting data with a timestamp already on it.
Paulo Ferreira

Missing Triggers

Hi,
I had a problem with a 12GB Database, where a failure on
the disks damaged the datafiles, leaving the database in
Suspect mode.
I managed to recover most of the data, with some data
missing from where the Data Pages where damaged.
No backups on this one (as usual), they where failing for
2 months
Then i created a new database, optimized for that size (5
datafiles top size=3.5GB) and moved the data.
And there it whnt online for users access
But somewhere on the process i forgot to activate the
triggers, when i detected my mistake the DB had already 1
week on prodution.
My question is: is there any way to force the Triggers to
execute (Insert) on data alread on a table?> My question is: is there any way to force the Triggers to
> execute (Insert) on data alread on a table?
No, but depending on what your trigger code did, you could probably run a
manual update/insert process ...
http://www.aspfaq.com/
(Reverse address to reply.)|||>No, but depending on what your trigger code did, you=20
could probably run a
>manual update/insert process ...
Hi, thanks for your reply
Yes i've tried to retransfer data using the export data,=20
but it seems that it disables the triggers before=20
inserting data.
I also tried to do a "insert into" a copy of the db but=20
some of the tables have a timestamp field that doesn=B4t=20
allow inserting data with a timestamp already on it.
Paulo Ferreira