The problem is, you're asking the question in a vacuum of information. Maybe if you tell us what point you're trying to prove or disprove, we could assist you better.
Server crashes usually have so many other issues associated with them that one cannot pinpoint that X problem will cause one alone. And SQL Server is designed to handle high volumes of input.
If you're worried about information overload and your database Recovery Mode is FULL, change your it to Bulk-Logged during the import, then flip it back to FULL after the import is done. That will help with the processing issue at least.
As far as problems, all I can say is don't borrow trouble before it decides to haunt you. The record count you're listing is almost average for a VLDB data warehouse job (or below average even). Lots of people do even bigger data transfers without issues.
Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.