MS-SQL 2000 SP2

I have a client that has noticed a "slowness in reads" during a performance
benchmark. They mentioned something about a MS-SQL "fix" to improve read
performance. Is there such a fix or patch? I know this is real vague but
it's all the information I have.All publicly available "fixes" are available through the service packs.
Microsoft Support may issue individual patches for specific problems to
resolve support cases, however these are only available after opening a case
with tech support or by specific reference in certain knowledgebase
articles. Without knowing exactly what "fix" your client is referencing,
its hard to provide additional information. I'd double check with them to
get some additional details.
--
--Brian
(Please reply to the newsgroups only.)
"Jo Ratner" <jo_ratner@.NOSPAMyahoo.com> wrote in message
news:riURb.466$jH6.359@.newsread1.news.atl.earthlink.net...
>I have a client that has noticed a "slowness in reads" during a performance
> benchmark. They mentioned something about a MS-SQL "fix" to improve read
> performance. Is there such a fix or patch? I know this is real vague but
> it's all the information I have.
>|||Hi
Although I dont know of any "fix" there are alot of things you can do to
improve reads.. ranging from changing SQL, adding/updating
indexes/statistics to additional hardware or a change of O/S. Windows 2003
has a improved file system that in turn improves SQL Server performance. It
could even be the way the tests are being run.
Without analysing the problem you may not know exacly where the problem(s)
may occur.
The latest service pack is 3a, and, as this contains several security fixes
it would be sensible to use this. It would be reasonable to assume any
system being implemented would be atleast at this level, a system on Service
pack 2 may not be representative.
John
"Jo Ratner" <jo_ratner@.NOSPAMyahoo.com> wrote in message
news:riURb.466$jH6.359@.newsread1.news.atl.earthlink.net...
> I have a client that has noticed a "slowness in reads" during a
performance
> benchmark. They mentioned something about a MS-SQL "fix" to improve read
> performance. Is there such a fix or patch? I know this is real vague but
> it's all the information I have.
>|||It was an invalid benchmark test...
Thanks!
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:bvft13$cal$1@.sparta.btinternet.com...
> Hi
> Although I dont know of any "fix" there are alot of things you can do to
> improve reads.. ranging from changing SQL, adding/updating
> indexes/statistics to additional hardware or a change of O/S. Windows 2003
> has a improved file system that in turn improves SQL Server performance.
It
> could even be the way the tests are being run.
> Without analysing the problem you may not know exacly where the problem(s)
> may occur.
> The latest service pack is 3a, and, as this contains several security
fixes
> it would be sensible to use this. It would be reasonable to assume any
> system being implemented would be atleast at this level, a system on
Service
> pack 2 may not be representative.
> John
> "Jo Ratner" <jo_ratner@.NOSPAMyahoo.com> wrote in message
> news:riURb.466$jH6.359@.newsread1.news.atl.earthlink.net...
> > I have a client that has noticed a "slowness in reads" during a
> performance
> > benchmark. They mentioned something about a MS-SQL "fix" to improve
read
> > performance. Is there such a fix or patch? I know this is real vague
but
> > it's all the information I have.
> >
> >
>

MS-SQL 2000 SP2

I have a client that has noticed a "slowness in reads" during a performance
benchmark. They mentioned something about a MS-SQL "fix" to improve read
performance. Is there such a fix or patch? I know this is real vague but
it's all the information I have.All publicly available "fixes" are available through the service packs.
Microsoft Support may issue individual patches for specific problems to
resolve support cases, however these are only available after opening a case
with tech support or by specific reference in certain knowledgebase
articles. Without knowing exactly what "fix" your client is referencing,
its hard to provide additional information. I'd double check with them to
get some additional details.
--Brian
(Please reply to the newsgroups only.)
"Jo Ratner" <jo_ratner@.NOSPAMyahoo.com> wrote in message
news:riURb.466$jH6.359@.newsread1.news.atl.earthlink.net...

quote:

---

>I have a client that has noticed a "slowness in reads" during a performance
> benchmark. They mentioned something about a MS-SQL "fix" to improve read
> performance. Is there such a fix or patch? I know this is real vague but
> it's all the information I have.
>

---

|||Hi
Although I dont know of any "fix" there are alot of things you can do to
improve reads.. ranging from changing SQL, adding/updating
indexes/statistics to additional hardware or a change of O/S. Windows 2003
has a improved file system that in turn improves SQL Server performance. It
could even be the way the tests are being run.
Without analysing the problem you may not know exacly where the problem(s)
may occur.
The latest service pack is 3a, and, as this contains several security fixes
it would be sensible to use this. It would be reasonable to assume any
system being implemented would be atleast at this level, a system on Service
pack 2 may not be representative.
John
"Jo Ratner" <jo_ratner@.NOSPAMyahoo.com> wrote in message
news:riURb.466$jH6.359@.newsread1.news.atl.earthlink.net...

