Starting Migration from SQL Server 2000

  • I have read the help files and technical articals..and don't seen anyting that addresses the following..

    One of the databases we are moving has stored procedures that makes liberal use of the sys tables(syscomments, sysobjects..etc) It's my understanding that SQL Server 2005 now makes use of the [INFORMATION_SCEMA} views. Has anyone dealt with this ?

    Anyone have any other pointers as far as migration goes ?

    TIA

    MJKulangara


    Mathew J Kulangara
    sqladventures.blogspot.com

  • SQL2000 also makes use of the INFORMATION_SCHEMA views. You can see the definitive list within the MASTER database.

    Some of the system tables have changed in SQL2005 so I would look very closely at what it is you do with them. INFORMATION_SCHEMA views aren't the be all and end all.

    In the days of SQL 6.5 you would do a SELECT on sysobjects where type='P' and name ="YourProc" for procedures. You can still do this in subsequent versions but in SQL 2000 the approved WHERE clause was WHERE Id=Object_Id('dbo.YourProc') AND OBJECTPROPERTY(id,'IsProcedure')=1

  • Like many of us, you'll get in troubles when using system-objects other than INFORMATION_SCHEMA.

    Make the effort to adapt to INFORMATION_SCHEMA-use.

    You can stil use the sys.sysobjects stuff. So MS did an effort to be downward compatible on that, but you'll have to use schema SYS in stead of dbo.

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • Yep, its always advicable to use InformationSchema Views, but as you said your code refers to syscomments , sysobjects etc.

    You can now use sys.syscomments, sys.sysobjects to make it compatable with SQL Server 2005.






    Regards,
    Sudheer 

    My Blog

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

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