From: mads001@xxxxxhotmail.com   
      
   Den 16-08-2014 10:55, Erland Sommarskog skrev:   
      
   Thanks for the answer, Erland.   
      
   > Mads Aggerholm (mads001@xxxxxhotmail.com) writes:   
   >> I am about to move a DB from a 10.50.1600 MS SQL Server to a 10.0.1600   
   >> Server.   
   >   
   > That's the RTM version of both SQL 2008 and SQL 2008 R2. Don't you believe   
   > in service packs?   
   >   
      
   That's beyound my influence. It's for some customer, who will not upgrade.   
      
   >> Backup the SB and restoring in the new place is impossible, since the   
   >> version does not 'fit'. I did already try setting it to 'Level 90', but   
   >> no luck.   
   >   
   > That's right. You cannot restore a backup from a higher version of SQL   
   > Server on a lower version.   
   >   
   >> I scriptet the whole thing, including data, and got a large file, about   
   >> one Gbyte.   
   >> This is far too big for the MS SQL Server to handle.   
   >   
   > It's far too big for SQL Server Management Studio. Whether it is too   
   > big for the engine is a moot question, since the engine will never   
   > see the full script, only the batches.   
   >   
   >> On the internet i forund this:   
   >> sqlcmd -S xxx.xxx.xxx.xxx -i C:\SQLFOLDER\database.sql -o   
   >>   
   >> Unfortunately, it does not work.   
   >   
   > What does "it does not work" mean? I seem to recall that I have been   
   > able to load very large files with SQLCMD, at least with the 64-bit   
   > version of SQLCMD.   
   >   
      
   First, it says: "Sqlcmd: '-o': Missing argument. Enter '-?' for help."   
      
   Then I type '-?', and get the message: "'-?' is not regoqnized as an   
   internal or external command, operable program or batch file."   
      
   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].   
   Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A   
   network-related or in stance-specific error has occurred while   
   establishing a connection to SQL Server. Server is not found or not   
   accessible. Check if instance name is correct and if SQL Server is   
   configured to allow remote connections. For more information see SQL   
   Server Books Online.   
   Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Login timeout   
   expired."   
      
   > But else, try a third-party product for your situaton, like Red Gate's   
   > SQL Compare. (There is an evaluation license for 14 days, I seem to recall.)   
   >   
      
   Not possible, since I'm not allowed to install other software at the   
   customer's servers.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)