query assistance: slow

Showing posts with label slow. Show all posts

Monday, March 12, 2012

query designer very slow loading tables

when i use the query designer and add tables it takes 15-30 mins to load a table....so if i need 6 tables in my query thats like 6 times 30 minute load times...i'm using oracle as my data source

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

any ideas?

moldypenguins wrote:

when i use the query designer and add tables it takes 15-30 mins to load a table

You're saying it takes 15-30 minutes to drag and drop a table control onto the layout of query designer?

What is it exactly that is taking that long?

|||>>

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

Yes -- use oledb and find a way around the named parameters thing <g>. Tell us more about your query, maybe we can figure out something there.

Alternatively... what version of what type of connection are you using when you don't use OLEDB? I use Oracle stuff, maybe I can help or somebody else will spot what's wrong. (I'll be off-line shortly for about a week)

>L<

|||

it takes 15-30 minutes to load the table...ie i click the add table button, click a table and click add, then i wait

|||

Can you post a screenshot of where you are doing this?

If you can't then describe further. I'm not slow, it's just there are several places you could be designing a query.

Are you using SQL 2000? 2005? Is this in BIS? SQL Server Management Studio?

|||

sorry i'm using sql 2005 in bis, here is a screen shot

|||

How much RAM is in the PC that you are adding the table to query designer from? What is the processor speed? How about on the SQL server?

What is the network configuration like between the PC that you are using query designer and the SQL server? Is it the same machine?

Have you noticed slow load times in any other SQL application (such as Management Studio)?

|||

its not the pc because i have tried it on other computers in the office, server is open vms running orcle 9i

|||

Just because you have tried it on other computers and it does the same thing doesn't mean it's not the PC.

If they all have 256 mb of RAM in them then you could experience the same problem in all of them.

In my experience, slow load time = not enough hardware OR poor network setup OR antivirus interference.

|||

i have 512mb

and the other 2 have 2gb or more

and like i said it works quickly when i chose oledb but i need to keep named parameters|||

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=324176&SiteID=1

here is someone else with the same problem!

|||

Given that the other post also uses the same Oracle connector (right/) I wonder if it is trying to re-use the connection for the same connection and the Oracle connector doesn't like that, the first use has to time out before it's possible. Sounds like a bug in the connector or the way it's being used -- no idea --

So I am going to ask again what I asked before <s>:

>>

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

<<

Yes -- use oledb and find a way around the named parameters thing <g>. Tell us more about your query, maybe we can figure out something there.

I'm serious, let's give this a go.

>L<

|||the query doesn't matter because i don't even make it that far....its just when i'm loading the tables into the designer, it seems like it is taking long to link the databases or something, but when i use oledb it works super fast.....|||

Hi there,

Look: I'm not talking about "optimizing" your query, and I don't think your query is the problem.

But the query *does* matter. Because if you could change the query so you could use oledb on the query, then you would be using oledb to load the tables in the designer and your problem would go away <g>.

As I said before:

... and this is something we probably can't fix. So I'm going for something that we *can*. OK?

>L<

|||BTW -- http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2096059&SiteID=1

... please look at this thread, you may be using an unsupported connection method for the query designer. So if you want to speed up the QD loads, let's work at arranging your query so you can use the OLE DB driver, really I think it may be possible to get around the "named parameters" reason that you can't use the OLE DB driver in this case.

So describe what you're doing and we'll take a shot...

>L<

query designer very slow loading tables

when i use the query designer and add tables it takes 15-30 mins to load a table....so if i need 6 tables in my query thats like 6 times 30 minute load times...i'm using oracle as my data source

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

any ideas?

moldypenguins wrote:

when i use the query designer and add tables it takes 15-30 mins to load a table

You're saying it takes 15-30 minutes to drag and drop a table control onto the layout of query designer?

What is it exactly that is taking that long?

|||>>

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

Yes -- use oledb and find a way around the named parameters thing <g>. Tell us more about your query, maybe we can figure out something there.

>L<

|||

it takes 15-30 minutes to load the table...ie i click the add table button, click a table and click add, then i wait

|||

Can you post a screenshot of where you are doing this?

If you can't then describe further. I'm not slow, it's just there are several places you could be designing a query.

Are you using SQL 2000? 2005? Is this in BIS? SQL Server Management Studio?

|||

sorry i'm using sql 2005 in bis, here is a screen shot

|||

How much RAM is in the PC that you are adding the table to query designer from? What is the processor speed? How about on the SQL server?

What is the network configuration like between the PC that you are using query designer and the SQL server? Is it the same machine?

Have you noticed slow load times in any other SQL application (such as Management Studio)?

|||

its not the pc because i have tried it on other computers in the office, server is open vms running orcle 9i

|||

Just because you have tried it on other computers and it does the same thing doesn't mean it's not the PC.

If they all have 256 mb of RAM in them then you could experience the same problem in all of them.

In my experience, slow load time = not enough hardware OR poor network setup OR antivirus interference.

|||

i have 512mb

and the other 2 have 2gb or more

and like i said it works quickly when i chose oledb but i need to keep named parameters|||

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=324176&SiteID=1

here is someone else with the same problem!

|||

So I am going to ask again what I asked before <s>:

>>

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

<<

Yes -- use oledb and find a way around the named parameters thing <g>. Tell us more about your query, maybe we can figure out something there.

I'm serious, let's give this a go.

>L<

Hi there,

Look: I'm not talking about "optimizing" your query, and I don't think your query is the problem.

As I said before:

... and this is something we probably can't fix. So I'm going for something that we *can*. OK?

>L<

|||BTW -- http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2096059&SiteID=1

So describe what you're doing and we'll take a shot...

>L<

query designer very slow loading tables

when i use the query designer and add tables it takes 15-30 mins to load a table....so if i need 6 tables in my query thats like 6 times 30 minute load times...i'm using oracle as my data source

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

any ideas?

moldypenguins wrote:

when i use the query designer and add tables it takes 15-30 mins to load a table

You're saying it takes 15-30 minutes to drag and drop a table control onto the layout of query designer?

What is it exactly that is taking that long?

|||>>

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

Yes -- use oledb and find a way around the named parameters thing <g>. Tell us more about your query, maybe we can figure out something there.

>L<

|||

it takes 15-30 minutes to load the table...ie i click the add table button, click a table and click add, then i wait

|||

Can you post a screenshot of where you are doing this?

If you can't then describe further. I'm not slow, it's just there are several places you could be designing a query.

Are you using SQL 2000? 2005? Is this in BIS? SQL Server Management Studio?

|||

sorry i'm using sql 2005 in bis, here is a screen shot

|||

How much RAM is in the PC that you are adding the table to query designer from? What is the processor speed? How about on the SQL server?

What is the network configuration like between the PC that you are using query designer and the SQL server? Is it the same machine?

Have you noticed slow load times in any other SQL application (such as Management Studio)?

|||

its not the pc because i have tried it on other computers in the office, server is open vms running orcle 9i

|||

Just because you have tried it on other computers and it does the same thing doesn't mean it's not the PC.

If they all have 256 mb of RAM in them then you could experience the same problem in all of them.

In my experience, slow load time = not enough hardware OR poor network setup OR antivirus interference.

|||

i have 512mb

and the other 2 have 2gb or more

and like i said it works quickly when i chose oledb but i need to keep named parameters|||

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=324176&SiteID=1

here is someone else with the same problem!

|||

So I am going to ask again what I asked before <s>:

>>

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

<<

Yes -- use oledb and find a way around the named parameters thing <g>. Tell us more about your query, maybe we can figure out something there.

I'm serious, let's give this a go.

>L<

Hi there,

Look: I'm not talking about "optimizing" your query, and I don't think your query is the problem.

As I said before:

... and this is something we probably can't fix. So I'm going for something that we *can*. OK?

>L<

|||BTW -- http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2096059&SiteID=1

So describe what you're doing and we'll take a shot...

>L<

query designer very slow loading tables

when i use the query designer and add tables it takes 15-30 mins to load a table....so if i need 6 tables in my query thats like 6 times 30 minute load times...i'm using oracle as my data source

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

any ideas?

moldypenguins wrote:

when i use the query designer and add tables it takes 15-30 mins to load a table

You're saying it takes 15-30 minutes to drag and drop a table control onto the layout of query designer?

What is it exactly that is taking that long?

|||>>

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

Yes -- use oledb and find a way around the named parameters thing <g>. Tell us more about your query, maybe we can figure out something there.

>L<

|||

it takes 15-30 minutes to load the table...ie i click the add table button, click a table and click add, then i wait

|||

Can you post a screenshot of where you are doing this?

If you can't then describe further. I'm not slow, it's just there are several places you could be designing a query.

Are you using SQL 2000? 2005? Is this in BIS? SQL Server Management Studio?

|||

sorry i'm using sql 2005 in bis, here is a screen shot

|||

How much RAM is in the PC that you are adding the table to query designer from? What is the processor speed? How about on the SQL server?

What is the network configuration like between the PC that you are using query designer and the SQL server? Is it the same machine?

Have you noticed slow load times in any other SQL application (such as Management Studio)?

|||

its not the pc because i have tried it on other computers in the office, server is open vms running orcle 9i

|||

Just because you have tried it on other computers and it does the same thing doesn't mean it's not the PC.

If they all have 256 mb of RAM in them then you could experience the same problem in all of them.

In my experience, slow load time = not enough hardware OR poor network setup OR antivirus interference.

|||

i have 512mb

and the other 2 have 2gb or more

and like i said it works quickly when i chose oledb but i need to keep named parameters|||

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=324176&SiteID=1

here is someone else with the same problem!

|||

So I am going to ask again what I asked before <s>:

>>

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

<<

Yes -- use oledb and find a way around the named parameters thing <g>. Tell us more about your query, maybe we can figure out something there.

I'm serious, let's give this a go.

>L<

Hi there,

Look: I'm not talking about "optimizing" your query, and I don't think your query is the problem.

As I said before:

... and this is something we probably can't fix. So I'm going for something that we *can*. OK?

>L<

|||BTW -- http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2096059&SiteID=1

So describe what you're doing and we'll take a shot...

>L<

query designer very slow loading tables

when i use the query designer and add tables it takes 15-30 mins to load a table....so if i need 6 tables in my query thats like 6 times 30 minute load times...i'm using oracle as my data source

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

any ideas?

moldypenguins wrote:

when i use the query designer and add tables it takes 15-30 mins to load a table

You're saying it takes 15-30 minutes to drag and drop a table control onto the layout of query designer?

What is it exactly that is taking that long?

|||>>

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

Yes -- use oledb and find a way around the named parameters thing <g>. Tell us more about your query, maybe we can figure out something there.

>L<

|||

it takes 15-30 minutes to load the table...ie i click the add table button, click a table and click add, then i wait

|||

Can you post a screenshot of where you are doing this?

If you can't then describe further. I'm not slow, it's just there are several places you could be designing a query.

Are you using SQL 2000? 2005? Is this in BIS? SQL Server Management Studio?

|||

sorry i'm using sql 2005 in bis, here is a screen shot

|||

How much RAM is in the PC that you are adding the table to query designer from? What is the processor speed? How about on the SQL server?

What is the network configuration like between the PC that you are using query designer and the SQL server? Is it the same machine?

Have you noticed slow load times in any other SQL application (such as Management Studio)?

|||

its not the pc because i have tried it on other computers in the office, server is open vms running orcle 9i

|||

Just because you have tried it on other computers and it does the same thing doesn't mean it's not the PC.

If they all have 256 mb of RAM in them then you could experience the same problem in all of them.

In my experience, slow load time = not enough hardware OR poor network setup OR antivirus interference.

|||

i have 512mb

and the other 2 have 2gb or more

and like i said it works quickly when i chose oledb but i need to keep named parameters|||

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=324176&SiteID=1

here is someone else with the same problem!

|||

So I am going to ask again what I asked before <s>:

>>

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

<<

Yes -- use oledb and find a way around the named parameters thing <g>. Tell us more about your query, maybe we can figure out something there.

I'm serious, let's give this a go.

>L<

Hi there,

Look: I'm not talking about "optimizing" your query, and I don't think your query is the problem.

As I said before:

... and this is something we probably can't fix. So I'm going for something that we *can*. OK?

>L<

|||BTW -- http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2096059&SiteID=1

So describe what you're doing and we'll take a shot...

>L<

query designer very slow loading tables

when i use the query designer and add tables it takes 15-30 mins to load a table....so if i need 6 tables in my query thats like 6 times 30 minute load times...i'm using oracle as my data source

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

any ideas?

moldypenguins wrote:

when i use the query designer and add tables it takes 15-30 mins to load a table

You're saying it takes 15-30 minutes to drag and drop a table control onto the layout of query designer?

What is it exactly that is taking that long?

|||>>

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

Yes -- use oledb and find a way around the named parameters thing <g>. Tell us more about your query, maybe we can figure out something there.

>L<

|||

it takes 15-30 minutes to load the table...ie i click the add table button, click a table and click add, then i wait

|||

Can you post a screenshot of where you are doing this?

If you can't then describe further. I'm not slow, it's just there are several places you could be designing a query.

Are you using SQL 2000? 2005? Is this in BIS? SQL Server Management Studio?

|||

sorry i'm using sql 2005 in bis, here is a screen shot

|||

How much RAM is in the PC that you are adding the table to query designer from? What is the processor speed? How about on the SQL server?

What is the network configuration like between the PC that you are using query designer and the SQL server? Is it the same machine?

Have you noticed slow load times in any other SQL application (such as Management Studio)?

|||

its not the pc because i have tried it on other computers in the office, server is open vms running orcle 9i

|||

Just because you have tried it on other computers and it does the same thing doesn't mean it's not the PC.

If they all have 256 mb of RAM in them then you could experience the same problem in all of them.

In my experience, slow load time = not enough hardware OR poor network setup OR antivirus interference.

|||

i have 512mb

and the other 2 have 2gb or more

and like i said it works quickly when i chose oledb but i need to keep named parameters|||

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=324176&SiteID=1

here is someone else with the same problem!

|||

So I am going to ask again what I asked before <s>:

>>

when i switch the source to oledb it adds tables within seconds the only thing is i need to use named parameters

<<

Yes -- use oledb and find a way around the named parameters thing <g>. Tell us more about your query, maybe we can figure out something there.

I'm serious, let's give this a go.

>L<

Hi there,

Look: I'm not talking about "optimizing" your query, and I don't think your query is the problem.

As I said before:

... and this is something we probably can't fix. So I'm going for something that we *can*. OK?

>L<

|||BTW -- http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2096059&SiteID=1

So describe what you're doing and we'll take a shot...

>L<

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:
> > 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
>> > >
>> > >
>> > >
>> >
>> >
>> >
>

Monday, March 12, 2012

query designer very slow loading tables

query designer very slow loading tables

query designer very slow loading tables

query designer very slow loading tables

query designer very slow loading tables

query designer very slow loading tables

Friday, March 9, 2012

Query data is very slow

Query data is very slow

Query data is very slow

Query data is very slow

Query data is very slow

Query data is very slow

query assistance

Blog Archive

About Me