December 9, 2013 at 2:16 am
Hi,
There exists a sql file (.sql) containing some create statements and bunch of inserts , details unknown and the size is 660 MB and needs to be run against a particular database in sql server 2008 R2. On tryingto open this file / attempts to rn this from sqlcmd /osql it gives scripting error as the error or insufficient resources as the options.
Any help to work on this file execution will be helpful.
/Supriya
December 9, 2013 at 2:30 am
share the complete error which is being generated while executing this file
December 9, 2013 at 3:35 am
sqlcmd:Scriptting error
This is what I get on the cmd line
December 9, 2013 at 3:51 am
in our environment also , we faced the same issue. The solution we found is, we have split the files into multiple files and executed those in the same order. We preferred each file size <= 8 MB in size
December 9, 2013 at 6:09 am
I've always moved CREATE statements to a single file, and INSERT statements are not insert statements at all, but actually files exported via BCP;
then i write the appropriate BCP/BULK INSERT scripts to bring the files in; the performance difference is multiple orders of magnitude faster than hundreds of megs of INSERT INTO statements; i can easily import a gigabyte of data in several minutes, and without the chances of running out of memory for the parsing of the statements.
Lowell
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply