Bulk Insert Runs out of space

Hello,

I am running a Bulk Insert and getting the error that the PRIMARY file group
is full. All the databases in the server have the Autogrow check box
selected and there is over a 100 GB space available on the hard drive. The
transaction log is set to autogrow as well.

Is there a maximum file size for the primary datafile? The size is
currently at 1.8 GB

Can someone help with some ideas for getting around this error.

Thanks

Hardee Mahoney
Washington, DC USA


.

Relevant Pages

  • Re: Help on transactional replication
    ... I have left the database/log size to autogrow and will keep an eye on ... keeping the distributor on a subscriber server instead of keeping it ... on how to read and understand processor and memory usage things. ...
    (microsoft.public.sqlserver.replication)
  • Re: Virtual SQL Server Transaction Log Auto-Grow problem.
    ... it is recommended to grow the data/logs manually as autogrow is expensive. ... As with any other service packs/security patches/hotfix, it is important to test the patch first on a dev/test server and then apply it on prod server. ... Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Primary File Group Full
    ... I still feel a little lost on this one. ... All of my databases are set to "Automatically Grow" by 10% each time. ... Primary File Group Is Full. ... > me what this means and how to go about correcting it? ...
    (microsoft.public.sqlserver.server)