query from mssql to sybase sucks

Hi,

I got a big problem. I try to run a query on ms query analyzer or my .net-app, but in both cause, it wouldn't work. when i run the query in ms query analyzer it returns me this error-message:

Der aktuelle Zeilenwert der [verkauf_online]..[hs].[std_ftext].text-Spalte konnte nicht vom OLE DB-Provider 'MSDASQL' gelesen werden.
[OLE/DB provider returned message: Die angeforderte Konvertierung wird nicht untersttzt.]
OLE DB-Fehlertrace [OLE/DB Provider 'MSDASQL' IRowset::GetData returned 0x80040e1d].

sorry, its in german, i know but the most important fact is, that a conversion failed. i tried to read a text-field from a sybase asa-8-database which is linked with a ms sql-server 2000. I tried to find out more about the error-messe an the error-code (x80040e1d) but i couldn't find anything helpful.

Now, I just hope some of you can maybe help me.What I would probably do to avoid such conversion errors would be to make a view in Sybase which has all columns as varchar( or equivalent in sybase) and then query this view.|||:S thanks very much, but...

...I am not the dba from the sybase db, just the guy who should extract some data from it.

Another way is a odbc-connection in vs.net but the i got 2 db-connections, also 2 times more to do, 2 times more problems, etc. you know what i mean...

Carsten

Query execution time problem

We are executing following query from query analyzer,
SELECT PD_ID, PD_DATA FROM TBL_PROJECT_DETAILS
[Table Strcuture => id int, data varchar(500)]
This table contains 45000 records.
When this query is executed from Query Analyzer locally on the database
server, output is returned in 30 seconds.
However, when the query is executed from Query Analyzer installed on
application server it takes 110 seconds.
Execution plan is same both times. CPU, reads are identical for both
executions. However there is big difference between the execution times.
Also, both database server and application server in same VLAN and direct
network connectivity is available without any interim hops.
Any kind of help or suggestion giving insight into this aspect is welcomed.
Thanks in advance for all the inputs.pvv30 (pvv30@.discussions.microsoft.com) writes:
> We are executing following query from query analyzer,
> SELECT PD_ID, PD_DATA FROM TBL_PROJECT_DETAILS
> [Table Strcuture => id int, data varchar(500)]
> This table contains 45000 records.
> When this query is executed from Query Analyzer locally on the database
> server, output is returned in 30 seconds.
> However, when the query is executed from Query Analyzer installed on
> application server it takes 110 seconds.
> Execution plan is same both times. CPU, reads are identical for both
> executions. However there is big difference between the execution times.
> Also, both database server and application server in same VLAN and direct
> network connectivity is available without any interim hops.
The most obvious guess is that network latency matters. It may be a good
VLAN, but on the database server the connection is over shared memory
so it's not unreasonable that it takes more time to get it over the
wire.
Another thing to consider is the CPU power on the two machines.
Particularly if you run the output in text mode in QA, this could
matter.
Then again, I don't really see the point in measuring how long time
takes to receive 45000 rows in Query Analyzer. The tool is not really
intended for that.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Query Analyzer was used just to indicate a client application.
We are also monitoring the SQL calls using Profiler which is also giving us
the same output.
Also, the two boxes are of same configuration in terms of RAM & CPU.
You mentioned about connection being created in shared memory. Can anyone
please explain it in more detail as to how will it impact the query
performance? It might help us in understanding the problem better and work
towards a solution.
This time we enabled client statistics option in Query Analyzer. The
difference between two queries is for following attributes,
1. "Cumulative wait time on server replies" 38045 [for 110 sec execution
(app server)] v/s 81 [for 30 sec execution (locally from database server)]
2. "Number of bytes received" recieved is slightly more for query executed
from app server compared to database server
What does "Cumulative wait time on server replies" stats represents and how
to interpret it?
Thanks in advance for the responses.
"Erland Sommarskog" wrote:

> pvv30 (pvv30@.discussions.microsoft.com) writes:
> The most obvious guess is that network latency matters. It may be a good
> VLAN, but on the database server the connection is over shared memory
> so it's not unreasonable that it takes more time to get it over the
> wire.
> Another thing to consider is the CPU power on the two machines.
> Particularly if you run the output in text mode in QA, this could
> matter.
> Then again, I don't really see the point in measuring how long time
> takes to receive 45000 rows in Query Analyzer. The tool is not really
> intended for that.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx
>|||pvv30 (pvv30@.discussions.microsoft.com) writes:
> Query Analyzer was used just to indicate a client application.
I don't think it's a good benchmark for that purpose, since QA does a lot
of things a client app wouldn't do. You are better of writing a client
application that just receives the dataset. Particularly, you should use
the client API you plan to use in your client application.

> You mentioned about connection being created in shared memory. Can anyone
> please explain it in more detail as to how will it impact the query
> performance? It might help us in understanding the problem better and work
> towards a solution.
Normally clients communicate with SQL Server over network connection, most
commonly these days is TCP/IP, but there is also support for named pipes
and a few more protocols.
But when the client and server are on the same physical machine, using
the network is bit of overkill and therefore there is the possibiliy to
use shared memory, and this is also the default when connecting locally.
You can use the Client Network Utility to turn off shared memory, but
even with TCP/IP locally, you would see much better execution times
locally than over the network.

> This time we enabled client statistics option in Query Analyzer. The
> difference between two queries is for following attributes,
> 1. "Cumulative wait time on server replies" 38045 [for 110 sec execution
> (app server)] v/s 81 [for 30 sec execution (locally from database server)]
> 2. "Number of bytes received" recieved is slightly more for query executed
> from app server compared to database server
> What does "Cumulative wait time on server replies" stats represents and
> how to interpret it?
Books Online says "Cumulative amount of time the driver spent waiting for
replies from the server."
I would account the difference in numbers to the network connection. I
did a quick test on our site. I ran the same SELECT * against a 35000
row table on two servers. One which is hear at our main office in
Stockholm, and one which is at our branch office in Gvle. For the
server here in Stockholm the number was 60, and the server in Gvle
it was 12075. The difference in execution time was 2 seconds in
Stockholm and 28 seconds for the server in Gvle.
I ran both tests from my own machine, which hosts none of the servers in
question.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Query Editor standalone? Like Query analyzer

With Sql Server 2000 you could select and launch the query analyzer without going through the Enterprise Manager. Is there a method for doing the same thing with the new Query Editor, without going through the SqlServer Studio Manager?

Thanks;
Mark E. JohnsonThere is not, no.|||Mark,

