Hello,
I've installed new CTP June of SQL2005. And I'd like to create new report in
reporting services with connection to Analysis Services 2000.
So, I've created datasource, looks fine, test connection succeeded. When I'm
starting to create report, after selecting datasource, when I click on
"Query Designer"
I get following message:
"The query designer could not be loaded.
Verify your connection string and query string or enter a valid query to
continue."
Where is the problem?
Best regards
Piotr TrêbaczMake sure you add ConnectTo=8.0 to the connection string
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Piotr Trêbacz" <ptrebacz@.kruk-inkaso.com.pl> wrote in message
news:uJ8n5WvdFHA.2124@.TK2MSFTNGP14.phx.gbl...
> Hello,
> I've installed new CTP June of SQL2005. And I'd like to create new report
> in
> reporting services with connection to Analysis Services 2000.
> So, I've created datasource, looks fine, test connection succeeded. When
> I'm
> starting to create report, after selecting datasource, when I click on
> "Query Designer"
> I get following message:
> "The query designer could not be loaded.
> Verify your connection string and query string or enter a valid query to
> continue."
> Where is the problem?
> Best regards
> Piotr Trêbacz
>|||> Make sure you add ConnectTo=8.0 to the connection string
It works, great, big thanks. I wonder why MS people didn't mention this when
I ask few times:)
Thanks again
Reagards
Piotr
Showing posts with label installed. Show all posts
Showing posts with label installed. Show all posts
Friday, March 9, 2012
Query data is very slow
Dear all,
I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
leased line 128 Kbps. The distance between HO and client side is 10 miles.
Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
30 seconds.
The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
If I execute the SQL from the HO computer, it just takes time 4 seconds.
What can I do to fix the problem ?
Thanks.
Regards,
Vensia
> What can I do to fix the problem ?
1) add a WHERE clause to your query
2) request only the columns needed instead of all columns
3) get a faster network connection
Hope this helps.
Dan Guzman
SQL Server MVP
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> Mb). The client side (Pentium 4, memory 256 Mb) connect to the server
> using
> leased line 128 Kbps. The distance between HO and client side is 10 miles.
> Using Query Analyzer, to retrieve 40.000 records, it takes time about 4
> min
> 30 seconds.
> The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> If I execute the SQL from the HO computer, it just takes time 4 seconds.
> What can I do to fix the problem ?
> Thanks.
> Regards,
> Vensia
>
>
|||I second the suggestions given by Dan.
A where clause reduces the search time and the query will work faster if you
use an insexed coloumn in the where clause.
Specifying the name of the coloumn that you need will reduce the time taken
to retireve the extra not-needed coloumns.
A faster n/w conn is usually preferred :-D
Also do check whether any other query is applying any locks on the table !!!!
Thanks
Amer M J
MCP
"Dan Guzman" wrote:
> 1) add a WHERE clause to your query
> 2) request only the columns needed instead of all columns
> 3) get a faster network connection
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
> news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
>
>
|||Actually I have added the where clause in the application and index in the
table.
The user reported to me that it takes a long time to open Invoice form.
At the server side, the invoice form can be opened in several seconds but at
the client side (10 miles from the server), it takes minutes to open the
form.
Then I use Query Analyzer to run SQL statement "SELECT * FROM
tblInvoiceMain" to check the execution time.
From the PC at server side, it takes only 4 seconds but at the client side,
it takes 4 minutes 30 seconds.
I just wonder if there is something wrong with the database setting.
Anyway, is there any relation with the log file size ? How to truncate the
log file in SQL Server 2000 ?
Thanks.
"Amer M J" <AmerMJ@.discussions.microsoft.com> wrote in message
news:5F35A98F-EBBA-4F86-B8D5-F06CA84BAE0E@.microsoft.com...
> I second the suggestions given by Dan.
> A where clause reduces the search time and the query will work faster if
you
> use an insexed coloumn in the where clause.
> Specifying the name of the coloumn that you need will reduce the time
taken
> to retireve the extra not-needed coloumns.
> A faster n/w conn is usually preferred :-D
> Also do check whether any other query is applying any locks on the table
!!!![vbcol=seagreen]
> Thanks
> Amer M J
> MCP
> "Dan Guzman" wrote:
512[vbcol=seagreen]
miles.[vbcol=seagreen]
4[vbcol=seagreen]
seconds.[vbcol=seagreen]
|||Hi
It has nothing to do with SQL Server. It is your network that is the
problem.
128Kbps = 16 kilo bytes per second. The practical throughput on your line,
assuming there is nothing else using it is about 10 kilo bytes per second.
If each row returned is 2'000 bytes, you can only transfer 5 rows per second
over the line.
And you are moving 40'000. Work that out.
The fact that the performance is acceptable when accessed locally indicates
at a glance your have network performance problems.
In a true n-tier application, there should be no reason to move 40'000 rows
around. I would seriously look at how your application and data access are
architected.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:Oa2tQYcCGHA.1232@.TK2MSFTNGP10.phx.gbl...
> Actually I have added the where clause in the application and index in
> the
> table.
> The user reported to me that it takes a long time to open Invoice form.
> At the server side, the invoice form can be opened in several seconds but
> at
> the client side (10 miles from the server), it takes minutes to open the
> form.
> Then I use Query Analyzer to run SQL statement "SELECT * FROM
> tblInvoiceMain" to check the execution time.
> From the PC at server side, it takes only 4 seconds but at the client
> side,
> it takes 4 minutes 30 seconds.
> I just wonder if there is something wrong with the database setting.
> Anyway, is there any relation with the log file size ? How to truncate the
> log file in SQL Server 2000 ?
> Thanks.
> "Amer M J" <AmerMJ@.discussions.microsoft.com> wrote in message
> news:5F35A98F-EBBA-4F86-B8D5-F06CA84BAE0E@.microsoft.com...
> you
> taken
> !!!!
> 512
> miles.
> 4
> seconds.
>
I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
leased line 128 Kbps. The distance between HO and client side is 10 miles.
Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
30 seconds.
The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
If I execute the SQL from the HO computer, it just takes time 4 seconds.
What can I do to fix the problem ?
Thanks.
Regards,
Vensia
> What can I do to fix the problem ?
1) add a WHERE clause to your query
2) request only the columns needed instead of all columns
3) get a faster network connection
Hope this helps.
Dan Guzman
SQL Server MVP
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> Mb). The client side (Pentium 4, memory 256 Mb) connect to the server
> using
> leased line 128 Kbps. The distance between HO and client side is 10 miles.
> Using Query Analyzer, to retrieve 40.000 records, it takes time about 4
> min
> 30 seconds.
> The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> If I execute the SQL from the HO computer, it just takes time 4 seconds.
> What can I do to fix the problem ?
> Thanks.
> Regards,
> Vensia
>
>
|||I second the suggestions given by Dan.
A where clause reduces the search time and the query will work faster if you
use an insexed coloumn in the where clause.
Specifying the name of the coloumn that you need will reduce the time taken
to retireve the extra not-needed coloumns.
A faster n/w conn is usually preferred :-D
Also do check whether any other query is applying any locks on the table !!!!
Thanks
Amer M J
MCP
"Dan Guzman" wrote:
> 1) add a WHERE clause to your query
> 2) request only the columns needed instead of all columns
> 3) get a faster network connection
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
> news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
>
>
|||Actually I have added the where clause in the application and index in the
table.
The user reported to me that it takes a long time to open Invoice form.
At the server side, the invoice form can be opened in several seconds but at
the client side (10 miles from the server), it takes minutes to open the
form.
Then I use Query Analyzer to run SQL statement "SELECT * FROM
tblInvoiceMain" to check the execution time.
From the PC at server side, it takes only 4 seconds but at the client side,
it takes 4 minutes 30 seconds.
I just wonder if there is something wrong with the database setting.
Anyway, is there any relation with the log file size ? How to truncate the
log file in SQL Server 2000 ?
Thanks.
"Amer M J" <AmerMJ@.discussions.microsoft.com> wrote in message
news:5F35A98F-EBBA-4F86-B8D5-F06CA84BAE0E@.microsoft.com...
> I second the suggestions given by Dan.
> A where clause reduces the search time and the query will work faster if
you
> use an insexed coloumn in the where clause.
> Specifying the name of the coloumn that you need will reduce the time
taken
> to retireve the extra not-needed coloumns.
> A faster n/w conn is usually preferred :-D
> Also do check whether any other query is applying any locks on the table
!!!![vbcol=seagreen]
> Thanks
> Amer M J
> MCP
> "Dan Guzman" wrote:
512[vbcol=seagreen]
miles.[vbcol=seagreen]
4[vbcol=seagreen]
seconds.[vbcol=seagreen]
|||Hi
It has nothing to do with SQL Server. It is your network that is the
problem.
128Kbps = 16 kilo bytes per second. The practical throughput on your line,
assuming there is nothing else using it is about 10 kilo bytes per second.
If each row returned is 2'000 bytes, you can only transfer 5 rows per second
over the line.
And you are moving 40'000. Work that out.
The fact that the performance is acceptable when accessed locally indicates
at a glance your have network performance problems.
In a true n-tier application, there should be no reason to move 40'000 rows
around. I would seriously look at how your application and data access are
architected.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:Oa2tQYcCGHA.1232@.TK2MSFTNGP10.phx.gbl...
> Actually I have added the where clause in the application and index in
> the
> table.
> The user reported to me that it takes a long time to open Invoice form.
> At the server side, the invoice form can be opened in several seconds but
> at
> the client side (10 miles from the server), it takes minutes to open the
> form.
> Then I use Query Analyzer to run SQL statement "SELECT * FROM
> tblInvoiceMain" to check the execution time.
> From the PC at server side, it takes only 4 seconds but at the client
> side,
> it takes 4 minutes 30 seconds.
> I just wonder if there is something wrong with the database setting.
> Anyway, is there any relation with the log file size ? How to truncate the
> log file in SQL Server 2000 ?
> Thanks.
> "Amer M J" <AmerMJ@.discussions.microsoft.com> wrote in message
> news:5F35A98F-EBBA-4F86-B8D5-F06CA84BAE0E@.microsoft.com...
> you
> taken
> !!!!
> 512
> miles.
> 4
> seconds.
>
Query data is very slow
Dear all,
I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
leased line 128 Kbps. The distance between HO and client side is 10 miles.
Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
30 seconds.
The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
If I execute the SQL from the HO computer, it just takes time 4 seconds.
What can I do to fix the problem ?
Thanks.
Regards,
Vensia
A prime place to being looking is the network bandwidth..
1. try doing this query from another computer close to the server (avoiding
the 128K line.)
If the response is good begin investigating the load this is placing on the
128k line..
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Vensia" wrote:
> Dear all,
> I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
> leased line 128 Kbps. The distance between HO and client side is 10 miles.
> Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
> 30 seconds.
> The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> If I execute the SQL from the HO computer, it just takes time 4 seconds.
> What can I do to fix the problem ?
> Thanks.
> Regards,
> Vensia
>
>
I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
leased line 128 Kbps. The distance between HO and client side is 10 miles.
Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
30 seconds.
The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
If I execute the SQL from the HO computer, it just takes time 4 seconds.
What can I do to fix the problem ?
Thanks.
Regards,
Vensia
A prime place to being looking is the network bandwidth..
1. try doing this query from another computer close to the server (avoiding
the 128K line.)
If the response is good begin investigating the load this is placing on the
128k line..
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Vensia" wrote:
> Dear all,
> I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
> leased line 128 Kbps. The distance between HO and client side is 10 miles.
> Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
> 30 seconds.
> The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> If I execute the SQL from the HO computer, it just takes time 4 seconds.
> What can I do to fix the problem ?
> Thanks.
> Regards,
> Vensia
>
>
Query data is very slow
Dear all,
I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
leased line 128 Kbps. The distance between HO and client side is 10 miles.
Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
30 seconds.
The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
If I execute the SQL from the HO computer, it just takes time 4 seconds.
What can I do to fix the problem ?
Thanks.
Regards,
VensiaA prime place to being looking is the network bandwidth..
1. try doing this query from another computer close to the server (avoiding
the 128K line.)
If the response is good begin investigating the load this is placing on the
128k line..
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Vensia" wrote:
> Dear all,
> I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
> leased line 128 Kbps. The distance between HO and client side is 10 miles.
> Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
> 30 seconds.
> The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> If I execute the SQL from the HO computer, it just takes time 4 seconds.
> What can I do to fix the problem ?
> Thanks.
> Regards,
> Vensia
>
>
I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
leased line 128 Kbps. The distance between HO and client side is 10 miles.
Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
30 seconds.
The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
If I execute the SQL from the HO computer, it just takes time 4 seconds.
What can I do to fix the problem ?
Thanks.
Regards,
VensiaA prime place to being looking is the network bandwidth..
1. try doing this query from another computer close to the server (avoiding
the 128K line.)
If the response is good begin investigating the load this is placing on the
128k line..
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Vensia" wrote:
> Dear all,
> I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
> leased line 128 Kbps. The distance between HO and client side is 10 miles.
> Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
> 30 seconds.
> The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> If I execute the SQL from the HO computer, it just takes time 4 seconds.
> What can I do to fix the problem ?
> Thanks.
> Regards,
> Vensia
>
>
Query data is very slow
Dear all,
I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
leased line 128 Kbps. The distance between HO and client side is 10 miles.
Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
30 seconds.
The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
If I execute the SQL from the HO computer, it just takes time 4 seconds.
What can I do to fix the problem ?
Thanks.
Regards,
Vensia> What can I do to fix the problem ?
1) add a WHERE clause to your query
2) request only the columns needed instead of all columns
3) get a faster network connection
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> Mb). The client side (Pentium 4, memory 256 Mb) connect to the server
> using
> leased line 128 Kbps. The distance between HO and client side is 10 miles.
> Using Query Analyzer, to retrieve 40.000 records, it takes time about 4
> min
> 30 seconds.
> The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> If I execute the SQL from the HO computer, it just takes time 4 seconds.
> What can I do to fix the problem ?
> Thanks.
> Regards,
> Vensia
>
>|||I second the suggestions given by Dan.
A where clause reduces the search time and the query will work faster if you
use an insexed coloumn in the where clause.
Specifying the name of the coloumn that you need will reduce the time taken
to retireve the extra not-needed coloumns.
A faster n/w conn is usually preferred :-D
Also do check whether any other query is applying any locks on the table !!!!
Thanks
Amer M J
MCP
"Dan Guzman" wrote:
> > What can I do to fix the problem ?
> 1) add a WHERE clause to your query
> 2) request only the columns needed instead of all columns
> 3) get a faster network connection
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
> news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> > Dear all,
> >
> > I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> > Mb). The client side (Pentium 4, memory 256 Mb) connect to the server
> > using
> > leased line 128 Kbps. The distance between HO and client side is 10 miles.
> > Using Query Analyzer, to retrieve 40.000 records, it takes time about 4
> > min
> > 30 seconds.
> > The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> > If I execute the SQL from the HO computer, it just takes time 4 seconds.
> > What can I do to fix the problem ?
> > Thanks.
> >
> > Regards,
> > Vensia
> >
> >
> >
>
>|||Actually I have added the where clause in the application and index in the
table.
The user reported to me that it takes a long time to open Invoice form.
At the server side, the invoice form can be opened in several seconds but at
the client side (10 miles from the server), it takes minutes to open the
form.
Then I use Query Analyzer to run SQL statement "SELECT * FROM
tblInvoiceMain" to check the execution time.
From the PC at server side, it takes only 4 seconds but at the client side,
it takes 4 minutes 30 seconds.
I just wonder if there is something wrong with the database setting.
Anyway, is there any relation with the log file size ? How to truncate the
log file in SQL Server 2000 ?
Thanks.
"Amer M J" <AmerMJ@.discussions.microsoft.com> wrote in message
news:5F35A98F-EBBA-4F86-B8D5-F06CA84BAE0E@.microsoft.com...
> I second the suggestions given by Dan.
> A where clause reduces the search time and the query will work faster if
you
> use an insexed coloumn in the where clause.
> Specifying the name of the coloumn that you need will reduce the time
taken
> to retireve the extra not-needed coloumns.
> A faster n/w conn is usually preferred :-D
> Also do check whether any other query is applying any locks on the table
!!!!
> Thanks
> Amer M J
> MCP
> "Dan Guzman" wrote:
> > > What can I do to fix the problem ?
> >
> > 1) add a WHERE clause to your query
> >
> > 2) request only the columns needed instead of all columns
> >
> > 3) get a faster network connection
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > "Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
> > news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> > > Dear all,
> > >
> > > I have SQL Server 2000 installed at the HO server (Pentium 4, memory
512
> > > Mb). The client side (Pentium 4, memory 256 Mb) connect to the server
> > > using
> > > leased line 128 Kbps. The distance between HO and client side is 10
miles.
> > > Using Query Analyzer, to retrieve 40.000 records, it takes time about
4
> > > min
> > > 30 seconds.
> > > The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> > > If I execute the SQL from the HO computer, it just takes time 4
seconds.
> > > What can I do to fix the problem ?
> > > Thanks.
> > >
> > > Regards,
> > > Vensia
> > >
> > >
> > >
> >
> >
> >|||Hi
It has nothing to do with SQL Server. It is your network that is the
problem.
128Kbps = 16 kilo bytes per second. The practical throughput on your line,
assuming there is nothing else using it is about 10 kilo bytes per second.
If each row returned is 2'000 bytes, you can only transfer 5 rows per second
over the line.
And you are moving 40'000. Work that out.
The fact that the performance is acceptable when accessed locally indicates
at a glance your have network performance problems.
In a true n-tier application, there should be no reason to move 40'000 rows
around. I would seriously look at how your application and data access are
architected.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:Oa2tQYcCGHA.1232@.TK2MSFTNGP10.phx.gbl...
> Actually I have added the where clause in the application and index in
> the
> table.
> The user reported to me that it takes a long time to open Invoice form.
> At the server side, the invoice form can be opened in several seconds but
> at
> the client side (10 miles from the server), it takes minutes to open the
> form.
> Then I use Query Analyzer to run SQL statement "SELECT * FROM
> tblInvoiceMain" to check the execution time.
> From the PC at server side, it takes only 4 seconds but at the client
> side,
> it takes 4 minutes 30 seconds.
> I just wonder if there is something wrong with the database setting.
> Anyway, is there any relation with the log file size ? How to truncate the
> log file in SQL Server 2000 ?
> Thanks.
> "Amer M J" <AmerMJ@.discussions.microsoft.com> wrote in message
> news:5F35A98F-EBBA-4F86-B8D5-F06CA84BAE0E@.microsoft.com...
>> I second the suggestions given by Dan.
>> A where clause reduces the search time and the query will work faster if
> you
>> use an insexed coloumn in the where clause.
>> Specifying the name of the coloumn that you need will reduce the time
> taken
>> to retireve the extra not-needed coloumns.
>> A faster n/w conn is usually preferred :-D
>> Also do check whether any other query is applying any locks on the table
> !!!!
>> Thanks
>> Amer M J
>> MCP
>> "Dan Guzman" wrote:
>> > > What can I do to fix the problem ?
>> >
>> > 1) add a WHERE clause to your query
>> >
>> > 2) request only the columns needed instead of all columns
>> >
>> > 3) get a faster network connection
>> >
>> > --
>> > Hope this helps.
>> >
>> > Dan Guzman
>> > SQL Server MVP
>> >
>> > "Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
>> > news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
>> > > Dear all,
>> > >
>> > > I have SQL Server 2000 installed at the HO server (Pentium 4, memory
> 512
>> > > Mb). The client side (Pentium 4, memory 256 Mb) connect to the server
>> > > using
>> > > leased line 128 Kbps. The distance between HO and client side is 10
> miles.
>> > > Using Query Analyzer, to retrieve 40.000 records, it takes time about
> 4
>> > > min
>> > > 30 seconds.
>> > > The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
>> > > If I execute the SQL from the HO computer, it just takes time 4
> seconds.
>> > > What can I do to fix the problem ?
>> > > Thanks.
>> > >
>> > > Regards,
>> > > Vensia
>> > >
>> > >
>> > >
>> >
>> >
>> >
>
I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
leased line 128 Kbps. The distance between HO and client side is 10 miles.
Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
30 seconds.
The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
If I execute the SQL from the HO computer, it just takes time 4 seconds.
What can I do to fix the problem ?
Thanks.
Regards,
Vensia> What can I do to fix the problem ?
1) add a WHERE clause to your query
2) request only the columns needed instead of all columns
3) get a faster network connection
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> Mb). The client side (Pentium 4, memory 256 Mb) connect to the server
> using
> leased line 128 Kbps. The distance between HO and client side is 10 miles.
> Using Query Analyzer, to retrieve 40.000 records, it takes time about 4
> min
> 30 seconds.
> The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> If I execute the SQL from the HO computer, it just takes time 4 seconds.
> What can I do to fix the problem ?
> Thanks.
> Regards,
> Vensia
>
>|||I second the suggestions given by Dan.
A where clause reduces the search time and the query will work faster if you
use an insexed coloumn in the where clause.
Specifying the name of the coloumn that you need will reduce the time taken
to retireve the extra not-needed coloumns.
A faster n/w conn is usually preferred :-D
Also do check whether any other query is applying any locks on the table !!!!
Thanks
Amer M J
MCP
"Dan Guzman" wrote:
> > What can I do to fix the problem ?
> 1) add a WHERE clause to your query
> 2) request only the columns needed instead of all columns
> 3) get a faster network connection
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
> news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> > Dear all,
> >
> > I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> > Mb). The client side (Pentium 4, memory 256 Mb) connect to the server
> > using
> > leased line 128 Kbps. The distance between HO and client side is 10 miles.
> > Using Query Analyzer, to retrieve 40.000 records, it takes time about 4
> > min
> > 30 seconds.
> > The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> > If I execute the SQL from the HO computer, it just takes time 4 seconds.
> > What can I do to fix the problem ?
> > Thanks.
> >
> > Regards,
> > Vensia
> >
> >
> >
>
>|||Actually I have added the where clause in the application and index in the
table.
The user reported to me that it takes a long time to open Invoice form.
At the server side, the invoice form can be opened in several seconds but at
the client side (10 miles from the server), it takes minutes to open the
form.
Then I use Query Analyzer to run SQL statement "SELECT * FROM
tblInvoiceMain" to check the execution time.
From the PC at server side, it takes only 4 seconds but at the client side,
it takes 4 minutes 30 seconds.
I just wonder if there is something wrong with the database setting.
Anyway, is there any relation with the log file size ? How to truncate the
log file in SQL Server 2000 ?
Thanks.
"Amer M J" <AmerMJ@.discussions.microsoft.com> wrote in message
news:5F35A98F-EBBA-4F86-B8D5-F06CA84BAE0E@.microsoft.com...
> I second the suggestions given by Dan.
> A where clause reduces the search time and the query will work faster if
you
> use an insexed coloumn in the where clause.
> Specifying the name of the coloumn that you need will reduce the time
taken
> to retireve the extra not-needed coloumns.
> A faster n/w conn is usually preferred :-D
> Also do check whether any other query is applying any locks on the table
!!!!
> Thanks
> Amer M J
> MCP
> "Dan Guzman" wrote:
> > > What can I do to fix the problem ?
> >
> > 1) add a WHERE clause to your query
> >
> > 2) request only the columns needed instead of all columns
> >
> > 3) get a faster network connection
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > "Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
> > news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> > > Dear all,
> > >
> > > I have SQL Server 2000 installed at the HO server (Pentium 4, memory
512
> > > Mb). The client side (Pentium 4, memory 256 Mb) connect to the server
> > > using
> > > leased line 128 Kbps. The distance between HO and client side is 10
miles.
> > > Using Query Analyzer, to retrieve 40.000 records, it takes time about
4
> > > min
> > > 30 seconds.
> > > The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> > > If I execute the SQL from the HO computer, it just takes time 4
seconds.
> > > What can I do to fix the problem ?
> > > Thanks.
> > >
> > > Regards,
> > > Vensia
> > >
> > >
> > >
> >
> >
> >|||Hi
It has nothing to do with SQL Server. It is your network that is the
problem.
128Kbps = 16 kilo bytes per second. The practical throughput on your line,
assuming there is nothing else using it is about 10 kilo bytes per second.
If each row returned is 2'000 bytes, you can only transfer 5 rows per second
over the line.
And you are moving 40'000. Work that out.
The fact that the performance is acceptable when accessed locally indicates
at a glance your have network performance problems.
In a true n-tier application, there should be no reason to move 40'000 rows
around. I would seriously look at how your application and data access are
architected.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:Oa2tQYcCGHA.1232@.TK2MSFTNGP10.phx.gbl...
> Actually I have added the where clause in the application and index in
> the
> table.
> The user reported to me that it takes a long time to open Invoice form.
> At the server side, the invoice form can be opened in several seconds but
> at
> the client side (10 miles from the server), it takes minutes to open the
> form.
> Then I use Query Analyzer to run SQL statement "SELECT * FROM
> tblInvoiceMain" to check the execution time.
> From the PC at server side, it takes only 4 seconds but at the client
> side,
> it takes 4 minutes 30 seconds.
> I just wonder if there is something wrong with the database setting.
> Anyway, is there any relation with the log file size ? How to truncate the
> log file in SQL Server 2000 ?
> Thanks.
> "Amer M J" <AmerMJ@.discussions.microsoft.com> wrote in message
> news:5F35A98F-EBBA-4F86-B8D5-F06CA84BAE0E@.microsoft.com...
>> I second the suggestions given by Dan.
>> A where clause reduces the search time and the query will work faster if
> you
>> use an insexed coloumn in the where clause.
>> Specifying the name of the coloumn that you need will reduce the time
> taken
>> to retireve the extra not-needed coloumns.
>> A faster n/w conn is usually preferred :-D
>> Also do check whether any other query is applying any locks on the table
> !!!!
>> Thanks
>> Amer M J
>> MCP
>> "Dan Guzman" wrote:
>> > > What can I do to fix the problem ?
>> >
>> > 1) add a WHERE clause to your query
>> >
>> > 2) request only the columns needed instead of all columns
>> >
>> > 3) get a faster network connection
>> >
>> > --
>> > Hope this helps.
>> >
>> > Dan Guzman
>> > SQL Server MVP
>> >
>> > "Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
>> > news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
>> > > Dear all,
>> > >
>> > > I have SQL Server 2000 installed at the HO server (Pentium 4, memory
> 512
>> > > Mb). The client side (Pentium 4, memory 256 Mb) connect to the server
>> > > using
>> > > leased line 128 Kbps. The distance between HO and client side is 10
> miles.
>> > > Using Query Analyzer, to retrieve 40.000 records, it takes time about
> 4
>> > > min
>> > > 30 seconds.
>> > > The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
>> > > If I execute the SQL from the HO computer, it just takes time 4
> seconds.
>> > > What can I do to fix the problem ?
>> > > Thanks.
>> > >
>> > > Regards,
>> > > Vensia
>> > >
>> > >
>> > >
>> >
>> >
>> >
>
Query data is very slow
Dear all,
I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
leased line 128 Kbps. The distance between HO and client side is 10 miles.
Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
30 seconds.
The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
If I execute the SQL from the HO computer, it just takes time 4 seconds.
What can I do to fix the problem ?
Thanks.
Regards,
Vensia> What can I do to fix the problem ?
1) add a WHERE clause to your query
2) request only the columns needed instead of all columns
3) get a faster network connection
Hope this helps.
Dan Guzman
SQL Server MVP
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> Mb). The client side (Pentium 4, memory 256 Mb) connect to the server
> using
> leased line 128 Kbps. The distance between HO and client side is 10 miles.
> Using Query Analyzer, to retrieve 40.000 records, it takes time about 4
> min
> 30 seconds.
> The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> If I execute the SQL from the HO computer, it just takes time 4 seconds.
> What can I do to fix the problem ?
> Thanks.
> Regards,
> Vensia
>
>|||I second the suggestions given by Dan.
A where clause reduces the search time and the query will work faster if you
use an insexed coloumn in the where clause.
Specifying the name of the coloumn that you need will reduce the time taken
to retireve the extra not-needed coloumns.
A faster n/w conn is usually preferred :-D
Also do check whether any other query is applying any locks on the table !!!
!
Thanks
Amer M J
MCP
"Dan Guzman" wrote:
> 1) add a WHERE clause to your query
> 2) request only the columns needed instead of all columns
> 3) get a faster network connection
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
> news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
>
>|||Actually I have added the where clause in the application and index in the
table.
The user reported to me that it takes a long time to open Invoice form.
At the server side, the invoice form can be opened in several seconds but at
the client side (10 miles from the server), it takes minutes to open the
form.
Then I use Query Analyzer to run SQL statement "SELECT * FROM
tblInvoiceMain" to check the execution time.
From the PC at server side, it takes only 4 seconds but at the client side,
it takes 4 minutes 30 seconds.
I just wonder if there is something wrong with the database setting.
Anyway, is there any relation with the log file size ? How to truncate the
log file in SQL Server 2000 ?
Thanks.
"Amer M J" <AmerMJ@.discussions.microsoft.com> wrote in message
news:5F35A98F-EBBA-4F86-B8D5-F06CA84BAE0E@.microsoft.com...
> I second the suggestions given by Dan.
> A where clause reduces the search time and the query will work faster if
you
> use an insexed coloumn in the where clause.
> Specifying the name of the coloumn that you need will reduce the time
taken
> to retireve the extra not-needed coloumns.
> A faster n/w conn is usually preferred :-D
> Also do check whether any other query is applying any locks on the table
!!!![vbcol=seagreen]
> Thanks
> Amer M J
> MCP
> "Dan Guzman" wrote:
>
512[vbcol=seagreen]
miles.[vbcol=seagreen]
4[vbcol=seagreen]
seconds.[vbcol=seagreen]|||Hi
It has nothing to do with SQL Server. It is your network that is the
problem.
128Kbps = 16 kilo bytes per second. The practical throughput on your line,
assuming there is nothing else using it is about 10 kilo bytes per second.
If each row returned is 2'000 bytes, you can only transfer 5 rows per second
over the line.
And you are moving 40'000. Work that out.
The fact that the performance is acceptable when accessed locally indicates
at a glance your have network performance problems.
In a true n-tier application, there should be no reason to move 40'000 rows
around. I would seriously look at how your application and data access are
architected.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:Oa2tQYcCGHA.1232@.TK2MSFTNGP10.phx.gbl...
> Actually I have added the where clause in the application and index in
> the
> table.
> The user reported to me that it takes a long time to open Invoice form.
> At the server side, the invoice form can be opened in several seconds but
> at
> the client side (10 miles from the server), it takes minutes to open the
> form.
> Then I use Query Analyzer to run SQL statement "SELECT * FROM
> tblInvoiceMain" to check the execution time.
> From the PC at server side, it takes only 4 seconds but at the client
> side,
> it takes 4 minutes 30 seconds.
> I just wonder if there is something wrong with the database setting.
> Anyway, is there any relation with the log file size ? How to truncate the
> log file in SQL Server 2000 ?
> Thanks.
> "Amer M J" <AmerMJ@.discussions.microsoft.com> wrote in message
> news:5F35A98F-EBBA-4F86-B8D5-F06CA84BAE0E@.microsoft.com...
> you
> taken
> !!!!
> 512
> miles.
> 4
> seconds.
>
I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
leased line 128 Kbps. The distance between HO and client side is 10 miles.
Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
30 seconds.
The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
If I execute the SQL from the HO computer, it just takes time 4 seconds.
What can I do to fix the problem ?
Thanks.
Regards,
Vensia> What can I do to fix the problem ?
1) add a WHERE clause to your query
2) request only the columns needed instead of all columns
3) get a faster network connection
Hope this helps.
Dan Guzman
SQL Server MVP
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> Dear all,
> I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> Mb). The client side (Pentium 4, memory 256 Mb) connect to the server
> using
> leased line 128 Kbps. The distance between HO and client side is 10 miles.
> Using Query Analyzer, to retrieve 40.000 records, it takes time about 4
> min
> 30 seconds.
> The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> If I execute the SQL from the HO computer, it just takes time 4 seconds.
> What can I do to fix the problem ?
> Thanks.
> Regards,
> Vensia
>
>|||I second the suggestions given by Dan.
A where clause reduces the search time and the query will work faster if you
use an insexed coloumn in the where clause.
Specifying the name of the coloumn that you need will reduce the time taken
to retireve the extra not-needed coloumns.
A faster n/w conn is usually preferred :-D
Also do check whether any other query is applying any locks on the table !!!
!
Thanks
Amer M J
MCP
"Dan Guzman" wrote:
> 1) add a WHERE clause to your query
> 2) request only the columns needed instead of all columns
> 3) get a faster network connection
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
> news:eNhWKQ2BGHA.1288@.TK2MSFTNGP09.phx.gbl...
>
>|||Actually I have added the where clause in the application and index in the
table.
The user reported to me that it takes a long time to open Invoice form.
At the server side, the invoice form can be opened in several seconds but at
the client side (10 miles from the server), it takes minutes to open the
form.
Then I use Query Analyzer to run SQL statement "SELECT * FROM
tblInvoiceMain" to check the execution time.
From the PC at server side, it takes only 4 seconds but at the client side,
it takes 4 minutes 30 seconds.
I just wonder if there is something wrong with the database setting.
Anyway, is there any relation with the log file size ? How to truncate the
log file in SQL Server 2000 ?
Thanks.
"Amer M J" <AmerMJ@.discussions.microsoft.com> wrote in message
news:5F35A98F-EBBA-4F86-B8D5-F06CA84BAE0E@.microsoft.com...
> I second the suggestions given by Dan.
> A where clause reduces the search time and the query will work faster if
you
> use an insexed coloumn in the where clause.
> Specifying the name of the coloumn that you need will reduce the time
taken
> to retireve the extra not-needed coloumns.
> A faster n/w conn is usually preferred :-D
> Also do check whether any other query is applying any locks on the table
!!!![vbcol=seagreen]
> Thanks
> Amer M J
> MCP
> "Dan Guzman" wrote:
>
512[vbcol=seagreen]
miles.[vbcol=seagreen]
4[vbcol=seagreen]
seconds.[vbcol=seagreen]|||Hi
It has nothing to do with SQL Server. It is your network that is the
problem.
128Kbps = 16 kilo bytes per second. The practical throughput on your line,
assuming there is nothing else using it is about 10 kilo bytes per second.
If each row returned is 2'000 bytes, you can only transfer 5 rows per second
over the line.
And you are moving 40'000. Work that out.
The fact that the performance is acceptable when accessed locally indicates
at a glance your have network performance problems.
In a true n-tier application, there should be no reason to move 40'000 rows
around. I would seriously look at how your application and data access are
architected.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:Oa2tQYcCGHA.1232@.TK2MSFTNGP10.phx.gbl...
> Actually I have added the where clause in the application and index in
> the
> table.
> The user reported to me that it takes a long time to open Invoice form.
> At the server side, the invoice form can be opened in several seconds but
> at
> the client side (10 miles from the server), it takes minutes to open the
> form.
> Then I use Query Analyzer to run SQL statement "SELECT * FROM
> tblInvoiceMain" to check the execution time.
> From the PC at server side, it takes only 4 seconds but at the client
> side,
> it takes 4 minutes 30 seconds.
> I just wonder if there is something wrong with the database setting.
> Anyway, is there any relation with the log file size ? How to truncate the
> log file in SQL Server 2000 ?
> Thanks.
> "Amer M J" <AmerMJ@.discussions.microsoft.com> wrote in message
> news:5F35A98F-EBBA-4F86-B8D5-F06CA84BAE0E@.microsoft.com...
> you
> taken
> !!!!
> 512
> miles.
> 4
> seconds.
>
Query data is very slow
Dear all,
I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
leased line 128 Kbps. The distance between HO and client side is 10 miles.
Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
30 seconds.
The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
If I execute the SQL from the HO computer, it just takes time 4 seconds.
What can I do to fix the problem ?
Thanks.
Regards,
VensiaA prime place to being looking is the network bandwidth..
1. try doing this query from another computer close to the server (avoiding
the 128K line.)
If the response is good begin investigating the load this is placing on the
128k line..
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Vensia" wrote:
> Dear all,
> I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> Mb). The client side (Pentium 4, memory 256 Mb) connect to the server usin
g
> leased line 128 Kbps. The distance between HO and client side is 10 miles.
> Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 mi
n
> 30 seconds.
> The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> If I execute the SQL from the HO computer, it just takes time 4 seconds.
> What can I do to fix the problem ?
> Thanks.
> Regards,
> Vensia
>
>
I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
Mb). The client side (Pentium 4, memory 256 Mb) connect to the server using
leased line 128 Kbps. The distance between HO and client side is 10 miles.
Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 min
30 seconds.
The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
If I execute the SQL from the HO computer, it just takes time 4 seconds.
What can I do to fix the problem ?
Thanks.
Regards,
VensiaA prime place to being looking is the network bandwidth..
1. try doing this query from another computer close to the server (avoiding
the 128K line.)
If the response is good begin investigating the load this is placing on the
128k line..
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Vensia" wrote:
> Dear all,
> I have SQL Server 2000 installed at the HO server (Pentium 4, memory 512
> Mb). The client side (Pentium 4, memory 256 Mb) connect to the server usin
g
> leased line 128 Kbps. The distance between HO and client side is 10 miles.
> Using Query Analyzer, to retrieve 40.000 records, it takes time about 4 mi
n
> 30 seconds.
> The SQL statatement that I execute is "SELECT * FROM tblInvoiceMain"
> If I execute the SQL from the HO computer, it just takes time 4 seconds.
> What can I do to fix the problem ?
> Thanks.
> Regards,
> Vensia
>
>
Monday, February 20, 2012
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:
>
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:
>
>
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. :-)
>>
>
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. :-)
>>
>
Subscribe to:
Posts (Atom)