Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Erland Sommarskog Newsgroups: comp.databases.ms-sqlserver Subject: Re: How to backup SQL Express 13 Date: Tue, 10 May 2022 09:41:38 +0200 Organization: Erland Sommarskog Lines: 26 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Injection-Info: reader02.eternal-september.org; posting-host="501af51d46109d974e84569e6f3c2d7c"; logging-data="28070"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+zmepdHNycQg2YBISY0WIE" User-Agent: Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32) Cancel-Lock: sha1:dLpqJ0MWLd3xjRoZjRhA+WVNF2k= Xref: csiph.com comp.databases.ms-sqlserver:2132 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.