Query Analyzer from SQL Server 2000 can connect to a SQL Server 2005 database and be used as before (Note that I can't give any advice on what licensing issues there may be). Not all of the Object Browser functionality works, but from your question, I suspect that's not as important. But the editor features, including graphical query plans, for example, work just fine against 2005.

Steve Kass
Drew University
SQL Server MVP
|||Thank you. What it really means for us, is that there will be a different method for pulling up the query tool. A discussion about what tools we really desire on a developers desktop etc will be in order.

Thanks again;

Query Cost - how is it calculated?

Hi,
I'm trying to figure out where the value of "Cost" comes from in the
Query Analyzer.
For example, when running this on Northwind:
select * from dbo.[Alphabetical list of products]
You get this 3 parts for the Query Plan. The part of
"Categories.PK_Categories" has a cost of 24% of the
total and a value of 0.0119... Where does this value
come from?
All I get is "cost for CPU" and "cost for I/O" - but adding
these together does not equal that value.
Anyone have a clue?
With regards,
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
I doubt that anyone outside of Microsft, and maybe Kalen, could really
answer that question...
Not only does the optimizer estimate IO and CPU, it does some estimation
about how much physical IO is required based on some expectation of how much
of the data might be in memory... It also looks at the recent use of tables
to determine the level of locking for certain operations as well...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Martijn Tonies" <m.tonies@.upscene-removethis.nospam.com> wrote in message
news:ekzghVpZFHA.3040@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I'm trying to figure out where the value of "Cost" comes from in the
> Query Analyzer.
> For example, when running this on Northwind:
> select * from dbo.[Alphabetical list of products]
> You get this 3 parts for the Query Plan. The part of
> "Categories.PK_Categories" has a cost of 24% of the
> total and a value of 0.0119... Where does this value
> come from?
> All I get is "cost for CPU" and "cost for I/O" - but adding
> these together does not equal that value.
>
> Anyone have a clue?
> --
> With regards,
> Martijn Tonies
> Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
> Server
> Upscene Productions
> http://www.upscene.com
>
>
|||Hello Wayne,

> I doubt that anyone outside of Microsft, and maybe Kalen, could really
> answer that question...
> Not only does the optimizer estimate IO and CPU, it does some estimation
> about how much physical IO is required based on some expectation of how
much
> of the data might be in memory... It also looks at the recent use of
tables
> to determine the level of locking for certain operations as well...
Hmm - when extracting a plan via SHOWPLAN_ALL, I do get the estimates
of some of the info (IO/CPU), but I have no idea where the actual "cost"
comes
from.
I've been fiddling around with multiplying IO * "nr of executes" and CPU *
nr of
executes, but it doesn't really add up properly... :-/
With regards,
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
[vbcol=seagreen]
>
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Martijn Tonies" <m.tonies@.upscene-removethis.nospam.com> wrote in message
> news:ekzghVpZFHA.3040@.TK2MSFTNGP14.phx.gbl...
SQL
>

Query Cost - how is it calculated?

Hi,
I'm trying to figure out where the value of "Cost" comes from in the
Query Analyzer.
For example, when running this on Northwind:
select * from dbo.[Alphabetical list of products]
You get this 3 parts for the Query Plan. The part of
"Categories.PK_Categories" has a cost of 24% of the
total and a value of 0.0119... Where does this value
come from?
All I get is "cost for CPU" and "cost for I/O" - but adding
these together does not equal that value.
Anyone have a clue?
--
With regards,
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.comI doubt that anyone outside of Microsft, and maybe Kalen, could really
answer that question...
Not only does the optimizer estimate IO and CPU, it does some estimation
about how much physical IO is required based on some expectation of how much
of the data might be in memory... It also looks at the recent use of tables
to determine the level of locking for certain operations as well...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Martijn Tonies" <m.tonies@.upscene-removethis.nospam.com> wrote in message
news:ekzghVpZFHA.3040@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I'm trying to figure out where the value of "Cost" comes from in the
> Query Analyzer.
> For example, when running this on Northwind:
> select * from dbo.[Alphabetical list of products]
> You get this 3 parts for the Query Plan. The part of
> "Categories.PK_Categories" has a cost of 24% of the
> total and a value of 0.0119... Where does this value
> come from?
> All I get is "cost for CPU" and "cost for I/O" - but adding
> these together does not equal that value.
>
> Anyone have a clue?
> --
> With regards,
> Martijn Tonies
> Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
> Server
> Upscene Productions
> http://www.upscene.com
>
>|||Hello Wayne,
> I doubt that anyone outside of Microsft, and maybe Kalen, could really
> answer that question...
> Not only does the optimizer estimate IO and CPU, it does some estimation
> about how much physical IO is required based on some expectation of how
much
> of the data might be in memory... It also looks at the recent use of
tables
> to determine the level of locking for certain operations as well...
Hmm - when extracting a plan via SHOWPLAN_ALL, I do get the estimates
of some of the info (IO/CPU), but I have no idea where the actual "cost"
comes
from.
I've been fiddling around with multiplying IO * "nr of executes" and CPU *
nr of
executes, but it doesn't really add up properly... :-/
With regards,
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
>
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Martijn Tonies" <m.tonies@.upscene-removethis.nospam.com> wrote in message
> news:ekzghVpZFHA.3040@.TK2MSFTNGP14.phx.gbl...
> > Hi,
> >
> > I'm trying to figure out where the value of "Cost" comes from in the
> > Query Analyzer.
> >
> > For example, when running this on Northwind:
> >
> > select * from dbo.[Alphabetical list of products]
> >
> > You get this 3 parts for the Query Plan. The part of
> > "Categories.PK_Categories" has a cost of 24% of the
> > total and a value of 0.0119... Where does this value
> > come from?
> >
> > All I get is "cost for CPU" and "cost for I/O" - but adding
> > these together does not equal that value.
> >
> >
> > Anyone have a clue?
> >
> > --
> > With regards,
> >
> > Martijn Tonies
> > Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS
SQL
> > Server
> > Upscene Productions
> > http://www.upscene.com
> >
> >
> >
>

Query Cost - how is it calculated?

Hi,
I'm trying to figure out where the value of "Cost" comes from in the
Query Analyzer.
For example, when running this on Northwind:
select * from dbo.[Alphabetical list of products]
You get this 3 parts for the Query Plan. The part of
"Categories.PK_Categories" has a cost of 24% of the
total and a value of 0.0119... Where does this value
come from?
All I get is "cost for CPU" and "cost for I/O" - but adding
these together does not equal that value.
Anyone have a clue?
With regards,
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.comI doubt that anyone outside of Microsft, and maybe Kalen, could really
answer that question...
Not only does the optimizer estimate IO and CPU, it does some estimation
about how much physical IO is required based on some expectation of how much
of the data might be in memory... It also looks at the recent use of tables
to determine the level of locking for certain operations as well...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Martijn Tonies" <m.tonies@.upscene-removethis.nospam.com> wrote in message
news:ekzghVpZFHA.3040@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I'm trying to figure out where the value of "Cost" comes from in the
> Query Analyzer.
> For example, when running this on Northwind:
> select * from dbo.[Alphabetical list of products]
> You get this 3 parts for the Query Plan. The part of
> "Categories.PK_Categories" has a cost of 24% of the
> total and a value of 0.0119... Where does this value
> come from?
> All I get is "cost for CPU" and "cost for I/O" - but adding
> these together does not equal that value.
>
> Anyone have a clue?
> --
> With regards,
> Martijn Tonies
> Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
> Server
> Upscene Productions
> http://www.upscene.com
>
>|||Hello Wayne,

> I doubt that anyone outside of Microsft, and maybe Kalen, could really
> answer that question...
> Not only does the optimizer estimate IO and CPU, it does some estimation
> about how much physical IO is required based on some expectation of how
much
> of the data might be in memory... It also looks at the recent use of
tables
> to determine the level of locking for certain operations as well...
Hmm - when extracting a plan via SHOWPLAN_ALL, I do get the estimates
of some of the info (IO/CPU), but I have no idea where the actual "cost"
comes
from.
I've been fiddling around with multiplying IO * "nr of executes" and CPU *
nr of
executes, but it doesn't really add up properly... :-/
With regards,
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com

>
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Martijn Tonies" <m.tonies@.upscene-removethis.nospam.com> wrote in message
> news:ekzghVpZFHA.3040@.TK2MSFTNGP14.phx.gbl...
SQL[vbcol=seagreen]
>

query analyzer's issue

Dear all,
Because of the large amount of live servers i am obligated to have in my
desktop
six or seven query analyzer sessions (linking servers is forbidden) against
them.
Sometimes and suddenly i lost my keyboard configuration and when I touch the
* key appears another character (this happen in one query analyzer not for
all)
It's a very strange behaviour.
Is there anybody here is suffering a similar problem?
Thanks in advance and best regards,XP professional with SP2.
language sp: english
keyboard: spanish.
Cheers,
"Enric" wrote:

> Dear all,
> Because of the large amount of live servers i am obligated to have in my
> desktop
> six or seven query analyzer sessions (linking servers is forbidden) agains
t
> them.
> Sometimes and suddenly i lost my keyboard configuration and when I touch t
he
> * key appears another character (this happen in one query analyzer not for
> all)
> It's a very strange behaviour.
> Is there anybody here is suffering a similar problem?
> Thanks in advance and best regards,

Query Analyzer-Result to Text

Hi, I am trying to print the query result directly from the query analyzer. I
am having two probles. One - I can't find a way of changing the <untitled>
title on the result, so I have to put it by hand. Is there a way of changing
the title? Two - Some of the fields on the tables were created too wide,
more than the should have been, so the result column are too wide for the
data. Is there a way of narrowing the result columns? I would really
appreciate any help
I don't know how to change the title. I never print directly. I typically
use the grid and copy and paste to Excel. You can issue a CAST() in the
select on the wide columns to make them as small as you want.
Andrew J. Kelly SQL MVP
"HLong" <HLong@.discussions.microsoft.com> wrote in message
news:338E2DC7-46DD-4E06-A0CB-BB89B8C5C343@.microsoft.com...
> Hi, I am trying to print the query result directly from the query
> analyzer. I
> am having two probles. One - I can't find a way of changing the
> <untitled>
> title on the result, so I have to put it by hand. Is there a way of
> changing
> the title? Two - Some of the fields on the tables were created too wide,
> more than the should have been, so the result column are too wide for the
> data. Is there a way of narrowing the result columns? I would really
> appreciate any help
|||Thank you. CAST() works fine for some columns but not for all, specially
calculated columns. I tried (cast(columnA ....)*cast(columnB....)) but it
didn't work.
"Andrew J. Kelly" wrote:

> I don't know how to change the title. I never print directly. I typically
> use the grid and copy and paste to Excel. You can issue a CAST() in the
> select on the wide columns to make them as small as you want.
> --
> Andrew J. Kelly SQL MVP
> "HLong" <HLong@.discussions.microsoft.com> wrote in message
> news:338E2DC7-46DD-4E06-A0CB-BB89B8C5C343@.microsoft.com...
>
>
|||You should do the calculation first and then cast it. I thought you were
talking about character columns anyway.
Andrew J. Kelly SQL MVP
"HLong" <HLong@.discussions.microsoft.com> wrote in message
news:061E730D-C6D1-4F64-BC0B-2F105F7E3203@.microsoft.com...[vbcol=seagreen]
> Thank you. CAST() works fine for some columns but not for all, specially
> calculated columns. I tried (cast(columnA ....)*cast(columnB....)) but
> it
> didn't work.
> "Andrew J. Kelly" wrote:

Query Analyzer?

Experts,
I have a standard SQL 2000 installed onto a Windows 2003 Server on which I
am a local administrator. An IIS server by way of ASP.NET uses this SQL
database server as it's back-end. Someone told me there is a way in SQL to
see who is using the database via the ASP>NET front-end on the IIS server.
Something called Query Analyzer I believe. How do I get to that in SQL? I
am such a SQL novice that I'm afraid I'll need the exact steps to click to
fire this thing up. :-)
Spin
Query Analyser is a query tool that comes with SQL Server 2000 (as part
of Microsoft's "client tools"). You run it from the Start menu (Start |
All Programs | Microsoft SQL Server | Query Analyzer).
However, just running QA (Query Analyser) probably won't help you as you
need to know what queries to actually run in QA to get the info you're
after (and it doesn't sounds like you're quite that advanced, no offence
intended). Running
exec sp_who2
in QA will probably tell you what you need to know but there is a
graphic tool in SQL Server Enterprise Manager that will show it to you
in a GUI, which will probably be much more user friendly for a novice.
To start SQLEM (SQL Server Enterprise Manager) run it from the Start
menu (Start | All Programs | Microsoft SQL Server | Enterprise
Manager). Then expand the tree in the left pane to the local server.
Expand the + for the server (it may ask you for login credentials if you
haven't saved them when registering the server in SQLEM). Then expand
Management | Current Activity and click on Process Info. The right pane
will then contain essentially the same info as you'd get from executing
"exec sp_who2", more or less, but in a more user friendly format.
Hope this helps.
*mike hodgson*
http://sqlnerd.blogspot.com
Spin wrote:

>Experts,
>I have a standard SQL 2000 installed onto a Windows 2003 Server on which I
>am a local administrator. An IIS server by way of ASP.NET uses this SQL
>database server as it's back-end. Someone told me there is a way in SQL to
>see who is using the database via the ASP>NET front-end on the IIS server.
>Something called Query Analyzer I believe. How do I get to that in SQL? I
>am such a SQL novice that I'm afraid I'll need the exact steps to click to
>fire this thing up. :-)
>
>
|||You are the MAN!
Spin
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message
news:%23QZkJwbNGHA.3272@.tk2msftngp13.phx.gbl...
> Query Analyser is a query tool that comes with SQL Server 2000 (as part
> of Microsoft's "client tools"). You run it from the Start menu (Start |
> All Programs | Microsoft SQL Server | Query Analyzer).
> However, just running QA (Query Analyser) probably won't help you as you
> need to know what queries to actually run in QA to get the info you're
> after (and it doesn't sounds like you're quite that advanced, no offence
> intended). Running
> exec sp_who2
> in QA will probably tell you what you need to know but there is a
> graphic tool in SQL Server Enterprise Manager that will show it to you
> in a GUI, which will probably be much more user friendly for a novice.
> To start SQLEM (SQL Server Enterprise Manager) run it from the Start
> menu (Start | All Programs | Microsoft SQL Server | Enterprise
> Manager). Then expand the tree in the left pane to the local server.
> Expand the + for the server (it may ask you for login credentials if you
> haven't saved them when registering the server in SQLEM). Then expand
> Management | Current Activity and click on Process Info. The right pane
> will then contain essentially the same info as you'd get from executing
> "exec sp_who2", more or less, but in a more user friendly format.
> Hope this helps.
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Spin wrote:
>

Query Analyzer?

Experts,
I have a standard SQL 2000 installed onto a Windows 2003 Server on which I
am a local administrator. An IIS server by way of ASP.NET uses this SQL
database server as it's back-end. Someone told me there is a way in SQL to
see who is using the database via the ASP>NET front-end on the IIS server.
Something called Query Analyzer I believe. How do I get to that in SQL? I
am such a SQL novice that I'm afraid I'll need the exact steps to click to
fire this thing up. :-)
SpinQuery Analyser is a query tool that comes with SQL Server 2000 (as part
of Microsoft's "client tools"). You run it from the Start menu (Start |
All Programs | Microsoft SQL Server | Query Analyzer).
However, just running QA (Query Analyser) probably won't help you as you
need to know what queries to actually run in QA to get the info you're
after (and it doesn't sounds like you're quite that advanced, no offence
intended). Running
exec sp_who2
in QA will probably tell you what you need to know but there is a
graphic tool in SQL Server Enterprise Manager that will show it to you
in a GUI, which will probably be much more user friendly for a novice.
To start SQLEM (SQL Server Enterprise Manager) run it from the Start
menu (Start | All Programs | Microsoft SQL Server | Enterprise
Manager). Then expand the tree in the left pane to the local server.
Expand the + for the server (it may ask you for login credentials if you
haven't saved them when registering the server in SQLEM). Then expand
Management | Current Activity and click on Process Info. The right pane
will then contain essentially the same info as you'd get from executing
"exec sp_who2", more or less, but in a more user friendly format.
Hope this helps.
*mike hodgson*
http://sqlnerd.blogspot.com
Spin wrote:

>Experts,
>I have a standard SQL 2000 installed onto a Windows 2003 Server on which I
>am a local administrator. An IIS server by way of ASP.NET uses this SQL
>database server as it's back-end. Someone told me there is a way in SQL to
>see who is using the database via the ASP>NET front-end on the IIS server.
>Something called Query Analyzer I believe. How do I get to that in SQL? I
>am such a SQL novice that I'm afraid I'll need the exact steps to click to
>fire this thing up. :-)
>
>|||You are the MAN!
Spin
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message
news:%23QZkJwbNGHA.3272@.tk2msftngp13.phx.gbl...
> Query Analyser is a query tool that comes with SQL Server 2000 (as part
> of Microsoft's "client tools"). You run it from the Start menu (Start |
> All Programs | Microsoft SQL Server | Query Analyzer).
> However, just running QA (Query Analyser) probably won't help you as you
> need to know what queries to actually run in QA to get the info you're
> after (and it doesn't sounds like you're quite that advanced, no offence
> intended). Running
> exec sp_who2
> in QA will probably tell you what you need to know but there is a
> graphic tool in SQL Server Enterprise Manager that will show it to you
> in a GUI, which will probably be much more user friendly for a novice.
> To start SQLEM (SQL Server Enterprise Manager) run it from the Start
> menu (Start | All Programs | Microsoft SQL Server | Enterprise
> Manager). Then expand the tree in the left pane to the local server.
> Expand the + for the server (it may ask you for login credentials if you
> haven't saved them when registering the server in SQLEM). Then expand
> Management | Current Activity and click on Process Info. The right pane
> will then contain essentially the same info as you'd get from executing
> "exec sp_who2", more or less, but in a more user friendly format.
> Hope this helps.
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Spin wrote:
>
>

Query Analyzer?

Experts,
I have a standard SQL 2000 installed onto a Windows 2003 Server on which I
am a local administrator. An IIS server by way of ASP.NET uses this SQL
database server as it's back-end. Someone told me there is a way in SQL to
see who is using the database via the ASP>NET front-end on the IIS server.
Something called Query Analyzer I believe. How do I get to that in SQL? I
am such a SQL novice that I'm afraid I'll need the exact steps to click to
fire this thing up. :-)
--
SpinThis is a multi-part message in MIME format.
--010701060909050109080101
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Query Analyser is a query tool that comes with SQL Server 2000 (as part
of Microsoft's "client tools"). You run it from the Start menu (Start |
All Programs | Microsoft SQL Server | Query Analyzer).
However, just running QA (Query Analyser) probably won't help you as you
need to know what queries to actually run in QA to get the info you're
after (and it doesn't sounds like you're quite that advanced, no offence
intended). Running
exec sp_who2
in QA will probably tell you what you need to know but there is a
graphic tool in SQL Server Enterprise Manager that will show it to you
in a GUI, which will probably be much more user friendly for a novice.
To start SQLEM (SQL Server Enterprise Manager) run it from the Start
menu (Start | All Programs | Microsoft SQL Server | Enterprise
Manager). Then expand the tree in the left pane to the local server.
Expand the + for the server (it may ask you for login credentials if you
haven't saved them when registering the server in SQLEM). Then expand
Management | Current Activity and click on Process Info. The right pane
will then contain essentially the same info as you'd get from executing
"exec sp_who2", more or less, but in a more user friendly format.
Hope this helps.
--
*mike hodgson*
http://sqlnerd.blogspot.com
Spin wrote:
>Experts,
>I have a standard SQL 2000 installed onto a Windows 2003 Server on which I
>am a local administrator. An IIS server by way of ASP.NET uses this SQL
>database server as it's back-end. Someone told me there is a way in SQL to
>see who is using the database via the ASP>NET front-end on the IIS server.
>Something called Query Analyzer I believe. How do I get to that in SQL? I
>am such a SQL novice that I'm afraid I'll need the exact steps to click to
>fire this thing up. :-)
>
>
--010701060909050109080101
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Query Analyser is a query tool that comes with SQL Server 2000 (as
part of Microsoft's "client tools"). You run it from the Start menu
(Start | All Programs | Microsoft SQL Server | Query Analyzer).<br>
<br>
However, just running QA (Query Analyser) probably won't help you as
you need to know what queries to actually run in QA to get the info
you're after (and it doesn't sounds like you're quite that advanced, no
offence intended). Running<br>
<br>
exec sp_who2<br>
<br>
in QA will probably tell you what you need to know but there is a
graphic tool in SQL Server Enterprise Manager that will show it to you
in a GUI, which will probably be much more user friendly for a novice.<br>
<br>
To start SQLEM (SQL Server Enterprise Manager) run it from the Start
menu (Start | All Programs | Microsoft SQL Server | Enterprise
Manager). Then expand the tree in the left pane to the local server.
Expand the + for the server (it may ask you for login credentials if
you haven't saved them when registering the server in SQLEM). Then
expand Management | Current Activity and click on Process Info. The
right pane will then contain essentially the same info as you'd get
from executing "exec sp_who2", more or less, but in a more user
friendly format.<br>
<br>
Hope this helps.<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Spin wrote:
<blockquote cite="mid45sij6F88964U1@.individual.net" type="cite">
<pre wrap="">Experts,
I have a standard SQL 2000 installed onto a Windows 2003 Server on which I
am a local administrator. An IIS server by way of ASP.NET uses this SQL
database server as it's back-end. Someone told me there is a way in SQL to
see who is using the database via the ASP>NET front-end on the IIS server.
Something called Query Analyzer I believe. How do I get to that in SQL? I
am such a SQL novice that I'm afraid I'll need the exact steps to click to
fire this thing up. :-)
</pre>
</blockquote>
</body>
</html>
--010701060909050109080101--|||You are the MAN!
--
Spin
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message
news:%23QZkJwbNGHA.3272@.tk2msftngp13.phx.gbl...
> Query Analyser is a query tool that comes with SQL Server 2000 (as part
> of Microsoft's "client tools"). You run it from the Start menu (Start |
> All Programs | Microsoft SQL Server | Query Analyzer).
> However, just running QA (Query Analyser) probably won't help you as you
> need to know what queries to actually run in QA to get the info you're
> after (and it doesn't sounds like you're quite that advanced, no offence
> intended). Running
> exec sp_who2
> in QA will probably tell you what you need to know but there is a
> graphic tool in SQL Server Enterprise Manager that will show it to you
> in a GUI, which will probably be much more user friendly for a novice.
> To start SQLEM (SQL Server Enterprise Manager) run it from the Start
> menu (Start | All Programs | Microsoft SQL Server | Enterprise
> Manager). Then expand the tree in the left pane to the local server.
> Expand the + for the server (it may ask you for login credentials if you
> haven't saved them when registering the server in SQLEM). Then expand
> Management | Current Activity and click on Process Info. The right pane
> will then contain essentially the same info as you'd get from executing
> "exec sp_who2", more or less, but in a more user friendly format.
> Hope this helps.
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Spin wrote:
>>Experts,
>>I have a standard SQL 2000 installed onto a Windows 2003 Server on which I
>>am a local administrator. An IIS server by way of ASP.NET uses this SQL
>>database server as it's back-end. Someone told me there is a way in SQL
>>to
>>see who is using the database via the ASP>NET front-end on the IIS server.
>>Something called Query Analyzer I believe. How do I get to that in SQL?
>>I
>>am such a SQL novice that I'm afraid I'll need the exact steps to click to
>>fire this thing up. :-)
>>
>

