space 1

[cruel]

I am trying to load in a table of size about 3.3GB to a database I designated to a storage drive (not default SQL app drive). I got 4.5 GB left on this storage drive. I tried coupe of times, always run into log file is full. But the log file is really brand new. What do I do to get around the space issue. Early response is very appreciated!

 

[cruel]

more specifically, for a table of size 3.5GB, how much space do I need to assign to log file? Thanks

 

[nigelrivett]

depends how you are loading it.
If you have the database in simple recovery mode and load in small bactches or a fast bcp then a few Mb log file should be OK.

======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.

 

[cruel]

Thanks, nigelrivett. I am totally new to MS SQL server, so I am using the wizard, instead of BCP command. I did specify simple recovery mode though. How do I do the small batch thing in wizard? Should I use increment by MegaBytes instead of precent?

 

[nigelrivett]

No that'll still grow.
Bcp would be the fastest and easiest - look it up in bol

for the bcp out

exec master..xp_cmdshel('bcp dbname..mytbl out c:\file.txt -n'

in
exec master..xp_cmdshel('bcp dbname..mytbl in c:\file.txt -n'

If you have no indexes on the table then the tr log shouldn't grow much - only to log extent allocation.

======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.