How do I import a big sql file in MS SQL Server 2012?

Question

0.00/5 (No votes)

See more:

Hi all,

My web host is moving all MS SQL Server databases from SQL Server 2008 (or possibly 2005) to 2012. I have Management Studio but am not sure of what to use.

I have done some searches on the web but am still not sure what's the best approach and I don't want to mess things up. I did an export from the old DB and chose to include both schema and data. The .sql file is 145 MB in size. I'm not going to append any data; it's a clean install.

How do I import this file into MS SQL Server 2012?
- I can't open it and just hit F5 as it's so big (or so I presume).
- The SQL Server import and export wizard doesn't have .sql file as an option.
- The Copy database feature didn't work (it says "The SQL Server agent does not appear to be running on the destination server...").

I'd be very grateful for any help here.

Thanks!

Posted 29-Oct-15 23:04pm

petter2012

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

phil.o · Accepted Answer · 2015-10-29T23:12:00

Solution 1

You may try another way: instead, make a SQL backup from the source server.
You will get a .bak file.
Then, restore to the new server, using the generated .bak file.
Finally, check that the connections to the new server match those of the old one.

Here's a link that you may use for these operations, if you are not familiar with them:
Back Up and Restore of SQL Server Databases[^]

This would be much more safe than trying to import from a 145 Mb file :)

Good luck, hope this helps.

Posted 29-Oct-15 23:12pm

phil.o

v2

Comments

petter2012 30-Oct-15 10:58am

Thank you, I'm sure you are correct. However, I didn't seem to have privilegies to perform a backup, and not to do a Copy database either... I ended up using the Export wizard. Now that tables and their data are moved; I only need to script the sp's as well.

Thanks again!

phil.o 30-Oct-15 10:59am

You're welcome :)