Given my index space is still growing, the problem seems to lie there. Still seems ridiculous. It has now used 240GB of log space to import an 18GB table.

Also of interest, while the destination table (which was empty before insert) is estimated at 50+ GB just for data, the source table is only 18GB. What am I...

Folks, please accept my apologies for the misleading title. There is no "log growth," and the title should read "log usage."

I would suggest installing processmon to find out more. It looks like a missing library or bad reg entry, at a glance, but I have not encountered that error first...

Not necessarily. As soon as the transactions have been delivered to the distribution database (assuming it's transactional replication), you should be able to truncate the log.

http://msdn.microsoft.com/en-us/library/ms151740%28v=SQL.100%29.aspx

One hack would be to add another log file on a different volume, if you have the space. You can also try to stop the log reader, issue the appropriate...

Use DBCC opentran to help identify the problem. Replication is likely the culprit.

You can either delete them all and reinsert a single copy or create a join and use delete top (n). The top (n) strategy will only work when n is...

Depending on the recovery model and DR strategy, you can also restore only the pages you are concerned with...

Several options here:

1. SSIS

2. Linked Server (Personally, I would shy away from this.)

3. OpenRowset

Note: Last I checked there was no 64 bit Jet driver available, which can add a bit...

If you want them to always be non null, you can consider an alter table statement with a "with values' clause in addition to default constraints of '' for each...

Nicely done. Very amusing, esp the "They will expect to see various diagrams an code such as this."

It's a shame that people actually posted here to complain. On the...

Phil Parkin (3/25/2010)

---

Tim Weintz (3/24/2010)

---

Another option is to load all data into a single column and write custom code to parse it, afterwards. Similar to the idea of loading it...

Another option is to load all data into a single column and write custom code to parse it, afterwards. Similar to the idea of loading it into an array, except...

Happy Cat, thank you for taking the time to respond to my original post. I followed your advice, and it resolved the issue.