From: esquel@sommarskog.se   
      
   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.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)