Re: Strategy for backup and restore
From: Andrea Montanari (andrea.sqlDMO_at_virgilio.it)
Date: 05/27/04
- Next message: Aaron Bertrand - MVP: "Re: Access - MSDE question"
- Previous message: Andrea Montanari: "Re: MSDE newbie quetsion: importing data from SQL Server"
- In reply to: a fast learner newbie: "Re: Strategy for backup and restore"
- Next in thread: newbie: "Re: Strategy for backup and restore"
- Reply: newbie: "Re: Strategy for backup and restore"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 27 May 2004 21:21:56 +0200
hi,
"a fast learner newbie" <anonymous@discussions.microsoft.com> ha scritto nel
messaggio news:DE5761E3-5DC3-4023-B5CA-E6BAD158F2FB@microsoft.com...
> 1> Andrea you say that simple copy and paste is not good. But why, what
is wrong
>or missing with it Or what better does backup/restore do which simple
copy/paste
>(means copy and paste the db to some location while backup and do the
opposite
> while restoring) cannot do. I can take care of prompting the user to
close everything
> and even MSDE if needed. Does anyone actually use copy/paste technique
for this
> purpose or is it only me who thought of it.
I strongly do not recommend this becouse you don't have to confuse Access
*.MDB databases with SQL Server databases, and simply doing a file copy will
lead to unclean bakup and disaster...
checkpoints can be performed to flush transactions depending on recovery
model and so on..
you are not alone in this thinking, but I warn you this is not recommended,
or, at least I don't..
please do your self a favour and correctly backup databases using SQL Server
supported features...
that's to say BACKUP DATABASE ....
> 2> you say that "is it is mandatory the database is not in use..", but I
thought based
>on what I read that there should be no other connection to database while
restoring
>…please confirm.
in order to backup it is not mandatory, while it is for restore operation...
perhaps I've read wrong your requirement, but if you want the database not
to be in use while backing up, you can alter it in single user mode...
for restore operation, no one must be connected to it, at least with SQL
Server 2000.... next SQL Server generation will support it..
> Also sp_who returns the active users, my app will always talk to database
as 1 user only ( The problem is that my app might be installed on more than
>1 machine, being used by different people and talking to the db using the
>same sql server user...I know it is not perfect setup, but that's the way
we
>want it for now), so in this case there will always be one user only, then
how
>do I determine if no one else is talking to db..
you can simply check for anyone using database "xxxx"... if it's in use,
then you have to wait or kicke them off...
>If I use ROLLBACK IMMEDIATE then other people on other machine might
>loose their data.. Isn't it.
=;-D
ON ERROR GOTO HELL
=;-)
> 3> "Suspect" if restore fails,.. Sounds interesting,
nope... it's not interesting when your user loses his/her data... you will
lose your sleep...
>but before I bug u with any question related to this, let me do some more
research on it ..
you are wellcome
> And Cheers ("Nobile di Montepulciano")
> :-)
good choice... but "Sassicaia" shoul'd be better... never tried... it's not
that cheap my wife allow me to buy it :-(
-- Andrea Montanari (Microsoft MVP - SQL Server) http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0 (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface) --------- remove DMO to reply
- Next message: Aaron Bertrand - MVP: "Re: Access - MSDE question"
- Previous message: Andrea Montanari: "Re: MSDE newbie quetsion: importing data from SQL Server"
- In reply to: a fast learner newbie: "Re: Strategy for backup and restore"
- Next in thread: newbie: "Re: Strategy for backup and restore"
- Reply: newbie: "Re: Strategy for backup and restore"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
