Results 1 to 10 of 10
  1. #1
    Join Date
    Jul 2003
    Posts
    123

    Unanswered: 128 characters limit on path in DTS?

    Hello,

    Im currently working with a DTS-package used for importing a Excelsheet into SQL-server.

    I have a "Microsoft Excel 97-2000" as source and a "Microsoft OLE DB" as destination.

    A "Transformation Data Task" is used to shuffle the data.

    The package works ok as long as the path for the Excelsheet doesn't exceed 128 characters! Then it gets truncated at 128 characters and of course the data task can't find the file......

    I can browse to my excelsheet, and when I look at the path it's ok. But when I close the package and then opens it again the path is truncated at 128 characters. Grrrr.

    Is this a set limit in SQL Server or is it something I can mail the databaseadministrator about tomorrow?

  2. #2
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    Since we don't know the details of the package being used, I'd think your dba would be the first person to contact to resolve the issue.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  3. #3
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    Move the file?

    I dislike DTS for sooooo many reasons
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  4. #4
    Join Date
    Jul 2003
    Posts
    123
    Quote Originally Posted by blindman
    Since we don't know the details of the package being used, I'd think your dba would be the first person to contact to resolve the issue.
    I even made a new DTS from scratch with the excelsheet, OLE DB and the transformation.... only these three components. Same behaviour. Grrr.

    I guess I'll have to talk to the DBA tomorrow then... see if he can explain it.
    Last edited by oneleg_theone; 06-29-06 at 03:51.

  5. #5
    Join Date
    Jul 2003
    Posts
    123
    The DBA had never heard about any limit on the path.

    The limit in windows SHOULD be 245 characters.

    My hunt on the internet for answers encountered this text:

    "I was running MS Access 2000 with Windows 2000 - Service Pack 3.
    (Note: It is NOT Office 2000 with SP3, it is the OPERATING SYSTEM with SP3!)
    With this configuration the problem is that the path length is limited to 128 characters.
    I installed Service Pack 4 for Windows 2000,
    restarted my computer and everything is working fine and without any problems!
    Hope, that this solution is working for you as well! Good luck! "

    I checked my SP and found it to be 2, IIII-haaaa... then it hit me. I'm not running WIN 2000 any longer, I'm running XP. Back to square one.

  6. #6
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Are you running the SQL-2000 sp3a or later? I vaguely remember this problem from long ago, and it seems to me that it was fixed by sp3.

    -PatP

  7. #7
    Join Date
    Jul 2003
    Posts
    123
    I'm running XP as I wrote in the above post ;-)

  8. #8
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    He was asking about your database version, not the operating system.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  9. #9
    Join Date
    Jul 2003
    Posts
    123
    I haven't got hold of my DBA yet...

    But select @@version shows this information:

    Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

    So it should be running SP4.

  10. #10
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    No, what you're seeing is the XP Service Pack 4. Build 760 means that you are running SQL sp3a, but that should be good enough to fix the problem that I remembered.

    -PatP

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •