May 19, 2010 at 9:13 am
I have a 3rd party app which I have to support. When doing some performance monitoring I noticed they never fully qualify their sql. So instead of
select field from database.schema.table I just see
select field from table.
All of their sql is like this, isn't this adding extra overhead. Kind of silly to bother with breaking objects into schemas if you are not going to reference them?
May 19, 2010 at 9:44 am
To be honest it probably depends when the application was written and for what version of SQL Server.
I have found that alot of 3rd party application developers have been lazy and not updated their code to use fully qualififed names as the the version of SQL Server have come along.
May 19, 2010 at 10:48 am
It adds overhead, but it's pretty trivial. The accumulative effects aren't good, but you're unlikely to see any given query perform badly because of this.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 19, 2010 at 10:52 am
As the others have said, the overhead is pretty trivial.
The benefit in qualifying your objects is to ensure that the correct object is being accessed should you have multiple schemas.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
May 19, 2010 at 9:47 pm
There's a good explanation of the issues in the following Knowledge Base article:
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply