I have a monthly reporting process that requires that I pull data from one system (System A) and load it into SQL Server (System B), the system I'm pulling from generates a .CSV file. I have a table already built in SQL server to load the data in to
with the exact same column names as the .CSV and the datatypes match those that are in System A.
However when trying to load the .CSV via the import wizard it fails because it thinks there is the potential for data loss. Is there a way to override this overbearing tendency? Because the datatypes match there should be no way that data is lost.
View Complete Post