Outside of security considerations, are there any performance issues
that should be addressed when using cross database queries on the same
server?Not for SELECT. There is a slight overhead for cross-database transactions b
ecause they involve
several databases transaction logs so an internal 2-phase commit protocol is
used.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Paul Sinclair" <paul.sinclair@.gmails.com> wrote in message
news:enV%23GO1UGHA.4944@.TK2MSFTNGP10.phx.gbl...
> Outside of security considerations, are there any performance issues that
should be addressed when
> using cross database queries on the same server?|||Tibor Karaszi wrote:
> Not for SELECT. There is a slight overhead for cross-database
> transactions because they involve several databases transaction logs so
> an internal 2-phase commit protocol is used.
>
Great, that's what I was seeing in my execution plans against recreated
objects in the same database vs objects in another database - but wasn't
sure if I was missing something or not. Thanks again for the help.
Paul
Tuesday, February 14, 2012
Cross Database Queries in SQL Server 2000
Labels:
addressed,
considerations,
cross,
database,
issuesthat,
microsoft,
mysql,
oracle,
outside,
performance,
queries,
security,
server,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment