Importing a large SQL script into SQL Server?

6,746

Solution 1

If you're only trying to copy it into the query analyzer to run it, maybe you could just create a batch file using OSQL to run it from the command prompt.

Here's the MSDN for OSQL: http://msdn.microsoft.com/en-us/library/aa213090.aspx

Solution 2

You can always take your database offline and detach it. Then you can just copy the physical files over to the other server and attach it. Easy way.

Share:
6,746

Related videos on Youtube

James McMahon
Author by

James McMahon

Updated on September 17, 2022

Comments

  • James McMahon
    James McMahon over 1 year

    I'm trying to move a database from our production server to our test server. I've used Microsoft's Database Publishing Wizard to create a script containing the schema and data for the production database.

    However **I can't figure out how to load this script into our test database.**The resulting script is about 500mb, which isn't 'large' by database standards but large enough that I can't copy and paste it into the query analyzer. Alternatively, when I try and open the file directly with the SQL Server Management Studio it complains

    The operation could not be completed. Not enough storage is available for this operation.

    This error happens before I select a database, so I believe it is the Management Studio complaining about not having enough memory to load a 500mb file.

    Any advice?

  • James McMahon
    James McMahon almost 15 years
    I'd vote you up but it requires 15 rep, but this does seem to be working, thank you.
  • Sean Howat
    Sean Howat almost 15 years
    No problem. Glad it's working.
  • James McMahon
    James McMahon almost 15 years
    Yeah I don't have admin privileges on the production machine, but I have enough privileges to generate a creation script.
  • Kejml
    Kejml almost 15 years
    The poster doesn't mention the version of SQL Server. On later versions I would use sqlcmd, this is functionally equivalent to osql though.
  • James McMahon
    James McMahon almost 15 years
    @Joel, The remote server is SQL server 2000, but locally I have the 2005 tools.