There are a few things to watch out for on importing. (At least with MySQL, not sure if MSSQL has the same issues, but I would think so).
There are few characters that must be escaped: NEWSTR=CHANGE(NEWSTR,"\","\\") NEWSTR=CHANGE(NEWSTR,"%","\%") NEWSTR=CHANGE(NEWSTR,"_","\_") Also, I found that dates need to be in YYYY-MM-DD format to import as a date I don't know if the characters need to be escaped if you use the INSERT/UPDATE method as suggested. But using the INSERT/UPDATE method has one big advantage over importing in that the order of the fields does not need to be the same order in the file description (unless you don't specify the fields you are updating). George > -----Original Message----- > From: [email protected] [mailto:u2-users- > [email protected]] On Behalf Of Wols Lists > Sent: Tuesday, August 17, 2010 4:42 AM > To: U2 Users List > Subject: Re: [U2] Unix to SQLServer > > On 17/08/10 05:47, Norman, David (Health) wrote: > > Thanks to all who responded. After managing to extract a bit more > info from the user on what they think they might want, it now seems > that all we need to do is put a CSV in a Samba share that can then be > imported into MS SQL Server. Simple. > As simple, think about spitting out a script rather than a CSV that you > can run rather than import. Might be a better solution, might not. It's > fairly easy, just wrap your csv line in an update or insert statement. > > Cheers, > Wol > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
