timeolz.blogg.se

You aren't connected to the database you think you are.The other possibilities are (in no particular order):

The only time a single probe will resolve the name is if the current user owns an object of the specified name and type. Name resolution slows down query execution as two probes must be made to resolve to the likely version of the object (that owned by 'dbo'). Recompilations cause compile locks to be taken out, blocking others from accessing the needed resource(s). This results in recompilation of the query/stored procedure, a performance hit. The unqualified reference is bound to the first match in the above sequence.Īs a general recommended practice, one should always qualify references to schema objects, for performance reasons:Īn unqualified reference may invalidate a cached execution plan for the stored procedure or query, since the schema to which the reference was bound may change depending on the credentials executing the stored procedure or query. Name resolution occurs by searching in the following sequence for an object of the appropriate type (table) with the specified name. When you have an unqualified reference to a schema object (such as a table) - one not qualified by schema name - the object reference must be resolved.

One is owned by the schema 'dbo' ( dbo.PerfDiag), and the other is owned by the default schema of the account used to connect to SQL Server (something like userid.PerfDiag). I suspect that you have two tables with the same name.