Performance

Is there any difference between:
executing 2 queries in the same database at the same time
or
Executing 2 queries in 2 different databases at the same time
The same conditions for the 2 databases (same query, tables, indexes).
The concrete question is: is there any performance advantages in spliting
one database into 2.
--
Thanks
Regards.
Josema"Josema" <Jestrade@.ocu.org> wrote in message
news:FA30EE5C-0959-456E-BDA6-080382700A51@.microsoft.com...
> Is there any difference between:
> executing 2 queries in the same database at the same time
> or
> Executing 2 queries in 2 different databases at the same time
> The same conditions for the 2 databases (same query, tables, indexes).
> The concrete question is: is there any performance advantages in spliting
> one database into 2.
"It depends."
On to many factors to really give a complete answer w/o knowing your schema,
your hardware, etc.
For example, if the dataset in DB 1 is cached, two queries against it will
be as fast as your memory can provide them. If you have it in two
databases, the chances both datasets will fit in memory drops which means
you increase your likelihood that you have to hit the disk which will
dramactically slow things down.
On the other hand, if both queries require a full table scan and you're
flooding your disk channel, putting the two databases on completely
different disk channels may improve throughput.
Generally though I'd say splitting a database into two pieces strictly for
performance reasons isn't going to help.
>
> --
> Thanks
> Regards.
> Josema