From: esquel@sommarskog.se   
      
   Mads Aggerholm (mads001@xxxxxhotmail.com) writes:   
   > That's beyound my influence. It's for some customer, who will not upgrade.   
      
   Idiots!   
      
   >>> On the internet i forund this:   
   >>> sqlcmd -S xxx.xxx.xxx.xxx -i C:\SQLFOLDER\database.sql -o   
   >>>   
   >>> Unfortunately, it does not work.   
   >   
   > First, it says: "Sqlcmd: '-o': Missing argument. Enter '-?' for help."   
      
   Yes, -o takes an argument. This option redirects the output to a file.   
      
   > Then I type '-?', and get the message: "'-?' is not regoqnized as an   
   > internal or external command, operable program or batch file."   
      
   You are supposed to type   
      
      sqlcmd -?   
      
   You can also find information about the command options to SQLCMD in Books   
   Online.   
      
   > Well, I ommit the '-o' and tries without it:   
   >   
   > If waits for some seconds, then says:   
   > "HResult 0x2, Level 16, State 1 Named Pipes Provider: Could not open a   
   > connection to SQL Server [2].   
      
   So you did not specify the name of the instance correctly. This is no   
   different from how you do it in SSMS. It has nothing to do with the size   
   of your scripts.   
      
   --   
   Erland Sommarskog, Stockholm, esquel@sommarskog.se   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)