Query Analyzer: Keyword color schema.

Hello,
Are there any information about Whick keywords is colored by Query Analyzer
?
I want to create keyword schema file for IMHO Instant blogger's Code Snippet
Editor.
Books Online's reserved keywords is not enouph.
For example: @.@.error, any sysobjects, etc.
Regards,
Yoshihiro Kawabata
MVP for SQL Server
PASSJ board-leader.
Yoshihiro Kawabata wrote:
> Hello,
> Are there any information about Whick keywords is colored by Query
> Analyzer ?
> I want to create keyword schema file for IMHO Instant blogger's Code
> Snippet Editor.
> Books Online's reserved keywords is not enouph.
> For example: @.@.error, any sysobjects, etc.
> Regards,
> Yoshihiro Kawabata
> MVP for SQL Server
> PASSJ board-leader.
Have a look at the SQL Server 2000 Syntax File for TextPad here:
http://www.textpad.com/add-ons/synn2t.html
Scroll to the item called:
SQL (Transact) TextPad syntax definitions for Transact SQL.
Complete list of keywords for MSSQL2000 SP3a.
Contributed by Alexander Mitelman, 17 August 2004.
You don't need TextPad to view the file. It may give you a good start.
David Gugick
Imceda Software
www.imceda.com
|||Hello, David.
Thank you for quick response.
It's a very nice.
I will feed back to IMHO team.
Best regards,
Yoshihiro Kawabata
MVP for SQL Server.
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:OAZog83KFHA.3076@.tk2msftngp13.phx.gbl...
> Yoshihiro Kawabata wrote:
> Have a look at the SQL Server 2000 Syntax File for TextPad here:
> http://www.textpad.com/add-ons/synn2t.html
> Scroll to the item called:
> SQL (Transact) TextPad syntax definitions for Transact SQL. Complete
> list of keywords for MSSQL2000 SP3a.
> Contributed by Alexander Mitelman, 17 August 2004.
>
> You don't need TextPad to view the file. It may give you a good start.
> --
> David Gugick
> Imceda Software
> www.imceda.com

Query Analyzer: Execution Plan: Clustered Index Seek: I/O Cost

Can anyone explain how I/O cost is calculated?
My example:
Physical operation: Clustered Index Seek
Logical operation: Clustered Index Seek
Row count: 1
Estimated row size: 76
I/O cost: 0.00632
CPU cost: 0.000080
Number of executes: 1
Cost: 0.006408(100%)
Subtree cost: 0.00640
Estimated row count: 1
Argument: ...
If you really want to know some of the details about query costs, you should
read some of Joe Chang's articles at www.sql-server-performance.com . This
is an excellent site for performance tips, and Joe has several detailed
articles about calculating the cost of a query.
"Dave Owen" <DaveOwen@.discussions.microsoft.com> wrote in message
news:811149F2-25E0-43BA-B3A6-43B17D7014F4@.microsoft.com...
> Can anyone explain how I/O cost is calculated?
> My example:
> Physical operation: Clustered Index Seek
> Logical operation: Clustered Index Seek
> Row count: 1
> Estimated row size: 76
> I/O cost: 0.00632
> CPU cost: 0.000080
> Number of executes: 1
> Cost: 0.006408(100%)
> Subtree cost: 0.00640
> Estimated row count: 1
> Argument: ...

Query analyzer...

I was wondering if there is any way I can find/make an install of ONLY
the client tools (isqlw, etc.) so that I don't have to pass out the
Server install CD all the time? Or maybe just grab all the files needed
and know where to put them...
Our programmers insist on installing that for everyone and their dog so
I'd like to just put it somewhere on the network or on a CD so it can be
accessible easily.
TIA!!
Follow the directions within SQLCLI.BAT on the install disk, and check the
SQLCLI.ISS file for info on what gets installed.
Simon Worth
"Jesse Gardner" <admin_deleteth1s@.badcrc.com> wrote in message
news:38rhshF5q49adU1@.individual.net...
> I was wondering if there is any way I can find/make an install of ONLY
> the client tools (isqlw, etc.) so that I don't have to pass out the
> Server install CD all the time? Or maybe just grab all the files needed
> and know where to put them...
> Our programmers insist on installing that for everyone and their dog so
> I'd like to just put it somewhere on the network or on a CD so it can be
> accessible easily.
>
> TIA!!
|||Sorry, forgot this part
start /wait x86\setup\setupsql.exe -s -m -SMS -f1 "sqlcli.iss"
That's what the batch file installs for unattended client tools installs.
Simon Worth
"Jesse Gardner" <admin_deleteth1s@.badcrc.com> wrote in message
news:38rhshF5q49adU1@.individual.net...
> I was wondering if there is any way I can find/make an install of ONLY
> the client tools (isqlw, etc.) so that I don't have to pass out the
> Server install CD all the time? Or maybe just grab all the files needed
> and know where to put them...
> Our programmers insist on installing that for everyone and their dog so
> I'd like to just put it somewhere on the network or on a CD so it can be
> accessible easily.
>
> TIA!!
|||You ROCK!
Simon Worth wrote:
> Sorry, forgot this part
> start /wait x86\setup\setupsql.exe -s -m -SMS -f1 "sqlcli.iss"
> That's what the batch file installs for unattended client tools installs.
>
|||I do have one question though... What points to what files? This is
what I'm seeing:
[SQLComponentMult-0]
MgtTool\SEM\ActiveX-type=string
MgtTool\SEM\ActiveX-count=2
MgtTool\SEM\ActiveX-0=MgtTool\SEM\ActiveX\Res1033
MgtTool\SEM\ActiveX-1=MgtTool\SEM\ActiveX\ResIntl
MgtTool\SEM\Office-type=string
MgtTool\SEM\Office-count=2
MgtTool\SEM\Office-0=MgtTool\SEM\Office\Res1033
MgtTool\SEM\Office-1=MgtTool\SEM\Office\ResIntl
MgtTool\SEM-type=string
MgtTool\SEM-count=12
MgtTool\SEM-0=MgtTool\SEM\HTML
MgtTool\SEM-1=MgtTool\SEM\MSD98
MgtTool\SEM-2=MgtTool\SEM\MSD98SYS
MgtTool\SEM-3=MgtTool\SEM\MSD98Res
MgtTool\SEM-4=MgtTool\SEM\MSD98Hlp
MgtTool\SEM-5=MgtTool\SEM\Help
MgtTool\SEM-6=MgtTool\SEM\Res1033
MgtTool\SEM-7=MgtTool\SEM\ResIntl
MgtTool\SEM-8=MgtTool\SEM\MSD98RsI
MgtTool\SEM-9=MgtTool\SEM\ActiveX
MgtTool\SEM-10=MgtTool\SEM\Office
MgtTool\SEM-11=MgtTool\SEM\Scripts
MgtTool\Profiler-type=string
MgtTool\Profiler-count=3
MgtTool\Profiler-0=MgtTool\Profiler\Help
MgtTool\Profiler-1=MgtTool\Profiler\Res1033
MgtTool\Profiler-2=MgtTool\Profiler\ResIntl
MgtTool\Qryanlz-type=string
MgtTool\Qryanlz-count=3
MgtTool\Qryanlz-0=MgtTool\Qryanlz\Help
MgtTool\Qryanlz-1=MgtTool\Qryanlz\Res1033
MgtTool\Qryanlz-2=MgtTool\Qryanlz\ResIntl
MgtTool\Wzcnflct-type=string
MgtTool\Wzcnflct-count=4
MgtTool\Wzcnflct-0=MgtTool\Wzcnflct\WzcnHlp
MgtTool\Wzcnflct-1=MgtTool\Wzcnflct\Wzcn1033
MgtTool\Wzcnflct-2=MgtTool\Wzcnflct\WzcnOthr
MgtTool\Wzcnflct-3=MgtTool\Wzcnflct\WzcnCmn
MgtTool-type=string
MgtTool-count=7
MgtTool-0=MgtTool\SEM
MgtTool-1=MgtTool\Profiler
MgtTool-2=MgtTool\Qryanlz
MgtTool-3=MgtTool\DTCCLi
MgtTool-4=MgtTool\Wzcnflct
MgtTool-5=MgtTool\UtilSys
MgtTool-6=MgtTool\UtilBinn
Connect-type=string
Connect-count=3
Connect-0=Connect\ConnSys
Connect-1=Connect\Conn9x
Connect-2=Connect\ConnNT
Books\Bookso-type=string
Books\Bookso-count=1
Books\Bookso-0=Books\Bookso\Utils
Books\BooksCD-type=string
Books\BooksCD-count=1
Books\BooksCD-0=Books\BooksCD\Utils
Books-type=string
Books-count=2
Books-0=Books\Bookso
Books-1=Books\BooksCD
DevTools\Dbg Int-type=string
DevTools\Dbg Int-count=2
DevTools\Dbg Int-0=DevTools\Dbg Int\Dbg Int Common
DevTools\Dbg Int-1=DevTools\Dbg Int\EXE
DevTools-type=string
DevTools-count=1
DevTools-0=DevTools\Dbg Int
CoreRepl-type=string
CoreRepl-count=2
CoreRepl-0=CoreRepl\Res1033
CoreRepl-1=CoreRepl\ResIntl
Repostry-type=string
Repostry-count=3
Repostry-0=Repostry\RepstSys
Repostry-1=Repostry\Res1033
Repostry-2=Repostry\ResIntl
CoreMisc\ActiveX-type=string
CoreMisc\ActiveX-count=2
CoreMisc\ActiveX-0=CoreMisc\ActiveX\Res1033
CoreMisc\ActiveX-1=CoreMisc\ActiveX\ResIntl
CoreMisc-type=string
CoreMisc-count=2
CoreMisc-0=CoreMisc\ActiveX
CoreMisc-1=CoreMisc\Res1033
Monarch-type=string
Monarch-count=2
Monarch-0=Monarch\Monr1033
Monarch-1=Monarch\MonrIntl
CoreCOM-type=string
CoreCOM-count=2
CoreCOM-0=CoreCOM\Res1033
CoreCOM-1=CoreCOM\ResIntl
CoreTool-type=string
CoreTool-count=2
CoreTool-0=CoreTool\Res1033
CoreTool-1=CoreTool\ResOther
SFExt\ActiveX-type=string
SFExt\ActiveX-count=2
SFExt\ActiveX-0=SFExt\ActiveX\Res1033
SFExt\ActiveX-1=SFExt\ActiveX\ResIntl
SFExt-type=string
SFExt-count=3
SFExt-0=SFExt\ActiveX
SFExt-1=SFExt\Res1033
SFExt-2=SFExt\ResIntl
Trace-type=string
Trace-count=2
Trace-0=Trace\Res1033
Trace-1=Trace\ResOther
MC-type=string
MC-count=3
MC-0=MC\MC1033
MC-1=MC\MCIntl
MC-2=MC\Help
DTSUI-type=string
DTSUI-count=2
DTSUI-0=DTSUI\Res1033
DTSUI-1=DTSUI\ResIntl
MSOlap-type=string
MSOlap-count=2
MSOlap-0=MSOlap\Res1033
MSOlap-1=MSOlap\ResIntl
ATL-type=string
ATL-count=2
ATL-0=ATL\winnt
ATL-1=ATL\win9x
Component-type=string
Component-count=21
Component-0=MgtTool
Component-1=Connect
Component-2=Books
Component-3=DevTools
Component-4=CoreRepl
Component-5=Repostry
Component-6=CoreMisc
Component-7=Monarch
Component-8=CoreCOM
Component-9=CoreTool
Component-10=DBLibCli
Component-11=SFExt
Component-12=Trace
Component-13=MiscCore
Component-14=MC
Component-15=DTSUI
Component-16=MSOlap
Component-17=ATL
Component-18=MFC42U
Component-19=VC
Component-20=VB
Result=1
Simon Worth wrote:
> Sorry, forgot this part
> start /wait x86\setup\setupsql.exe -s -m -SMS -f1 "sqlcli.iss"
> That's what the batch file installs for unattended client tools installs.
>
|||That's not going to list what files are required to do an install - that
lists the requriments for the process to complete. Sorry about that, I
didn't mean to indicate the ISS file would list the files needed. That's
handled by the installer.
Simon Worth
"Jesse Gardner" <admin_deleteth1s@.badcrc.com> wrote in message
news:38rmmfF5ndtkhU1@.individual.net...[vbcol=seagreen]
> I do have one question though... What points to what files? This is
> what I'm seeing:
> [SQLComponentMult-0]
> MgtTool\SEM\ActiveX-type=string
> MgtTool\SEM\ActiveX-count=2
> MgtTool\SEM\ActiveX-0=MgtTool\SEM\ActiveX\Res1033
> MgtTool\SEM\ActiveX-1=MgtTool\SEM\ActiveX\ResIntl
> MgtTool\SEM\Office-type=string
> MgtTool\SEM\Office-count=2
> MgtTool\SEM\Office-0=MgtTool\SEM\Office\Res1033
> MgtTool\SEM\Office-1=MgtTool\SEM\Office\ResIntl
> MgtTool\SEM-type=string
> MgtTool\SEM-count=12
> MgtTool\SEM-0=MgtTool\SEM\HTML
> MgtTool\SEM-1=MgtTool\SEM\MSD98
> MgtTool\SEM-2=MgtTool\SEM\MSD98SYS
> MgtTool\SEM-3=MgtTool\SEM\MSD98Res
> MgtTool\SEM-4=MgtTool\SEM\MSD98Hlp
> MgtTool\SEM-5=MgtTool\SEM\Help
> MgtTool\SEM-6=MgtTool\SEM\Res1033
> MgtTool\SEM-7=MgtTool\SEM\ResIntl
> MgtTool\SEM-8=MgtTool\SEM\MSD98RsI
> MgtTool\SEM-9=MgtTool\SEM\ActiveX
> MgtTool\SEM-10=MgtTool\SEM\Office
> MgtTool\SEM-11=MgtTool\SEM\Scripts
> MgtTool\Profiler-type=string
> MgtTool\Profiler-count=3
> MgtTool\Profiler-0=MgtTool\Profiler\Help
> MgtTool\Profiler-1=MgtTool\Profiler\Res1033
> MgtTool\Profiler-2=MgtTool\Profiler\ResIntl
> MgtTool\Qryanlz-type=string
> MgtTool\Qryanlz-count=3
> MgtTool\Qryanlz-0=MgtTool\Qryanlz\Help
> MgtTool\Qryanlz-1=MgtTool\Qryanlz\Res1033
> MgtTool\Qryanlz-2=MgtTool\Qryanlz\ResIntl
> MgtTool\Wzcnflct-type=string
> MgtTool\Wzcnflct-count=4
> MgtTool\Wzcnflct-0=MgtTool\Wzcnflct\WzcnHlp
> MgtTool\Wzcnflct-1=MgtTool\Wzcnflct\Wzcn1033
> MgtTool\Wzcnflct-2=MgtTool\Wzcnflct\WzcnOthr
> MgtTool\Wzcnflct-3=MgtTool\Wzcnflct\WzcnCmn
> MgtTool-type=string
> MgtTool-count=7
> MgtTool-0=MgtTool\SEM
> MgtTool-1=MgtTool\Profiler
> MgtTool-2=MgtTool\Qryanlz
> MgtTool-3=MgtTool\DTCCLi
> MgtTool-4=MgtTool\Wzcnflct
> MgtTool-5=MgtTool\UtilSys
> MgtTool-6=MgtTool\UtilBinn
> Connect-type=string
> Connect-count=3
> Connect-0=Connect\ConnSys
> Connect-1=Connect\Conn9x
> Connect-2=Connect\ConnNT
> Books\Bookso-type=string
> Books\Bookso-count=1
> Books\Bookso-0=Books\Bookso\Utils
> Books\BooksCD-type=string
> Books\BooksCD-count=1
> Books\BooksCD-0=Books\BooksCD\Utils
> Books-type=string
> Books-count=2
> Books-0=Books\Bookso
> Books-1=Books\BooksCD
> DevTools\Dbg Int-type=string
> DevTools\Dbg Int-count=2
> DevTools\Dbg Int-0=DevTools\Dbg Int\Dbg Int Common
> DevTools\Dbg Int-1=DevTools\Dbg Int\EXE
> DevTools-type=string
> DevTools-count=1
> DevTools-0=DevTools\Dbg Int
> CoreRepl-type=string
> CoreRepl-count=2
> CoreRepl-0=CoreRepl\Res1033
> CoreRepl-1=CoreRepl\ResIntl
> Repostry-type=string
> Repostry-count=3
> Repostry-0=Repostry\RepstSys
> Repostry-1=Repostry\Res1033
> Repostry-2=Repostry\ResIntl
> CoreMisc\ActiveX-type=string
> CoreMisc\ActiveX-count=2
> CoreMisc\ActiveX-0=CoreMisc\ActiveX\Res1033
> CoreMisc\ActiveX-1=CoreMisc\ActiveX\ResIntl
> CoreMisc-type=string
> CoreMisc-count=2
> CoreMisc-0=CoreMisc\ActiveX
> CoreMisc-1=CoreMisc\Res1033
> Monarch-type=string
> Monarch-count=2
> Monarch-0=Monarch\Monr1033
> Monarch-1=Monarch\MonrIntl
> CoreCOM-type=string
> CoreCOM-count=2
> CoreCOM-0=CoreCOM\Res1033
> CoreCOM-1=CoreCOM\ResIntl
> CoreTool-type=string
> CoreTool-count=2
> CoreTool-0=CoreTool\Res1033
> CoreTool-1=CoreTool\ResOther
> SFExt\ActiveX-type=string
> SFExt\ActiveX-count=2
> SFExt\ActiveX-0=SFExt\ActiveX\Res1033
> SFExt\ActiveX-1=SFExt\ActiveX\ResIntl
> SFExt-type=string
> SFExt-count=3
> SFExt-0=SFExt\ActiveX
> SFExt-1=SFExt\Res1033
> SFExt-2=SFExt\ResIntl
> Trace-type=string
> Trace-count=2
> Trace-0=Trace\Res1033
> Trace-1=Trace\ResOther
> MC-type=string
> MC-count=3
> MC-0=MC\MC1033
> MC-1=MC\MCIntl
> MC-2=MC\Help
> DTSUI-type=string
> DTSUI-count=2
> DTSUI-0=DTSUI\Res1033
> DTSUI-1=DTSUI\ResIntl
> MSOlap-type=string
> MSOlap-count=2
> MSOlap-0=MSOlap\Res1033
> MSOlap-1=MSOlap\ResIntl
> ATL-type=string
> ATL-count=2
> ATL-0=ATL\winnt
> ATL-1=ATL\win9x
> Component-type=string
> Component-count=21
> Component-0=MgtTool
> Component-1=Connect
> Component-2=Books
> Component-3=DevTools
> Component-4=CoreRepl
> Component-5=Repostry
> Component-6=CoreMisc
> Component-7=Monarch
> Component-8=CoreCOM
> Component-9=CoreTool
> Component-10=DBLibCli
> Component-11=SFExt
> Component-12=Trace
> Component-13=MiscCore
> Component-14=MC
> Component-15=DTSUI
> Component-16=MSOlap
> Component-17=ATL
> Component-18=MFC42U
> Component-19=VC
> Component-20=VB
> Result=1
>
> Simon Worth wrote:
installs.[vbcol=seagreen]

Query analyzer...

I was wondering if there is any way I can find/make an install of ONLY
the client tools (isqlw, etc.) so that I don't have to pass out the
Server install CD all the time? Or maybe just grab all the files needed
and know where to put them...
Our programmers insist on installing that for everyone and their dog so
I'd like to just put it somewhere on the network or on a CD so it can be
accessible easily.
TIA!!Follow the directions within SQLCLI.BAT on the install disk, and check the
SQLCLI.ISS file for info on what gets installed.
Simon Worth
"Jesse Gardner" <admin_deleteth1s@.badcrc.com> wrote in message
news:38rhshF5q49adU1@.individual.net...
> I was wondering if there is any way I can find/make an install of ONLY
> the client tools (isqlw, etc.) so that I don't have to pass out the
> Server install CD all the time? Or maybe just grab all the files needed
> and know where to put them...
> Our programmers insist on installing that for everyone and their dog so
> I'd like to just put it somewhere on the network or on a CD so it can be
> accessible easily.
>
> TIA!!|||Sorry, forgot this part
start /wait x86\setup\setupsql.exe -s -m -SMS -f1 "sqlcli.iss"
That's what the batch file installs for unattended client tools installs.
Simon Worth
"Jesse Gardner" <admin_deleteth1s@.badcrc.com> wrote in message
news:38rhshF5q49adU1@.individual.net...
> I was wondering if there is any way I can find/make an install of ONLY
> the client tools (isqlw, etc.) so that I don't have to pass out the
> Server install CD all the time? Or maybe just grab all the files needed
> and know where to put them...
> Our programmers insist on installing that for everyone and their dog so
> I'd like to just put it somewhere on the network or on a CD so it can be
> accessible easily.
>
> TIA!!|||You ROCK!
Simon Worth wrote:
> Sorry, forgot this part
> start /wait x86\setup\setupsql.exe -s -m -SMS -f1 "sqlcli.iss"
> That's what the batch file installs for unattended client tools installs.
>|||I do have one question though... What points to what files? This is
what I'm seeing:
[SQLComponentMult-0]
MgtTool\SEM\ActiveX-type=string
MgtTool\SEM\ActiveX-count=2
MgtTool\SEM\ActiveX-0=MgtTool\SEM\ActiveX\Res1033
MgtTool\SEM\ActiveX-1=MgtTool\SEM\ActiveX\ResIntl
MgtTool\SEM\Office-type=string
MgtTool\SEM\Office-count=2
MgtTool\SEM\Office-0=MgtTool\SEM\Office\Res1033
MgtTool\SEM\Office-1=MgtTool\SEM\Office\ResIntl
MgtTool\SEM-type=string
MgtTool\SEM-count=12
MgtTool\SEM-0=MgtTool\SEM\HTML
MgtTool\SEM-1=MgtTool\SEM\MSD98
MgtTool\SEM-2=MgtTool\SEM\MSD98SYS
MgtTool\SEM-3=MgtTool\SEM\MSD98Res
MgtTool\SEM-4=MgtTool\SEM\MSD98Hlp
MgtTool\SEM-5=MgtTool\SEM\Help
MgtTool\SEM-6=MgtTool\SEM\Res1033
MgtTool\SEM-7=MgtTool\SEM\ResIntl
MgtTool\SEM-8=MgtTool\SEM\MSD98RsI
MgtTool\SEM-9=MgtTool\SEM\ActiveX
MgtTool\SEM-10=MgtTool\SEM\Office
MgtTool\SEM-11=MgtTool\SEM\Scripts
MgtTool\Profiler-type=string
MgtTool\Profiler-count=3
MgtTool\Profiler-0=MgtTool\Profiler\Help
MgtTool\Profiler-1=MgtTool\Profiler\Res1033
MgtTool\Profiler-2=MgtTool\Profiler\ResIntl
MgtTool\Qryanlz-type=string
MgtTool\Qryanlz-count=3
MgtTool\Qryanlz-0=MgtTool\Qryanlz\Help
MgtTool\Qryanlz-1=MgtTool\Qryanlz\Res1033
MgtTool\Qryanlz-2=MgtTool\Qryanlz\ResIntl
MgtTool\Wzcnflct-type=string
MgtTool\Wzcnflct-count=4
MgtTool\Wzcnflct-0=MgtTool\Wzcnflct\WzcnHlp
MgtTool\Wzcnflct-1=MgtTool\Wzcnflct\Wzcn1033
MgtTool\Wzcnflct-2=MgtTool\Wzcnflct\WzcnOthr
MgtTool\Wzcnflct-3=MgtTool\Wzcnflct\WzcnCmn
MgtTool-type=string
MgtTool-count=7
MgtTool-0=MgtTool\SEM
MgtTool-1=MgtTool\Profiler
MgtTool-2=MgtTool\Qryanlz
MgtTool-3=MgtTool\DTCCLi
MgtTool-4=MgtTool\Wzcnflct
MgtTool-5=MgtTool\UtilSys
MgtTool-6=MgtTool\UtilBinn
Connect-type=string
Connect-count=3
Connect-0=Connect\ConnSys
Connect-1=Connect\Conn9x
Connect-2=Connect\ConnNT
Books\Bookso-type=string
Books\Bookso-count=1
Books\Bookso-0=Books\Bookso\Utils
Books\BooksCD-type=string
Books\BooksCD-count=1
Books\BooksCD-0=Books\BooksCD\Utils
Books-type=string
Books-count=2
Books-0=Books\Bookso
Books-1=Books\BooksCD
DevTools\Dbg Int-type=string
DevTools\Dbg Int-count=2
DevTools\Dbg Int-0=DevTools\Dbg Int\Dbg Int Common
DevTools\Dbg Int-1=DevTools\Dbg Int\EXE
DevTools-type=string
DevTools-count=1
DevTools-0=DevTools\Dbg Int
CoreRepl-type=string
CoreRepl-count=2
CoreRepl-0=CoreRepl\Res1033
CoreRepl-1=CoreRepl\ResIntl
Repostry-type=string
Repostry-count=3
Repostry-0=Repostry\RepstSys
Repostry-1=Repostry\Res1033
Repostry-2=Repostry\ResIntl
CoreMisc\ActiveX-type=string
CoreMisc\ActiveX-count=2
CoreMisc\ActiveX-0=CoreMisc\ActiveX\Res1033
CoreMisc\ActiveX-1=CoreMisc\ActiveX\ResIntl
CoreMisc-type=string
CoreMisc-count=2
CoreMisc-0=CoreMisc\ActiveX
CoreMisc-1=CoreMisc\Res1033
Monarch-type=string
Monarch-count=2
Monarch-0=Monarch\Monr1033
Monarch-1=Monarch\MonrIntl
CoreCOM-type=string
CoreCOM-count=2
CoreCOM-0=CoreCOM\Res1033
CoreCOM-1=CoreCOM\ResIntl
CoreTool-type=string
CoreTool-count=2
CoreTool-0=CoreTool\Res1033
CoreTool-1=CoreTool\ResOther
SFExt\ActiveX-type=string
SFExt\ActiveX-count=2
SFExt\ActiveX-0=SFExt\ActiveX\Res1033
SFExt\ActiveX-1=SFExt\ActiveX\ResIntl
SFExt-type=string
SFExt-count=3
SFExt-0=SFExt\ActiveX
SFExt-1=SFExt\Res1033
SFExt-2=SFExt\ResIntl
Trace-type=string
Trace-count=2
Trace-0=Trace\Res1033
Trace-1=Trace\ResOther
MC-type=string
MC-count=3
MC-0=MC\MC1033
MC-1=MC\MCIntl
MC-2=MC\Help
DTSUI-type=string
DTSUI-count=2
DTSUI-0=DTSUI\Res1033
DTSUI-1=DTSUI\ResIntl
MSOlap-type=string
MSOlap-count=2
MSOlap-0=MSOlap\Res1033
MSOlap-1=MSOlap\ResIntl
ATL-type=string
ATL-count=2
ATL-0=ATL\winnt
ATL-1=ATL\win9x
Component-type=string
Component-count=21
Component-0=MgtTool
Component-1=Connect
Component-2=Books
Component-3=DevTools
Component-4=CoreRepl
Component-5=Repostry
Component-6=CoreMisc
Component-7=Monarch
Component-8=CoreCOM
Component-9=CoreTool
Component-10=DBLibCli
Component-11=SFExt
Component-12=Trace
Component-13=MiscCore
Component-14=MC
Component-15=DTSUI
Component-16=MSOlap
Component-17=ATL
Component-18=MFC42U
Component-19=VC
Component-20=VB
Result=1
Simon Worth wrote:
> Sorry, forgot this part
> start /wait x86\setup\setupsql.exe -s -m -SMS -f1 "sqlcli.iss"
> That's what the batch file installs for unattended client tools installs.
>|||That's not going to list what files are required to do an install - that
lists the requriments for the process to complete. Sorry about that, I
didn't mean to indicate the ISS file would list the files needed. That's
handled by the installer.
Simon Worth
"Jesse Gardner" <admin_deleteth1s@.badcrc.com> wrote in message
news:38rmmfF5ndtkhU1@.individual.net...[vbcol=seagreen]
> I do have one question though... What points to what files? This is
> what I'm seeing:
> [SQLComponentMult-0]
> MgtTool\SEM\ActiveX-type=string
> MgtTool\SEM\ActiveX-count=2
> MgtTool\SEM\ActiveX-0=MgtTool\SEM\ActiveX\Res1033
> MgtTool\SEM\ActiveX-1=MgtTool\SEM\ActiveX\ResIntl
> MgtTool\SEM\Office-type=string
> MgtTool\SEM\Office-count=2
> MgtTool\SEM\Office-0=MgtTool\SEM\Office\Res1033
> MgtTool\SEM\Office-1=MgtTool\SEM\Office\ResIntl
> MgtTool\SEM-type=string
> MgtTool\SEM-count=12
> MgtTool\SEM-0=MgtTool\SEM\HTML
> MgtTool\SEM-1=MgtTool\SEM\MSD98
> MgtTool\SEM-2=MgtTool\SEM\MSD98SYS
> MgtTool\SEM-3=MgtTool\SEM\MSD98Res
> MgtTool\SEM-4=MgtTool\SEM\MSD98Hlp
> MgtTool\SEM-5=MgtTool\SEM\Help
> MgtTool\SEM-6=MgtTool\SEM\Res1033
> MgtTool\SEM-7=MgtTool\SEM\ResIntl
> MgtTool\SEM-8=MgtTool\SEM\MSD98RsI
> MgtTool\SEM-9=MgtTool\SEM\ActiveX
> MgtTool\SEM-10=MgtTool\SEM\Office
> MgtTool\SEM-11=MgtTool\SEM\Scripts
> MgtTool\Profiler-type=string
> MgtTool\Profiler-count=3
> MgtTool\Profiler-0=MgtTool\Profiler\Help
> MgtTool\Profiler-1=MgtTool\Profiler\Res1033
> MgtTool\Profiler-2=MgtTool\Profiler\ResIntl
> MgtTool\Qryanlz-type=string
> MgtTool\Qryanlz-count=3
> MgtTool\Qryanlz-0=MgtTool\Qryanlz\Help
> MgtTool\Qryanlz-1=MgtTool\Qryanlz\Res1033
> MgtTool\Qryanlz-2=MgtTool\Qryanlz\ResIntl
> MgtTool\Wzcnflct-type=string
> MgtTool\Wzcnflct-count=4
> MgtTool\Wzcnflct-0=MgtTool\Wzcnflct\WzcnHlp
> MgtTool\Wzcnflct-1=MgtTool\Wzcnflct\Wzcn1033
> MgtTool\Wzcnflct-2=MgtTool\Wzcnflct\WzcnOthr
> MgtTool\Wzcnflct-3=MgtTool\Wzcnflct\WzcnCmn
> MgtTool-type=string
> MgtTool-count=7
> MgtTool-0=MgtTool\SEM
> MgtTool-1=MgtTool\Profiler
> MgtTool-2=MgtTool\Qryanlz
> MgtTool-3=MgtTool\DTCCLi
> MgtTool-4=MgtTool\Wzcnflct
> MgtTool-5=MgtTool\UtilSys
> MgtTool-6=MgtTool\UtilBinn
> Connect-type=string
> Connect-count=3
> Connect-0=Connect\ConnSys
> Connect-1=Connect\Conn9x
> Connect-2=Connect\ConnNT
> Books\Bookso-type=string
> Books\Bookso-count=1
> Books\Bookso-0=Books\Bookso\Utils
> Books\BooksCD-type=string
> Books\BooksCD-count=1
> Books\BooksCD-0=Books\BooksCD\Utils
> Books-type=string
> Books-count=2
> Books-0=Books\Bookso
> Books-1=Books\BooksCD
> DevTools\Dbg Int-type=string
> DevTools\Dbg Int-count=2
> DevTools\Dbg Int-0=DevTools\Dbg Int\Dbg Int Common
> DevTools\Dbg Int-1=DevTools\Dbg Int\EXE
> DevTools-type=string
> DevTools-count=1
> DevTools-0=DevTools\Dbg Int
> CoreRepl-type=string
> CoreRepl-count=2
> CoreRepl-0=CoreRepl\Res1033
> CoreRepl-1=CoreRepl\ResIntl
> Repostry-type=string
> Repostry-count=3
> Repostry-0=Repostry\RepstSys
> Repostry-1=Repostry\Res1033
> Repostry-2=Repostry\ResIntl
> CoreMisc\ActiveX-type=string
> CoreMisc\ActiveX-count=2
> CoreMisc\ActiveX-0=CoreMisc\ActiveX\Res1033
> CoreMisc\ActiveX-1=CoreMisc\ActiveX\ResIntl
> CoreMisc-type=string
> CoreMisc-count=2
> CoreMisc-0=CoreMisc\ActiveX
> CoreMisc-1=CoreMisc\Res1033
> Monarch-type=string
> Monarch-count=2
> Monarch-0=Monarch\Monr1033
> Monarch-1=Monarch\MonrIntl
> CoreCOM-type=string
> CoreCOM-count=2
> CoreCOM-0=CoreCOM\Res1033
> CoreCOM-1=CoreCOM\ResIntl
> CoreTool-type=string
> CoreTool-count=2
> CoreTool-0=CoreTool\Res1033
> CoreTool-1=CoreTool\ResOther
> SFExt\ActiveX-type=string
> SFExt\ActiveX-count=2
> SFExt\ActiveX-0=SFExt\ActiveX\Res1033
> SFExt\ActiveX-1=SFExt\ActiveX\ResIntl
> SFExt-type=string
> SFExt-count=3
> SFExt-0=SFExt\ActiveX
> SFExt-1=SFExt\Res1033
> SFExt-2=SFExt\ResIntl
> Trace-type=string
> Trace-count=2
> Trace-0=Trace\Res1033
> Trace-1=Trace\ResOther
> MC-type=string
> MC-count=3
> MC-0=MC\MC1033
> MC-1=MC\MCIntl
> MC-2=MC\Help
> DTSUI-type=string
> DTSUI-count=2
> DTSUI-0=DTSUI\Res1033
> DTSUI-1=DTSUI\ResIntl
> MSOlap-type=string
> MSOlap-count=2
> MSOlap-0=MSOlap\Res1033
> MSOlap-1=MSOlap\ResIntl
> ATL-type=string
> ATL-count=2
> ATL-0=ATL\winnt
> ATL-1=ATL\win9x
> Component-type=string
> Component-count=21
> Component-0=MgtTool
> Component-1=Connect
> Component-2=Books
> Component-3=DevTools
> Component-4=CoreRepl
> Component-5=Repostry
> Component-6=CoreMisc
> Component-7=Monarch
> Component-8=CoreCOM
> Component-9=CoreTool
> Component-10=DBLibCli
> Component-11=SFExt
> Component-12=Trace
> Component-13=MiscCore
> Component-14=MC
> Component-15=DTSUI
> Component-16=MSOlap
> Component-17=ATL
> Component-18=MFC42U
> Component-19=VC
> Component-20=VB
> Result=1
>
> Simon Worth wrote:
installs.[vbcol=seagreen]

Query analyzer...

I was wondering if there is any way I can find/make an install of ONLY
the client tools (isqlw, etc.) so that I don't have to pass out the
Server install CD all the time? Or maybe just grab all the files needed
and know where to put them...
Our programmers insist on installing that for everyone and their dog so
I'd like to just put it somewhere on the network or on a CD so it can be
accessible easily.
TIA!!Follow the directions within SQLCLI.BAT on the install disk, and check the
SQLCLI.ISS file for info on what gets installed.
--
Simon Worth
"Jesse Gardner" <admin_deleteth1s@.badcrc.com> wrote in message
news:38rhshF5q49adU1@.individual.net...
> I was wondering if there is any way I can find/make an install of ONLY
> the client tools (isqlw, etc.) so that I don't have to pass out the
> Server install CD all the time? Or maybe just grab all the files needed
> and know where to put them...
> Our programmers insist on installing that for everyone and their dog so
> I'd like to just put it somewhere on the network or on a CD so it can be
> accessible easily.
>
> TIA!!|||Sorry, forgot this part
start /wait x86\setup\setupsql.exe -s -m -SMS -f1 "sqlcli.iss"
That's what the batch file installs for unattended client tools installs.
--
Simon Worth
"Jesse Gardner" <admin_deleteth1s@.badcrc.com> wrote in message
news:38rhshF5q49adU1@.individual.net...
> I was wondering if there is any way I can find/make an install of ONLY
> the client tools (isqlw, etc.) so that I don't have to pass out the
> Server install CD all the time? Or maybe just grab all the files needed
> and know where to put them...
> Our programmers insist on installing that for everyone and their dog so
> I'd like to just put it somewhere on the network or on a CD so it can be
> accessible easily.
>
> TIA!!|||You ROCK!
Simon Worth wrote:
> Sorry, forgot this part
> start /wait x86\setup\setupsql.exe -s -m -SMS -f1 "sqlcli.iss"
> That's what the batch file installs for unattended client tools installs.
>|||I do have one question though... What points to what files? This is
what I'm seeing:
[SQLComponentMult-0]
MgtTool\SEM\ActiveX-type=string
MgtTool\SEM\ActiveX-count=2
MgtTool\SEM\ActiveX-0=MgtTool\SEM\ActiveX\Res1033
MgtTool\SEM\ActiveX-1=MgtTool\SEM\ActiveX\ResIntl
MgtTool\SEM\Office-type=string
MgtTool\SEM\Office-count=2
MgtTool\SEM\Office-0=MgtTool\SEM\Office\Res1033
MgtTool\SEM\Office-1=MgtTool\SEM\Office\ResIntl
MgtTool\SEM-type=string
MgtTool\SEM-count=12
MgtTool\SEM-0=MgtTool\SEM\HTML
MgtTool\SEM-1=MgtTool\SEM\MSD98
MgtTool\SEM-2=MgtTool\SEM\MSD98SYS
MgtTool\SEM-3=MgtTool\SEM\MSD98Res
MgtTool\SEM-4=MgtTool\SEM\MSD98Hlp
MgtTool\SEM-5=MgtTool\SEM\Help
MgtTool\SEM-6=MgtTool\SEM\Res1033
MgtTool\SEM-7=MgtTool\SEM\ResIntl
MgtTool\SEM-8=MgtTool\SEM\MSD98RsI
MgtTool\SEM-9=MgtTool\SEM\ActiveX
MgtTool\SEM-10=MgtTool\SEM\Office
MgtTool\SEM-11=MgtTool\SEM\Scripts
MgtTool\Profiler-type=string
MgtTool\Profiler-count=3
MgtTool\Profiler-0=MgtTool\Profiler\Help
MgtTool\Profiler-1=MgtTool\Profiler\Res1033
MgtTool\Profiler-2=MgtTool\Profiler\ResIntl
MgtTool\Qryanlz-type=string
MgtTool\Qryanlz-count=3
MgtTool\Qryanlz-0=MgtTool\Qryanlz\Help
MgtTool\Qryanlz-1=MgtTool\Qryanlz\Res1033
MgtTool\Qryanlz-2=MgtTool\Qryanlz\ResIntl
MgtTool\Wzcnflct-type=string
MgtTool\Wzcnflct-count=4
MgtTool\Wzcnflct-0=MgtTool\Wzcnflct\WzcnHlp
MgtTool\Wzcnflct-1=MgtTool\Wzcnflct\Wzcn1033
MgtTool\Wzcnflct-2=MgtTool\Wzcnflct\WzcnOthr
MgtTool\Wzcnflct-3=MgtTool\Wzcnflct\WzcnCmn
MgtTool-type=string
MgtTool-count=7
MgtTool-0=MgtTool\SEM
MgtTool-1=MgtTool\Profiler
MgtTool-2=MgtTool\Qryanlz
MgtTool-3=MgtTool\DTCCLi
MgtTool-4=MgtTool\Wzcnflct
MgtTool-5=MgtTool\UtilSys
MgtTool-6=MgtTool\UtilBinn
Connect-type=string
Connect-count=3
Connect-0=Connect\ConnSys
Connect-1=Connect\Conn9x
Connect-2=Connect\ConnNT
Books\Bookso-type=string
Books\Bookso-count=1
Books\Bookso-0=Books\Bookso\Utils
Books\BooksCD-type=string
Books\BooksCD-count=1
Books\BooksCD-0=Books\BooksCD\Utils
Books-type=string
Books-count=2
Books-0=Books\Bookso
Books-1=Books\BooksCD
DevTools\Dbg Int-type=string
DevTools\Dbg Int-count=2
DevTools\Dbg Int-0=DevTools\Dbg Int\Dbg Int Common
DevTools\Dbg Int-1=DevTools\Dbg Int\EXE
DevTools-type=string
DevTools-count=1
DevTools-0=DevTools\Dbg Int
CoreRepl-type=string
CoreRepl-count=2
CoreRepl-0=CoreRepl\Res1033
CoreRepl-1=CoreRepl\ResIntl
Repostry-type=string
Repostry-count=3
Repostry-0=Repostry\RepstSys
Repostry-1=Repostry\Res1033
Repostry-2=Repostry\ResIntl
CoreMisc\ActiveX-type=string
CoreMisc\ActiveX-count=2
CoreMisc\ActiveX-0=CoreMisc\ActiveX\Res1033
CoreMisc\ActiveX-1=CoreMisc\ActiveX\ResIntl
CoreMisc-type=string
CoreMisc-count=2
CoreMisc-0=CoreMisc\ActiveX
CoreMisc-1=CoreMisc\Res1033
Monarch-type=string
Monarch-count=2
Monarch-0=Monarch\Monr1033
Monarch-1=Monarch\MonrIntl
CoreCOM-type=string
CoreCOM-count=2
CoreCOM-0=CoreCOM\Res1033
CoreCOM-1=CoreCOM\ResIntl
CoreTool-type=string
CoreTool-count=2
CoreTool-0=CoreTool\Res1033
CoreTool-1=CoreTool\ResOther
SFExt\ActiveX-type=string
SFExt\ActiveX-count=2
SFExt\ActiveX-0=SFExt\ActiveX\Res1033
SFExt\ActiveX-1=SFExt\ActiveX\ResIntl
SFExt-type=string
SFExt-count=3
SFExt-0=SFExt\ActiveX
SFExt-1=SFExt\Res1033
SFExt-2=SFExt\ResIntl
Trace-type=string
Trace-count=2
Trace-0=Trace\Res1033
Trace-1=Trace\ResOther
MC-type=string
MC-count=3
MC-0=MC\MC1033
MC-1=MC\MCIntl
MC-2=MC\Help
DTSUI-type=string
DTSUI-count=2
DTSUI-0=DTSUI\Res1033
DTSUI-1=DTSUI\ResIntl
MSOlap-type=string
MSOlap-count=2
MSOlap-0=MSOlap\Res1033
MSOlap-1=MSOlap\ResIntl
ATL-type=string
ATL-count=2
ATL-0=ATL\winnt
ATL-1=ATL\win9x
Component-type=string
Component-count=21
Component-0=MgtTool
Component-1=Connect
Component-2=Books
Component-3=DevTools
Component-4=CoreRepl
Component-5=Repostry
Component-6=CoreMisc
Component-7=Monarch
Component-8=CoreCOM
Component-9=CoreTool
Component-10=DBLibCli
Component-11=SFExt
Component-12=Trace
Component-13=MiscCore
Component-14=MC
Component-15=DTSUI
Component-16=MSOlap
Component-17=ATL
Component-18=MFC42U
Component-19=VC
Component-20=VB
Result=1
Simon Worth wrote:
> Sorry, forgot this part
> start /wait x86\setup\setupsql.exe -s -m -SMS -f1 "sqlcli.iss"
> That's what the batch file installs for unattended client tools installs.
>|||That's not going to list what files are required to do an install - that
lists the requriments for the process to complete. Sorry about that, I
didn't mean to indicate the ISS file would list the files needed. That's
handled by the installer.
--
Simon Worth
"Jesse Gardner" <admin_deleteth1s@.badcrc.com> wrote in message
news:38rmmfF5ndtkhU1@.individual.net...
> I do have one question though... What points to what files? This is
> what I'm seeing:
> [SQLComponentMult-0]
> MgtTool\SEM\ActiveX-type=string
> MgtTool\SEM\ActiveX-count=2
> MgtTool\SEM\ActiveX-0=MgtTool\SEM\ActiveX\Res1033
> MgtTool\SEM\ActiveX-1=MgtTool\SEM\ActiveX\ResIntl
> MgtTool\SEM\Office-type=string
> MgtTool\SEM\Office-count=2
> MgtTool\SEM\Office-0=MgtTool\SEM\Office\Res1033
> MgtTool\SEM\Office-1=MgtTool\SEM\Office\ResIntl
> MgtTool\SEM-type=string
> MgtTool\SEM-count=12
> MgtTool\SEM-0=MgtTool\SEM\HTML
> MgtTool\SEM-1=MgtTool\SEM\MSD98
> MgtTool\SEM-2=MgtTool\SEM\MSD98SYS
> MgtTool\SEM-3=MgtTool\SEM\MSD98Res
> MgtTool\SEM-4=MgtTool\SEM\MSD98Hlp
> MgtTool\SEM-5=MgtTool\SEM\Help
> MgtTool\SEM-6=MgtTool\SEM\Res1033
> MgtTool\SEM-7=MgtTool\SEM\ResIntl
> MgtTool\SEM-8=MgtTool\SEM\MSD98RsI
> MgtTool\SEM-9=MgtTool\SEM\ActiveX
> MgtTool\SEM-10=MgtTool\SEM\Office
> MgtTool\SEM-11=MgtTool\SEM\Scripts
> MgtTool\Profiler-type=string
> MgtTool\Profiler-count=3
> MgtTool\Profiler-0=MgtTool\Profiler\Help
> MgtTool\Profiler-1=MgtTool\Profiler\Res1033
> MgtTool\Profiler-2=MgtTool\Profiler\ResIntl
> MgtTool\Qryanlz-type=string
> MgtTool\Qryanlz-count=3
> MgtTool\Qryanlz-0=MgtTool\Qryanlz\Help
> MgtTool\Qryanlz-1=MgtTool\Qryanlz\Res1033
> MgtTool\Qryanlz-2=MgtTool\Qryanlz\ResIntl
> MgtTool\Wzcnflct-type=string
> MgtTool\Wzcnflct-count=4
> MgtTool\Wzcnflct-0=MgtTool\Wzcnflct\WzcnHlp
> MgtTool\Wzcnflct-1=MgtTool\Wzcnflct\Wzcn1033
> MgtTool\Wzcnflct-2=MgtTool\Wzcnflct\WzcnOthr
> MgtTool\Wzcnflct-3=MgtTool\Wzcnflct\WzcnCmn
> MgtTool-type=string
> MgtTool-count=7
> MgtTool-0=MgtTool\SEM
> MgtTool-1=MgtTool\Profiler
> MgtTool-2=MgtTool\Qryanlz
> MgtTool-3=MgtTool\DTCCLi
> MgtTool-4=MgtTool\Wzcnflct
> MgtTool-5=MgtTool\UtilSys
> MgtTool-6=MgtTool\UtilBinn
> Connect-type=string
> Connect-count=3
> Connect-0=Connect\ConnSys
> Connect-1=Connect\Conn9x
> Connect-2=Connect\ConnNT
> Books\Bookso-type=string
> Books\Bookso-count=1
> Books\Bookso-0=Books\Bookso\Utils
> Books\BooksCD-type=string
> Books\BooksCD-count=1
> Books\BooksCD-0=Books\BooksCD\Utils
> Books-type=string
> Books-count=2
> Books-0=Books\Bookso
> Books-1=Books\BooksCD
> DevTools\Dbg Int-type=string
> DevTools\Dbg Int-count=2
> DevTools\Dbg Int-0=DevTools\Dbg Int\Dbg Int Common
> DevTools\Dbg Int-1=DevTools\Dbg Int\EXE
> DevTools-type=string
> DevTools-count=1
> DevTools-0=DevTools\Dbg Int
> CoreRepl-type=string
> CoreRepl-count=2
> CoreRepl-0=CoreRepl\Res1033
> CoreRepl-1=CoreRepl\ResIntl
> Repostry-type=string
> Repostry-count=3
> Repostry-0=Repostry\RepstSys
> Repostry-1=Repostry\Res1033
> Repostry-2=Repostry\ResIntl
> CoreMisc\ActiveX-type=string
> CoreMisc\ActiveX-count=2
> CoreMisc\ActiveX-0=CoreMisc\ActiveX\Res1033
> CoreMisc\ActiveX-1=CoreMisc\ActiveX\ResIntl
> CoreMisc-type=string
> CoreMisc-count=2
> CoreMisc-0=CoreMisc\ActiveX
> CoreMisc-1=CoreMisc\Res1033
> Monarch-type=string
> Monarch-count=2
> Monarch-0=Monarch\Monr1033
> Monarch-1=Monarch\MonrIntl
> CoreCOM-type=string
> CoreCOM-count=2
> CoreCOM-0=CoreCOM\Res1033
> CoreCOM-1=CoreCOM\ResIntl
> CoreTool-type=string
> CoreTool-count=2
> CoreTool-0=CoreTool\Res1033
> CoreTool-1=CoreTool\ResOther
> SFExt\ActiveX-type=string
> SFExt\ActiveX-count=2
> SFExt\ActiveX-0=SFExt\ActiveX\Res1033
> SFExt\ActiveX-1=SFExt\ActiveX\ResIntl
> SFExt-type=string
> SFExt-count=3
> SFExt-0=SFExt\ActiveX
> SFExt-1=SFExt\Res1033
> SFExt-2=SFExt\ResIntl
> Trace-type=string
> Trace-count=2
> Trace-0=Trace\Res1033
> Trace-1=Trace\ResOther
> MC-type=string
> MC-count=3
> MC-0=MC\MC1033
> MC-1=MC\MCIntl
> MC-2=MC\Help
> DTSUI-type=string
> DTSUI-count=2
> DTSUI-0=DTSUI\Res1033
> DTSUI-1=DTSUI\ResIntl
> MSOlap-type=string
> MSOlap-count=2
> MSOlap-0=MSOlap\Res1033
> MSOlap-1=MSOlap\ResIntl
> ATL-type=string
> ATL-count=2
> ATL-0=ATL\winnt
> ATL-1=ATL\win9x
> Component-type=string
> Component-count=21
> Component-0=MgtTool
> Component-1=Connect
> Component-2=Books
> Component-3=DevTools
> Component-4=CoreRepl
> Component-5=Repostry
> Component-6=CoreMisc
> Component-7=Monarch
> Component-8=CoreCOM
> Component-9=CoreTool
> Component-10=DBLibCli
> Component-11=SFExt
> Component-12=Trace
> Component-13=MiscCore
> Component-14=MC
> Component-15=DTSUI
> Component-16=MSOlap
> Component-17=ATL
> Component-18=MFC42U
> Component-19=VC
> Component-20=VB
> Result=1
>
> Simon Worth wrote:
> > Sorry, forgot this part
> > start /wait x86\setup\setupsql.exe -s -m -SMS -f1 "sqlcli.iss"
> > That's what the batch file installs for unattended client tools
installs.
> >