quote:

---

> I have a client that has noticed a "slowness in reads" during a

---

performance

quote:

---

> benchmark. They mentioned something about a MS-SQL "fix" to improve read
> performance. Is there such a fix or patch? I know this is real vague but
> it's all the information I have.
>

---

|||It was an invalid benchmark test...
Thanks!
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:bvft13$cal$1@.sparta.btinternet.com...

quote:

---

> Hi
> Although I dont know of any "fix" there are alot of things you can do to
> improve reads.. ranging from changing SQL, adding/updating
> indexes/statistics to additional hardware or a change of O/S. Windows 2003
> has a improved file system that in turn improves SQL Server performance.

---

It

quote:

---

> could even be the way the tests are being run.
> Without analysing the problem you may not know exacly where the problem(s)
> may occur.
> The latest service pack is 3a, and, as this contains several security

---

fixes

quote:

---

> it would be sensible to use this. It would be reasonable to assume any
> system being implemented would be atleast at this level, a system on

---

Service

quote:

---

> pack 2 may not be representative.
> John
> "Jo Ratner" <jo_ratner@.NOSPAMyahoo.com> wrote in message
> news:riURb.466$jH6.359@.newsread1.news.atl.earthlink.net...
> performance
read[QUOTE]
but[QUOTE]
>

---

MSSQL 2000 Restore - can I roll back Transaction Logs

Not sure if this is possible, but a client wants to now if we can use a
backup we made on 2/24
and then pull transaction out of the database using the daily
transaction log backups to get the database to be an effective copy of
what it looked like on 2/13/06.
We have all the daily transaction logs up to today and the 2/24/06 is
the latest backup we have.
Any help would be greatly appreciated.
RegardsNo. You need a full backup as a starting point BEFORE the desired target
date. Transaction logs are write-ahead, I.E. they log new data, not old.
Logs can thus be rolled forward but not backwards.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<raekwon2112@.gmail.com> wrote in message
news:1143669384.250415.233980@.z34g2000cwc.googlegroups.com...
> Not sure if this is possible, but a client wants to now if we can use a
> backup we made on 2/24
> and then pull transaction out of the database using the daily
> transaction log backups to get the database to be an effective copy of
> what it looked like on 2/13/06.
> We have all the daily transaction logs up to today and the 2/24/06 is
> the latest backup we have.
> Any help would be greatly appreciated.
> Regards
>|||Technical correction for the fussy. The logs do contain roll-back
information, but the restore/recovery process is a forward-only one.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:upWIc03UGHA.1572@.tk2msftngp13.phx.gbl...
> No. You need a full backup as a starting point BEFORE the desired target
> date. Transaction logs are write-ahead, I.E. they log new data, not old.
> Logs can thus be rolled forward but not backwards.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> <raekwon2112@.gmail.com> wrote in message
> news:1143669384.250415.233980@.z34g2000cwc.googlegroups.com...
>> Not sure if this is possible, but a client wants to now if we can use a
>> backup we made on 2/24
>> and then pull transaction out of the database using the daily
>> transaction log backups to get the database to be an effective copy of
>> what it looked like on 2/13/06.
>> We have all the daily transaction logs up to today and the 2/24/06 is
>> the latest backup we have.
>> Any help would be greatly appreciated.
>> Regards
>|||<raekwon2112@.gmail.com> wrote in message
news:1143669384.250415.233980@.z34g2000cwc.googlegroups.com...
> Not sure if this is possible, but a client wants to now if we can use a
> backup we made on 2/24
> and then pull transaction out of the database using the daily
> transaction log backups to get the database to be an effective copy of
> what it looked like on 2/13/06.
> We have all the daily transaction logs up to today and the 2/24/06 is
> the latest backup we have.
> Any help would be greatly appreciated.
> Regards
>
See the topic "How to Restore to a Point In Time" in Books Online.
You need to restore the latest full backup dated BEFORE 2/13/06 with NO
RECOVERY option, followed by the sequence of transaction log backups
covering that date.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

MSSQL 2000 Restore - can I roll back Transaction Logs

Not sure if this is possible, but a client wants to now if we can use a
backup we made on 2/24
and then pull transaction out of the database using the daily
transaction log backups to get the database to be an effective copy of
what it looked like on 2/13/06.
We have all the daily transaction logs up to today and the 2/24/06 is
the latest backup we have.
Any help would be greatly appreciated.
Regards
No. You need a full backup as a starting point BEFORE the desired target
date. Transaction logs are write-ahead, I.E. they log new data, not old.
Logs can thus be rolled forward but not backwards.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<raekwon2112@.gmail.com> wrote in message
news:1143669384.250415.233980@.z34g2000cwc.googlegr oups.com...
> Not sure if this is possible, but a client wants to now if we can use a
> backup we made on 2/24
> and then pull transaction out of the database using the daily
> transaction log backups to get the database to be an effective copy of
> what it looked like on 2/13/06.
> We have all the daily transaction logs up to today and the 2/24/06 is
> the latest backup we have.
> Any help would be greatly appreciated.
> Regards
>
|||Technical correction for the fussy. The logs do contain roll-back
information, but the restore/recovery process is a forward-only one.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:upWIc03UGHA.1572@.tk2msftngp13.phx.gbl...
> No. You need a full backup as a starting point BEFORE the desired target
> date. Transaction logs are write-ahead, I.E. they log new data, not old.
> Logs can thus be rolled forward but not backwards.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> <raekwon2112@.gmail.com> wrote in message
> news:1143669384.250415.233980@.z34g2000cwc.googlegr oups.com...
>
|||<raekwon2112@.gmail.com> wrote in message
news:1143669384.250415.233980@.z34g2000cwc.googlegr oups.com...
> Not sure if this is possible, but a client wants to now if we can use a
> backup we made on 2/24
> and then pull transaction out of the database using the daily
> transaction log backups to get the database to be an effective copy of
> what it looked like on 2/13/06.
> We have all the daily transaction logs up to today and the 2/24/06 is
> the latest backup we have.
> Any help would be greatly appreciated.
> Regards
>
See the topic "How to Restore to a Point In Time" in Books Online.
You need to restore the latest full backup dated BEFORE 2/13/06 with NO
RECOVERY option, followed by the sequence of transaction log backups
covering that date.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx

MSSQL 2000 Restore - can I roll back Transaction Logs

Not sure if this is possible, but a client wants to now if we can use a
backup we made on 2/24
and then pull transaction out of the database using the daily
transaction log backups to get the database to be an effective copy of
what it looked like on 2/13/06.
We have all the daily transaction logs up to today and the 2/24/06 is
the latest backup we have.
Any help would be greatly appreciated.
RegardsNo. You need a full backup as a starting point BEFORE the desired target
date. Transaction logs are write-ahead, I.E. they log new data, not old.
Logs can thus be rolled forward but not backwards.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<raekwon2112@.gmail.com> wrote in message
news:1143669384.250415.233980@.z34g2000cwc.googlegroups.com...
> Not sure if this is possible, but a client wants to now if we can use a
> backup we made on 2/24
> and then pull transaction out of the database using the daily
> transaction log backups to get the database to be an effective copy of
> what it looked like on 2/13/06.
> We have all the daily transaction logs up to today and the 2/24/06 is
> the latest backup we have.
> Any help would be greatly appreciated.
> Regards
>|||Technical correction for the fussy. The logs do contain roll-back
information, but the restore/recovery process is a forward-only one.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:upWIc03UGHA.1572@.tk2msftngp13.phx.gbl...
> No. You need a full backup as a starting point BEFORE the desired target
> date. Transaction logs are write-ahead, I.E. they log new data, not old.
> Logs can thus be rolled forward but not backwards.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> <raekwon2112@.gmail.com> wrote in message
> news:1143669384.250415.233980@.z34g2000cwc.googlegroups.com...
>|||<raekwon2112@.gmail.com> wrote in message
news:1143669384.250415.233980@.z34g2000cwc.googlegroups.com...
> Not sure if this is possible, but a client wants to now if we can use a
> backup we made on 2/24
> and then pull transaction out of the database using the daily
> transaction log backups to get the database to be an effective copy of
> what it looked like on 2/13/06.
> We have all the daily transaction logs up to today and the 2/24/06 is
> the latest backup we have.
> Any help would be greatly appreciated.
> Regards
>
See the topic "How to Restore to a Point In Time" in Books Online.
You need to restore the latest full backup dated BEFORE 2/13/06 with NO
RECOVERY option, followed by the sequence of transaction log backups
covering that date.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

MSSearch.exe error window: "Tracer"

My company has a client using SQLServer 2000 SP3a.
Every so often (approx. once a week), the full-text indexing will fail on
one of our database tables. We are unsure why, but have noticed some rather
bizarre behavior associated with this failure. (Normally, we restart the
MSSearch service and everything works again.)
Just today, the client called to tell us it didn't work. So, using
LogMeIn.com, I controlled their server computer to see what was going on.
Immediately I noticed a messagebox window with a title of "Tracer" and text
of "Release products should NOT call tracer!". The only button was "OK".
I didn't know for sure where this message was coming from, so I used
SysInternals' Process Explorer to list the processes and their window titles.
Lo and behold, MSSearch.exe was the process tied to "Tracer".
Obviously, this is a SQL Server bug, but I've not found reference to it in
any online searches. Has anyone seen this? Is it fixable by upgrading to
SP4 (this client is still using NT4, though).
Thanks for any information.
John,
Basic troubleshooting of SQL Server 2000 and MSSearch is somewhat of a black
art (as I can attest to), but the first place you should look for
information on what is causing the full-text indexing failure is the
server's Application event log as this is the only place where errors,
warning and information events are recorded for the MSSearch service. Look
for all related "Microsoft Search" or MssCi source events (errors, warning
and information) near the time of the failure. This will be the best source
of info as to what is causing the problem.
While I've never have used LogMeIn.com, I have known Microsoft to attach
debuggers to both SQL Server and the MSSearch.exe to identify bugs. If you
believe this to be a bug, then I'd highly recommend that you open a support
case with Microsoft PSS SQL Server support and get this resolved for your
client.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"John" <John@.discussions.microsoft.com> wrote in message
news:FAE1B226-FF90-41EC-9465-575285E412FF@.microsoft.com...
> My company has a client using SQLServer 2000 SP3a.
> Every so often (approx. once a week), the full-text indexing will fail on
> one of our database tables. We are unsure why, but have noticed some
> rather
> bizarre behavior associated with this failure. (Normally, we restart the
> MSSearch service and everything works again.)
> Just today, the client called to tell us it didn't work. So, using
> LogMeIn.com, I controlled their server computer to see what was going on.
> Immediately I noticed a messagebox window with a title of "Tracer" and
> text
> of "Release products should NOT call tracer!". The only button was "OK".
> I didn't know for sure where this message was coming from, so I used
> SysInternals' Process Explorer to list the processes and their window
> titles.
> Lo and behold, MSSearch.exe was the process tied to "Tracer".
> Obviously, this is a SQL Server bug, but I've not found reference to it in
> any online searches. Has anyone seen this? Is it fixable by upgrading to
> SP4 (this client is still using NT4, though).
> Thanks for any information.
|||We have the same thing happening sparodically at one of clients as well, The Tracer message pops up, the fulltext search quits working, if we restart mssearch it starts working again.
Only real difference I see, is that our client is running Small Bussiness Server, (Windows 2000, SP4) and I was blaming it on that, since they have all kinds of strange limitations they try to put in it.
I am switching it to update at 4AM each day instead of the continuas background update, and see if that makes a difference.
It only causes trouble when indexing 1 of the two tables we are indexing. The table has 550,000 items and a 5303 MB catalog, with a key count 6 million.
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

MSRS Java Client

