Post reply

Linked server to text file - column names messed up

  • November 14, 2008 at 3:51 am

    #202815

    I have a process that generates a text file from our Avaya phone system which has two columns - Extension and Name. The file is saved directly onto a network share on the SQL server. I use this to import the extensions into both our Active Directory and SharePoint phone books daily via a linked server.

    Until recently, I was running the Avaya export process on a Vista 32 bit machine. I have now upgraded my machine to Win2008 64 bit. I am running the same scheduled task to generate the text file and it looks the same to me as it always has.

    But the sql linked server no longer works properly. It can't seem to read the column names now. Instead of getting Extension and Name it gets  and F2. I can't figure out why. I've tried using different collation settings, and creating the text file manually, but nothing seems to help. Anyone got any ideas what might have happened?

  • November 14, 2008 at 6:52 pm

    #898942

    If dropping and recreating the linked server doesn't do it for you, then I think you're pretty much toast for using a linked server to read the files. There's lots of differences between the 32 bit and 64 bit versions and I believe that little problem is one of them. You may have to switch your logic to use Bulk Insert or some such instead.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • August 11, 2010 at 2:58 pm

    #1205728

    Run instcat.sql provided by install package on 32 bit system and now cretae linked server on 64 bit to talk to 32 bit system.

    The above works for sql server 2000 32 bit /64 bit .Not sure for later versions.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply