Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #2132
| From | Erland Sommarskog <esquel@sommarskog.se> |
|---|---|
| Newsgroups | comp.databases.ms-sqlserver |
| Subject | Re: How to backup SQL Express 13 |
| Date | 2022-05-10 09:41 +0200 |
| Organization | Erland Sommarskog |
| Message-ID | <XnsAE93629CB7D32Yazorman@127.0.0.1> (permalink) |
| References | <t5aqus$9v2d$1@tota-refugium.de> <XnsAE929550276E3Yazorman@127.0.0.1> <t5bg88$aehe$1@tota-refugium.de> <XnsAE92E9E405CFEYazorman@127.0.0.1> <t5d3ds$bbi0$1@tota-refugium.de> |
Tim Ritberg (tim@server.invalid) writes: > Am 09.05.22 um 22:59 schrieb Erland Sommarskog: >> Tim Ritberg (tim@server.invalid) writes: >>> To connect from another host, which is doing backup. >>> >> >> And what do you want the final result to be? Where do you want the >> backup? And I don't still don't see why you would a separate user. Then >> again, I have a feeling that you have not told the full story yet. > > Same procedure like mysqldump. I dont know which format is best for > MsSQL, a SQL dump or a binary file? Just some file to store somewhere > else, but not that desktop pc. Sorry, this is a newsgroup for Microsoft SQL Server. You can't expect people here to know what mysqldump is. I have a vague recollection that is actually a list of INSERT statements. A backup that you take with the BACKUP statement in SQL Server is indeed a binary file. Since it is SQL Server that writes the backup, the backup must be written to a destination where SQL Server has write access, either local disk or a file share. But it is a good idea to copy the backup elsewhere, once you have taken it. Yes, you can can also generate INSERT statemnents, but such a dump may not be transactionally consistent. This is why you want a real backup.
Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Next in thread | Find similar
How to backup SQL Express 13 Tim Ritberg <tim@server.invalid> - 2022-05-09 12:38 +0200
Re: How to backup SQL Express 13 Erland Sommarskog <esquel@sommarskog.se> - 2022-05-09 14:40 +0200
Re: How to backup SQL Express 13 Tim Ritberg <tim@server.invalid> - 2022-05-09 18:41 +0200
Re: How to backup SQL Express 13 Erland Sommarskog <esquel@sommarskog.se> - 2022-05-09 22:59 +0200
Re: How to backup SQL Express 13 Tim Ritberg <tim@server.invalid> - 2022-05-10 09:15 +0200
Re: How to backup SQL Express 13 Erland Sommarskog <esquel@sommarskog.se> - 2022-05-10 09:41 +0200
Re: How to backup SQL Express 13 Tim Ritberg <tim@server.invalid> - 2022-05-10 09:52 +0200
Re: How to backup SQL Express 13 Erland Sommarskog <esquel@sommarskog.se> - 2022-05-10 16:13 +0200
Re: How to backup SQL Express 13 Tim Ritberg <tim@server.invalid> - 2022-05-10 18:11 +0200
Re: How to backup SQL Express 13 Erland Sommarskog <esquel@sommarskog.se> - 2022-05-10 22:56 +0200
Re: How to backup SQL Express 13 Tim Ritberg <tim@server.invalid> - 2022-05-11 09:37 +0200
Re: How to backup SQL Express 13 Anton Shepelev <anton.txt@g{oogle}mail.com> - 2022-05-11 12:54 +0300
Re: How to backup SQL Express 13 Tim Ritberg <tim@server.invalid> - 2022-05-11 12:21 +0200
Re: How to backup SQL Express 13 Anton Shepelev <anton.txt@g{oogle}mail.com> - 2022-05-11 13:40 +0300
Re: How to backup SQL Express 13 Erland Sommarskog <esquel@sommarskog.se> - 2022-05-11 20:00 +0200
Re: How to backup SQL Express 13 Tim Ritberg <tim@server.invalid> - 2022-05-11 22:34 +0200
Re: How to backup SQL Express 13 Erland Sommarskog <esquel@sommarskog.se> - 2022-05-11 22:42 +0200
Re: How to backup SQL Express 13 Tim Ritberg <tim@server.invalid> - 2022-05-11 23:02 +0200
Re: How to backup SQL Express 13 Anton Shepelev <anton.txt@g{oogle}mail.com> - 2022-05-11 15:28 +0300
csiph-web