We tried to develop a MSRS Java Client to communicate with the MSRS server
via web services. Because of integrated windows authentication, we
encountered an access denial error. Has anyone encountered this problem and
know how to embed windows security in the Java client. By the way, I used
Apache Axis to create client stub classes from a WSDL file. I obtained the
WSDL file from the MSRS server directly.
Thanks,
JamesJames, I am trying to do exactly what you are describing and have run into
the same problem. Did you ever discover a solution?
Thanks!
"James" wrote:
> We tried to develop a MSRS Java Client to communicate with the MSRS server
> via web services. Because of integrated windows authentication, we
> encountered an access denial error. Has anyone encountered this problem and
> know how to embed windows security in the Java client. By the way, I used
> Apache Axis to create client stub classes from a WSDL file. I obtained the
> WSDL file from the MSRS server directly.
> Thanks,
> James|||Josh, James, I'm having this problem as well. Was there a solution?
"Josh Hensley" wrote:
> James, I am trying to do exactly what you are describing and have run into
> the same problem. Did you ever discover a solution?
> Thanks!
> "James" wrote:
> > We tried to develop a MSRS Java Client to communicate with the MSRS server
> > via web services. Because of integrated windows authentication, we
> > encountered an access denial error. Has anyone encountered this problem and
> > know how to embed windows security in the Java client. By the way, I used
> > Apache Axis to create client stub classes from a WSDL file. I obtained the
> > WSDL file from the MSRS server directly.
> >
> > Thanks,
> >
> > James|||Hey LT,
I did find a solution, but forgot to come back and mention it here.
The problem comes from the fact that we need to call the Render method
without specifying some optional parameters (like historyID). When you call
a Web Service API method from Java and leave out an optional parameter, the
SOAP message that is generated by AXIS can either exclude the tag for that
missing parameter or include the tag with a special attribute saying it's not
being used (xsi:nil="true"). The default for behavior for AXIS is to send
the tag with the special attribute but apparently Microsoft Reporting
Services doesn't want the tag sent at all. So you have to modify AXIS to
satisfy Reporting Services and stop sending tags for arguments that aren't
specified.
A much more detailed explanation is in this article written by a fella from
France. (You will have to register on their site to read the article)
http://www.sqlreportingservices.net/Tools/1996.aspx
Good luck!
"LT" wrote:
> Josh, James, I'm having this problem as well. Was there a solution?
> "Josh Hensley" wrote:
> > James, I am trying to do exactly what you are describing and have run into
> > the same problem. Did you ever discover a solution?
> >
> > Thanks!
> >
> > "James" wrote:
> >
> > > We tried to develop a MSRS Java Client to communicate with the MSRS server
> > > via web services. Because of integrated windows authentication, we
> > > encountered an access denial error. Has anyone encountered this problem and
> > > know how to embed windows security in the Java client. By the way, I used
> > > Apache Axis to create client stub classes from a WSDL file. I obtained the
> > > WSDL file from the MSRS server directly.
> > >
> > > Thanks,
> > >
> > > Jamessql

MSRS Developer Edition on MS SQL 2000 STD

Hello,
I have a client installation I need to load Reporting Services on but
the disk they put into the server is Developer edition rather than
standard. This is a production server. Are their any potential issues I
might encounter?
Any information is greatly appreciated.
Thanks,
HLittle things like licensing issues a concern?
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1164072012.870727.39050@.m73g2000cwd.googlegroups.com...
> Hello,
> I have a client installation I need to load Reporting Services on but
> the disk they put into the server is Developer edition rather than
> standard. This is a production server. Are their any potential issues I
> might encounter?
> Any information is greatly appreciated.
> Thanks,
> H
>

MSRS Developer Edition on MS SQL 2000 STD

Hello,
I have a client installation I need to load Reporting Services on but
the disk they put into the server is Developer edition rather than
standard. This is a production server. Are their any potential issues I
might encounter?
Any information is greatly appreciated.
Thanks,
H
Little things like licensing issues a concern?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1164072012.870727.39050@.m73g2000cwd.googlegro ups.com...
> Hello,
> I have a client installation I need to load Reporting Services on but
> the disk they put into the server is Developer edition rather than
> standard. This is a production server. Are their any potential issues I
> might encounter?
> Any information is greatly appreciated.
> Thanks,
> H
>

MSRS Developer Edition on MS SQL 2000 STD

Hello,
I have a client installation I need to load Reporting Services on but
the disk they put into the server is Developer edition rather than
standard. This is a production server. Are their any potential issues I
might encounter?
Any information is greatly appreciated.
Thanks,
HLittle things like licensing issues a concern?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1164072012.870727.39050@.m73g2000cwd.googlegroups.com...
> Hello,
> I have a client installation I need to load Reporting Services on but
> the disk they put into the server is Developer edition rather than
> standard. This is a production server. Are their any potential issues I
> might encounter?
> Any information is greatly appreciated.
> Thanks,
> H
>

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

msi push install upgrade

Is it possible to upgrade about 80 clients from SQL 7 client to SQL 2000
client automatically using group policy push and msi technology?
Aswered in .clients "Subject: SQL 7 to 2K client upgrade"
"Dex Dexter" wrote:

> Is it possible to upgrade about 80 clients from SQL 7 client to SQL 2000
> client automatically using group policy push and msi technology?

MSDTC on server <ServerName> is unvailable

Hi,
I have an issue when a client tries to connect to an
application, he gets the error message saying:
"MSDTC on server <ServerName> is unvailable"
for now, we are using two methods to work around the
problem:
- uninstall and re-install the MSDTC service on the server
- rebbot the server
Can anyone help please?
Verify that you have Netbios Name Resolution working in both directions.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

MSDTC on server <ServerName> is unvailable

Hi,
I have an issue when a client tries to connect to an
application, he gets the error message saying:
"MSDTC on server <ServerName> is unvailable"
for now, we are using two methods to work around the
problem:
- uninstall and re-install the MSDTC service on the server
- rebbot the server
Can anyone help please?Verify that you have Netbios Name Resolution working in both directions.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.