Home/ Questions/Q 320951
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T08:48:03+00:00

I am looking for a performant default policy for dealing with the .dbo prefix.

  • 0

I am looking for a performant default policy for dealing with the .dbo prefix.

I realize that the dbo. prefix is more than syntactic noise, however I got through the past 8 years of MS based development skipping typing the dbo. prefix and ignoring its function.

Apart from a performance issue with stored proc compile locks is there a downside to skipping typing “.dbo” in SQLqueries and stored procedures?

Further background: All my development is web middle-tier based with integrated security based on a middle tier service account.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    [dbo].[xxx]

    The SQL Server engine always parse the query into pieces, if you don’t use the prefix definitely it going search for object in similar name with different users before it uses [dbo]. I would suggest you follow the prefix mechanism not only to satisfy the best practices, also to avoid performance glitches and make the code scalable.

    I don’t know I answered your question, but these are just my knowledge share

    • 0