transferring stored procs from sql 2000 to 2k5

  • Thanks for any help or suggestions... much appreciated

    I am trying to transfer SP's but it seems to only move some and not all.. when i go from the SSIS in 2k5 it seems to only pull some of the procs. There are well over 150 sp's and i know there has to be a better way then what i am trying..any suggestions.

    Also have tried to go back from 2k and export over to the 2k5 machine the problem here is this seems to blow up towards the end with some error stating "objects are not defined"

    any suggestions.....

    DHeath

  • Have you tried scripting out the stored procedures in SQL 2000 and running the scripts to create them in SQL 2005? It's a few more steps than transferring with SSIS, but it's pretty reliable.

    Greg

    Greg

  • will give that a shot thanks..and i thought each NEW version we to make things easier 🙂 o well...

    DHeath

  • One thought...

    SQL Server 2005 handles stored procs differently than in 2000. Essentially 2K5 verifies dependencies at install time rather than at execute time (as 2000 did). So, if the tables / views / etc. that the stored proc uses don't exist or don't match the structure expected, you can't install the sp in 2K5. We ran into this issue on our first pass or two at migrating.

    Also, have you run upgrade advisor against the DB?

    (oh, alright, that's two thoughts...)

  • Thanks for the insight Pam... but i cant run an advisor simply because the migration is going across to 2 separate servers..one will remain 2k and the other will remain 2k5. So the upgrade advisor altho a wonderful idea cant be used. Currently trying to script off most that dont go over using the regular scripts due to the new verification process that you were mentioning.

    DHeath

  • ? Nothing you've said should stop you from running Upgrade Advisor. It's independent of a 2K5 install.

    Upgrade Advisor is designed to run on a 2K machine. Either that or you can run it on your 2K5 box and connect remotely to the 2K box. I've done both with no issues whatsoever.

    See the website for details:

    http://msdn2.microsoft.com/en-us/library/ms144256.aspx

  • Pam Brisjar (10/10/2007)


    Also, have you run upgrade advisor against the DB?

    Make that 2 votes for the use of upgrade advisor. It'll do syntactical checking you'd otherwise have to do by hand. It's not 100% but it's pretty good at picking up things that have changed between the versions. That'll tell you what you have to fix before converting.

    K. Brian Kelley
    @kbriankelley

Viewing 7 posts - 1 through 6 (of 6 total)

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