Post reply

SQL Server 2005 upgrade changes column order of tables.

  • February 2, 2009 at 5:52 pm

    #206147

    I have a customer who performed an upgrade from SQL Server 2000 to SQL Server 2005. After doing so, they performed a PeopleTools upgrade. They have found that the column order on their custom tables have changed on the database. The PeopleTools upgrade would not affect the field order of custom records. And the column order does not affect the way the PeopleSoft application interacts with the table. It does however affect custom SQR's and imports that rely on a specific field order. Fixing the issue is easy. But determining the root cause of why the column has changed is my task at hand.

    Is there a known issue where after upgrading to SQL Server 2005 that the column order of tables changes.

    Thanks in advance,

    Rich

  • February 2, 2009 at 6:59 pm

    #936861

    rich.ramos (2/2/2009)

    The PeopleTools upgrade would not affect the field order of custom records. And the column order does not affect the way the PeopleSoft application interacts with the table.

    Oh, I wouldn't bet on that even if they say it won't. Went through that same scenario a couple of years back with a different 3rd party vendor and it was the "migration software" the vendor had built that put the screws to things. We were lucky... we knew it was them because they changed all of the custom column names to all upper case.

    --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)

  • February 2, 2009 at 7:10 pm

    #936868

    Jeff Moden (2/2/2009)

    rich.ramos (2/2/2009)

    The PeopleTools upgrade would not affect the field order of custom records. And the column order does not affect the way the PeopleSoft application interacts with the table.

    Oh, I wouldn't bet on that even if they say it won't. Went through that same scenario a couple of years back with a different 3rd party vendor and it was the "migration software" the vendor had built that put the screws to things. We were lucky... we knew it was them because they changed all of the custom column names to all upper case.

    And I wouldn't put the blame on PeopleSoft directly either. I am not the PeopleSoft Administrator where I work, but I do provide the SQL Server support to our PeopleSoft team. We had no problems upgrading from SQL Server 2000 to SQL Server 2005 in regards to column order changing in any of the custom tables or processes in either our Finance or HR systems. If we had, I know I would have heard about it.

    I'll pass this thread on to our PeopleSoft Admin. I'm sure she'll have some questions before trying to help out, such as what modules you are using, what version of the modules you are on (our Finance is 8.9 and HR is 9.0)., what version of PeopleTools you are using, and that is just a start.

  • February 3, 2009 at 11:22 am

    #937391

    This is no longer an issue. The customer just informed me that the field order in their SQL 2000 database is the same as what they are seeing in 2005.

    Thanks to everyone who replied.

  • February 4, 2009 at 8:40 pm

    #938575

    rich.ramos (2/3/2009)

    This is no longer an issue. The customer just informed me that the field order in their SQL 2000 database is the same as what they are seeing in 2005.

    Thanks to everyone who replied.

    Curious.... it that's true, why did they think it had?

    --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)

Viewing 5 posts - 1 through 5 (of 5 total)

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