1

I have over 18GB of database .sql file, which have over 200 Millions records. My server have Xeon E5 processor, 16GB ECC RAM and SSDs. I have SQL Server 2014 Web Edition and Windows Server 2012.

I know I would need sqlcmd to run huge database so my command is this

sqlcmd -S SQL-Server2014 -i C:\main_db.sql -d newtest -o D:\main_db_log.txt

When I start this command, T-SQL command line utility start working it's magic. But after few minutes it use full 16GB of RAM and server crashes.

main_db_log.txt show's this error

Sqlcmd: Error: Scripting error.

I tried to restrict SQL Server to use only 10GB by limiting memory in ServerInstance > Properties > Memory Tab but it didn't work.

I researched around but only found out about sqlcmd to run large databases but it's not working in my case.

Please help, because our old server crashed and I can't make .bak file there anymore.

Improve this question
9
  • One doesn't "execute" a database (although I have a few I wouldn't mind taking out hunting....). You've not given enough information about the database or the query(ies) you're running or even what you're really trying to achieve for people to guess here. Commented Dec 5, 2016 at 18:53
  • @alroc: Sorry about word execute, I am a newbie with Databases. I just want to add the whole database's records in newtest in MS SQL Server 2014 but I only used the single line above sqlcmd. Still having memory issues and scripting error. Commented Dec 5, 2016 at 19:03
  • Again, without seeing what your query(ies) are actually doing, it's impossible to even guess. You've got an error related your script - so show the script and maybe we can find the error. How big is main_db.sql? Also look at stackoverflow.com/questions/24665757/sqlcmd-scripting-error and dba.stackexchange.com/questions/16763/… Commented Dec 5, 2016 at 19:22
  • there are only insert commands on each line with just two columns, 1st is id and second is sales_id and database slze is 18GB. I saw the questions you recommended, should I use GO every 1000 lines? Commented Dec 5, 2016 at 19:33
  • If you have tens of thousands of INSERT statements yes, it would make sense to break them into smaller batches. Commented Dec 5, 2016 at 19:40
Related questions
7
sqlcmd won't run - Is this a config issue?
2
SQLCMD stops at first GO it reaches in script
2
SQL Server 2012 OUT OF MEMORY error messages
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.