I'm sending some data to a client to load. I want to give the client an easy way to load the data -- simple for them and quick for me to prepare. The easiest way I can see to do this is to write a load_data.sql file with a series of BULK INSERT statements.
Some of the original data is in SQL SERVER 7.0, and the target is (currently) SQL SERVER 7.0. Others are in MS EXCEL. I tried two exports, first into an EXCEL .csv file. Using BULK INSERT resulted in the quote marks ("
around each field being imported into the database as part of each value. Not good.
Then I tried into a tab-delimited .txt file (fortunately there are no Tab characters embedded in the data). This has the result of _sporadically_ importing Tab characters into two of the later (and longer) columns, occasionally concatenating the whole next row into the last column value. This stinks, and I don't see the pattern to it.
Is there something I'm doing wrong? What are my alternatives for a quick way to share data?
Thanks,
Avery Cohen
PS
I tried BCP, but get errors with even the most simple requests - SQL Server does not exist or access denied, perhaps due to the fact that I've been using NT Authentication to connect to SQL Server?
Some of the original data is in SQL SERVER 7.0, and the target is (currently) SQL SERVER 7.0. Others are in MS EXCEL. I tried two exports, first into an EXCEL .csv file. Using BULK INSERT resulted in the quote marks ("
Then I tried into a tab-delimited .txt file (fortunately there are no Tab characters embedded in the data). This has the result of _sporadically_ importing Tab characters into two of the later (and longer) columns, occasionally concatenating the whole next row into the last column value. This stinks, and I don't see the pattern to it.
Is there something I'm doing wrong? What are my alternatives for a quick way to share data?
Thanks,
Avery Cohen
PS
I tried BCP, but get errors with even the most simple requests - SQL Server does not exist or access denied, perhaps due to the fact that I've been using NT Authentication to connect to SQL Server?