SQL Server Data Transfer: Module Summary
You can now distinguish three related workflows: a guided copy through the Import and Export Wizard, a maintainable integration process in SSIS, and a file transfer through bcp.
What to remember
- Choose a tool from the transfer requirements, not the age of an example.
- Define mappings and file formats before loading data.
- Use bcp in an operating-system terminal; use T-SQL in a database query tool.
- Distinguish the machine running bcp from the server accessing a BULK INSERT file.
- Check permissions, rejected rows, counts, and business totals.
- Plan logging and retries; bulk loading is not automatically unlogged or safe to repeat.
A practical decision
For a one-time guided transfer, start with the wizard. For recurring cleansing and transformation, consider an SSIS package with operational logging. For a scripted table-to-file or file-to-table operation, consider bcp. A complete database migration requires separate planning for schema, security, and other database objects.
Self-assessment
Can you explain why a file path that works in a desktop terminal may fail in a server-side job? Can you identify what happens when an import is repeated? These questions connect command syntax to a reliable operational process.
Complete the bcp exercise, then review the module quiz. The retained quiz filename is historical; the questions cover the current SSIS and bcp workflow.