I have a query file, test.sql, in the root of my C drive. It is
400,000 lines worth of insert into statements and is so big i cannot
load in into management studio. How can I run this?

On Wed, 31 Oct 2007 17:02:36 -0700, "mitchman10 [at] gmail.com"
<mitchman10 [at] gmail.com> wrote:

>I have a query file, test.sql, in the root of my C drive. It is
>400,000 lines worth of insert into statements and is so big i cannot
>load in into management studio. How can I run this?

Add a line with nothing but a GO every, oh say after every 100 INSERT
commands. Then you could TRY to execute the file using the command
line utilities OSQL or SQLCMD. I'm not sure if they will choke on a
file that size as I've never had reason to test them in that way.

Roy Harvey
Beacon Falls, CT

Roy Harvey (SQL Server MVP) wrote:

> On Wed, 31 Oct 2007 17:02:36 -0700, "mitchman10 [at] gmail.com"
> <mitchman10 [at] gmail.com> wrote:
>
>> I have a query file, test.sql, in the root of my C drive. It is
>> 400,000 lines worth of insert into statements and is so big i cannot
>> load in into management studio. How can I run this?
>
> Add a line with nothing but a GO every, oh say after every 100 INSERT
> commands. Then you could TRY to execute the file using the command
> line utilities OSQL or SQLCMD. I'm not sure if they will choke on a
> file that size as I've never had reason to test them in that way.

Failing that, split it up into multiple files (by whatever means you
like) and execute them individually.

On Wed, 31 Oct 2007 18:38:12 -0700, Ed Murphy <emurphy42 [at] socal.rr.com>
wrote:

>Roy Harvey (SQL Server MVP) wrote:
>
>> On Wed, 31 Oct 2007 17:02:36 -0700, "mitchman10 [at] gmail.com"
>> <mitchman10 [at] gmail.com> wrote:
>>
>>> I have a query file, test.sql, in the root of my C drive. It is
>>> 400,000 lines worth of insert into statements and is so big i cannot
>>> load in into management studio. How can I run this?
>>
>> Add a line with nothing but a GO every, oh say after every 100 INSERT
>> commands. Then you could TRY to execute the file using the command
>> line utilities OSQL or SQLCMD. I'm not sure if they will choke on a
>> file that size as I've never had reason to test them in that way.
>
>Failing that, split it up into multiple files (by whatever means you
>like) and execute them individually.

Which might be no more work than adding the GO lines.

Roy Harvey
Beacon Falls, CT