MsQuery

I've heard when using MSQuery on the client side, the where statement
gets processes at the client side, thus many records come across that
are not necessary. Is that true?
If so, would Query Analyzer be a better choice? We are trying to run
queries against our server (we are not in IT) and we have been getting
CBSIO errors.
ThanksCBSIO?
It does seem fine. I ran it from the OFFICE11 folder for Office 2003 and it
sent the where clause to the server. It might do it on the client if you
have disparate sources, but I would doubt it on the same server.
Query Analyzer would be better, but it does not have the joining tools that
MSQuery does. As long as you get the performance you desire, it should be
fine.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
<bdaoust@.yahoo.com> wrote in message
news:1126273874.851824.292530@.g47g2000cwa.googlegroups.com...
> I've heard when using MSQuery on the client side, the where statement
> gets processes at the client side, thus many records come across that
> are not necessary. Is that true?
> If so, would Query Analyzer be a better choice? We are trying to run
> queries against our server (we are not in IT) and we have been getting
> CBSIO errors.
> Thanks
>|||Louis,
Thank you for the reply. When you say joining tools, what are you
referring to?
I guess I wouldnt miss them much since I dont even know what they are!
:)
Also, how can you confirm that the where clause was sent to the server?
Thank you.|||> Thank you for the reply. When you say joining tools, what are you
> referring to?
The query by example stuff that MSQuery has where you can pick the tables,
and it joins them for you, etc. If you don't need this and you are writing
SQL Statements in text, then query analyzer is the way to go anyhow.

> Also, how can you confirm that the where clause was sent to the server?
I used profiler and watched the statements being sent to the server.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
"BerkshireGuy" <bdaoust@.yahoo.com> wrote in message
news:1126281216.691598.305900@.g47g2000cwa.googlegroups.com...
> Louis,
> Thank you for the reply. When you say joining tools, what are you
> referring to?
> I guess I wouldnt miss them much since I dont even know what they are!
> :)
> Also, how can you confirm that the where clause was sent to the server?
>
> Thank you.
>|||Aww I see, there is no design grid.
I am use to writing the SQL, so it will work for me. Hopefully IT is
willing to install it on my machine.
Thanks for the help.sql

MSDTC resource in a Cluster

I've read and heard some conflicting information about the best method for
setting up a MSDTC resource in a cluster. I am running MSSQL 2000 SP3a and
Windows 2003. 2 node cluster with currently only once instance of MSSQL
with a great chance of growing.
A few questions I have:
Should the resource be in the cluster group or the virtual server group?
What else does it need, ip address, name...?
If it's not yet being used, is it safe to have it on the quorum drive
(currently 1GB RAID1)?
Has anyone found a white paper specific to Win2k3, MSSQL2k and MSDTC?
Thanks,
Joseph
Hi,
I've found this paper
http://support.microsoft.com/default...b;en-us;301600
It suggests to put MSDTC in its own group with its storage resource(disk).
On other hand if that is not possible you can put it in a group with disk.
Anyway I would mess with quorum drive, so I would put it in a Virtual Server
group.
Danijel
"Joseph" <Joseph@.discussions.microsoft.com> wrote in message
news:OEv$n4M%23EHA.2552@.TK2MSFTNGP09.phx.gbl...
> I've read and heard some conflicting information about the best method for
> setting up a MSDTC resource in a cluster. I am running MSSQL 2000 SP3a
> and
> Windows 2003. 2 node cluster with currently only once instance of MSSQL
> with a great chance of growing.
> A few questions I have:
> Should the resource be in the cluster group or the virtual server group?
> What else does it need, ip address, name...?
> If it's not yet being used, is it safe to have it on the quorum drive
> (currently 1GB RAID1)?
> Has anyone found a white paper specific to Win2k3, MSSQL2k and MSDTC?
> Thanks,
> Joseph
>
|||The official best practice is "put MSDTC in its own group" but to do that
you will need an extra disk, Network Name and IP Address.
Unless you know you will be hitting MSDTC hard, like in a BizTalk
environment for example then leave it in the cluster group. In the event of
an MSDTC failure the Cluster Group will failover to the passive node. The
only "outage" will be for admin's connected to the Virtual Cluster Name in
Cluster Administrator as the resources are re-started on the new node. It
will not affect any other groups.
Alternatively, if MSDTC was in the SQL Group then a failure would cause a
SQL Server outage. If your application is entirely dependant on MSDTC, this
might be fine but its more likely that you wouldn't want that to happen.
You can set MSDTC to not affect the group but then you don't have the
benefit of failover.
In summary, leave MSDTC in the Cluster Group. It makes sense and we support
it
Christian Bolton
Microsoft
"Danijel Novak" <danijel.novak@.snt.si> wrote in message
news:nVfFd.8296$F6.1420730@.news.siol.net...
> Hi,
> I've found this paper
> http://support.microsoft.com/default...b;en-us;301600
> It suggests to put MSDTC in its own group with its storage resource(disk).
> On other hand if that is not possible you can put it in a group with disk.
> Anyway I would mess with quorum drive, so I would put it in a Virtual
> Server group.
> Danijel
> "Joseph" <Joseph@.discussions.microsoft.com> wrote in message
> news:OEv$n4M%23EHA.2552@.TK2MSFTNGP09.phx.gbl...
>