Solved

Missing Newline when importing Excel data

Posted on 2011-02-16
7
1,714 Views
Last Modified: 2012-05-11
I have an excel file that has been created from a Sharepoint data source..

That excel file has a cell that includes a new line in the middle of the data.

When I import that data using the Import wizard in SQL 2008, that new line character is dropped.

Any ideas how I can prevent that from happening?
0
Comment
Question by:MWilliamsBolton
  • 4
  • 3
7 Comments
 
LVL 39

Expert Comment

by:lcohan
ID: 34907598
It may not be "dropped" but not translated correctly. I believe in SQL a "new line" as you describe it you should have a ENTER = CRLF (0D0A in hex) and not just a LF(0A in hex) as new line indicator. MAke sure you have the appropriate data in excel or chose the right import format for line terminator in sql then it should work fine.
0
 

Author Comment

by:MWilliamsBolton
ID: 34908913
I tried to make the problem simpler by using Excel and that hasn't helped - just confused things.

I have written something that looks at every character in the SQL field and outputs the ASCII value.. I can now explain the problem a little better..

I have a text entry in Sharepoint that has a new line in the middle of it. When I export that to Excel and then import the Excel file, the new line is represented as LF (ascii 10).

However, when I import the data into SQL from Sharepoint using SSIS, the new line is replaced with a space (character 32). Do you know how I can stop this happening?
0
 

Author Comment

by:MWilliamsBolton
ID: 34909000
THe results from sharepoint will be passed to SSIS using XML. I suspect this will be part of the problem but I have no idea how to address it.. :-((
0
U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

 
LVL 39

Accepted Solution

by:
lcohan earned 500 total points
ID: 34909620
Do you have the EXCEL document created on a folder accessible to your SQL server? Then you could try import from EXCEL by using SQL commends and OLEDB like in the article below:

http://support.microsoft.com/kb/306397
0
 

Author Comment

by:MWilliamsBolton
ID: 34910189
The problem is I would need to use SSIS services to populate the Excel file. That process uses Sharepoint web services which uses XML. A new line is not recognised as a a new line when it is put in an XML file. It needs encoding which is not possible in Sharepoint without allowing the field to be formatted.. That is my only way forward I think. Thanks for your help..
0
 

Author Closing Comment

by:MWilliamsBolton
ID: 34910191
Thanks for your help..
0
 
LVL 39

Expert Comment

by:lcohan
ID: 34910299
If the input is an XML file and you don't need to mandatory generate your EXCEL file see maybe you could use the SP example below to read in the XML directly into your SQL database:


CREATE PROCEDURE dbo.my_XML_update
      @XMLData NTEXT,
      @myId SMALLINT
AS
SET NOCOUNT ON

-- Retrieve XML data
DECLARE @hocDoc INT

DECLARE @Comments NVARCHAR(2048)

EXEC SP_XML_PREPAREDOCUMENT @hocDoc OUTPUT, @XMLData

-- OPEN XML
-- Param1 is Pointer to DOC
-- Param2 is XML doc hiearchy
-- Param3 is Use Element Structure rather than Attributes


SELECT
      ContactId,
      ContactName
INTO
      #tmpContact
FROM
      OPENXML(@hocDoc, '/root/Contact', 2)
WITH (ContactId  INTEGER, ContactName NVARCHAR(50))

--this is how you populate the contact xml
SELECT Contact.ContactId,
            ISNULL(Contact.ContactName, '') AS ContactName
FROM #tmpContact Contact, Contact C
WHERE      Contact.ContactId = C.Id
ORDER BY      Contact.ContactName
FOR XML AUTO, ELEMENTS

-- Then you can do an INSERT
INSERT INTO Contact (Id, ContactName)
      SELECT ContactId,ContactName
      FROM #tmpContact

--or an UPDATE
UPDATE Contact SET ContactName = t.ContactName
FROM #tmpContact t
                  WHERE      contact.Id = #tmpContact.ContactId
            
-- Drop the temp Table
DROP TABLE #tmpContact

-- and MUST release XML doc to avoid memeory issues
EXEC SP_XML_REMOVEDOCUMENT @hocDoc
GO
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
First Max value 3 31
Get Next number from Stored Procedure 8 23
RESTORE MASTER DATABASE -- NOW 2 20
Setting variables in a stored procedure 5 21
How to leverage one TLS certificate to encrypt Microsoft SQL traffic and Remote Desktop Services, versus creating multiple tickets for the same server.
The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed
Via a live example, show how to shrink a transaction log file down to a reasonable size.

828 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question