committed to the database. In other words a clean-up process is
performed to the extent that a detach does. The idea being the server
restarting the server processes. This tends to be a faster process than
broken. Some backup software like Veritas can perform on-line backups as
Andrew D. Newbould
>Why is it more risky to copy the files after stopping the server, rather than
>after a detach. I am asking because I want to in part use this as a method
>for backup and restore.
>
>Periodically, I want to take copies of the mdf and log files for later
>attachment under a new database name - but without detaching the existing
>database. So since I will stop the server anyway during backup, I thought it
>unnecessary to go through an extra step of detach/attach of the original that
>still need to run after the backup.
>Regards
>Bo
>
>"Andrew D. Newbould" wrote:
>
>> In message <#3qDpRkjFHA.1204@TK2MSFTNGP12.phx.gbl>, pheonix1t
>> <nothing@nothing.gone> writes
>> >hello,
>> >we use Protection Pilot (from McAffee), it installs a MSDE that it uses
>> >to store info about clients.
>> >so, I need to do a backup of the MSDE to send to their tech support
>> >people but their backup utility isn't working.
>> >They've tried for about 2 weeks now and it's not working.
>> >
>> >I asked the tech person about doing backup via command line and she
>> >looked into it, but it started asking for password!
>> >
>> >Neither of use knew about any MSDE passwords, so that didn't work either.
>>
>> This sounds a little fishy if you ask me.
>>
>> The instance of MSDE they installed for use with their software must
>> have got one or more user accounts assigned to it and these have
>> probably been assigned passwords. At a very minimum it MUST have an "sa"
>> user account. If your normal PC's Administrator password does not work
>> then it would suggest MSDE is running in SQL User Only mode. This then
>> brings the point that McAffee MUST know the passwords used when
>> installing and configuring the installation. It is therefore more likely
>> that they do NOT want to tell YOU (probably for very good reasons,
>> however, if their own tools ain't working ...).
>>
>> >I figured I'd ask here, what is a quick/easy way to do a backup of a
>> >MSDE via command line (taking into consideration I don't know what
>> >password it's asking for). I guess the sa account can be used, but how
>> >can I reset that account's password so the backups will work?
>> >
>> >thanks,
>> >
>> >dave
>>
>> One possible solution would be to use OSQL to detach their database from
>> the instance of MSDE and then send them the MDF & LDF files (they will
>> need both). They could then re-attach the database at their end to fix
>> the problems.
>>
>> Another, slightly more risky move, would be to stop MSDE from running
>> (ie: NET STOP [services]) and then copy the MDF and LDF files to them.
>> Again, they will need both files. Don't forget to restart the MSDE
>> services after the files have been copied.
>>
>> --
>> Andrew D. Newbould E-Mail: newsgroups@NOSPAMzadsoft.com
>>
>> ZAD Software Systems Web :
www.zadsoft.com >>
Andrew D. Newbould E-Mail: newsgroups@NOSPAMzadsoft.com