Query Analyzer..

Hi,
I am trying to write some queries in SQL Server 2005.
Is there any option like query analyzer?
Please guide me out..
Reg
ArijitUse SQL Server Management Studio (SSMS).
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada tom@.cips.ca
www.pinpub.com
"Arijit" <arijit77@.gmail.com> wrote in message
news:1133700925.182636.231720@.g44g2000cwa.googlegroups.com...
> Hi,
> I am trying to write some queries in SQL Server 2005.
> Is there any option like query analyzer?
> Please guide me out..
> Reg
> Arijit
>|||Hi
In SQL Server Management Studio you have the New Query button or the
File/New/Database Engine Query options to give you a query window. Under
Tools/Options you have a range of settings for Query Execution.
You may want to look at the virtual lab "SQL Server 2005 Introduction to SQL
Server Management Studio" at
http://msdn.microsoft.com/vstudio/t...ql/default.aspx for an
introduction on how to use it.
John
"Arijit" <arijit77@.gmail.com> wrote in message
news:1133700925.182636.231720@.g44g2000cwa.googlegroups.com...
> Hi,
> I am trying to write some queries in SQL Server 2005.
> Is there any option like query analyzer?
> Please guide me out..
> Reg
> Arijit
>|||Arijit wrote:

> Hi,
> I am trying to write some queries in SQL Server 2005.
> Is there any option like query analyzer?
> Please guide me out..
> Reg
> Arijit
Management Studio. You can also still use SQL Server 2000 Query
Analyzer for many things. Some of the GUI features won't work but for
straight TSQL development it's just fine.
David Portas
SQL Server MVP
--|||VS 2005 also has it and it stays up instead of closing and poking the select
text in your window as SSMS does (unless I missed something in SSMS which is
likely). See the server explorer or new "Database project" in VS2005. An
interesting note is that a "SQL Server Project" will not give you this query
designer. I can only assume because that is geared for clr projects. But
it would have been nice to be able to use QA within that project and also be
able to just "Run" (instead of debug) queries to see the grid results pane.
William Stacey [MVP]
"Arijit" <arijit77@.gmail.com> wrote in message
news:1133700925.182636.231720@.g44g2000cwa.googlegroups.com...
> Hi,
> I am trying to write some queries in SQL Server 2005.
> Is there any option like query analyzer?
> Please guide me out..
> Reg
> Arijit
>|||William Stacey [MVP] (william.stacey@.gmail.com) writes:
> VS 2005 also has it and it stays up instead of closing and poking the
> select text in your window as SSMS does (unless I missed something in
> SSMS which is likely). See the server explorer or new "Database
> project" in VS2005. An interesting note is that a "SQL Server Project"
> will not give you this query designer. I can only assume because that
> is geared for clr projects. But it would have been nice to be able to
> use QA within that project and also be able to just "Run" (instead of
> debug) queries to see the grid results pane.
He asked about Query Analyzer, not Query Designer. The Query Designer
certainly deserves its name: it designs the queries according to its own
idea, and queries often come out with a different meaning than they
entered. Certainly nothing to recommend.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx