Post reply

Why Sql 2005 requires to prefix the Owner name with Object name?

  • February 13, 2009 at 7:32 am

    #126384

    Hi,

    I am currently in the process of migrating my SPs from Sql 2000 to Sql 2005. My Sql 2000 SP calls are currently running with out prefixing it's owner name (Exec Sp_name). How ever, if I try the same in Sql 2005, it throws error as 'Object doesn't exist' and works only when I prefix with Owner name (Exec Owner.Sp_name).

    Are there any changes in 2005 to insist Owner name perfixing while using any DB objects? I also heard like there is a new concept called Schema in 2005. Does that come into picture in my case?

    Thanks in advance,

    Suresh

    Regards,
    Suresh Arumugam

  • February 13, 2009 at 7:39 am

    #943591

    You shouldnt be calling Stored procs without the Object/Schema qualifier. It has performance impact. Be it 2000 or 2005.

    -Roy

  • February 13, 2009 at 7:52 am

    #943621

    Yeah, you're probably running into schema issues. If the schema defining the object is anything other than the default schema for the connection, you can't simply call the proc.

    ----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software

  • February 13, 2009 at 8:20 am

    #943650

    Thanks for the quick reply.

    I understand the importance of using schema along with object names. How ever, still trying to understand why it was working in Sql 2000 for me but not in Sql 2005.

    Thanks,

    Suresh

    Regards,
    Suresh Arumugam

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

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