Re: Performance really poor if calling data from sql clients
- From: "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx>
- Date: Sun, 2 Apr 2006 21:21:02 -0400
Sorry I meant SSMS (SQL Server Management Studio).
--
Andrew J. Kelly SQL MVP
"Stephan (Germany)" <StephanGermany@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:187C37B8-FC91-4978-B928-FA17A21979E1@xxxxxxxxxxxxxxxx
Hello Andrew,
what do you mean with SSIS ?
I have checked DNS, WINS and address resolution. The laptop where the
database is running can be found via ping and nslookup.
If I make another test (creating new logins in SQL management studio), it
is
not possible to see any other domain rather than the laptop itself, this
is a
bit confusing.
Maybe it has nothing to do with my problem but it is not really good.
"Andrew J. Kelly" wrote:
If you run the same query from SSIS on the server does it run fast or
slow?
Sounds like network issues or problems with name resolution.
--
Andrew J. Kelly SQL MVP
"Stephan (Germany)" <StephanGermany@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:E1285720-7132-4B56-B754-B98E9594F466@xxxxxxxxxxxxxxxx
Ok, the performance is not stable:
it is true that with named pipes. it is going a bit faster, but each
time
I
select another table to be displayed, it is still waiting for something
I
cannot see even in the profiler. There is an overhead I can't actually
find
out.
Any idea?
Yours
Stephan
"Stephan (Germany)" wrote:
Hello Andrew,
good hint with the profiler.
You know I'm "fighting" since a while to follow the documented
recommendation of using TCP instead of Named Pipes to get performance.
I see now if I using Named Pipes connection in VS2005, everything is
going
faster in VS2005 (and I assume this will also happen for my
application
if I
do the same).
So, what is the problem with TCP as connection type? Already known
issues
by
Microsoft SQL developer teams?
Yours
Stephan
"Andrew J. Kelly" wrote:
I can't vouch for any of the VS components when it comes to
performance
since I don't use them for database access. But you should be able
to
use
profiler to see what is happening on the sql server end. Also what
does the
query plan look like? Is it optimal? Did you run sp_updatestats?
--
Andrew J. Kelly SQL MVP
"Stephan (Germany)" <StephanGermany@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:FB05EA03-F277-4FBE-B1AB-A7C8C767B41D@xxxxxxxxxxxxxxxx
Hello,
I have installed SQL2005 developer edition on a laptop (2 GB RAM),
VS2005
on
another computer. The database is quite small (nearly no data or
some
test
data). The performance is still really bad:
xxx each time you open the server explorer in VS2005 and you use
"show
table
data" (takes at least 20 sec., sometimes time out).
xxx each time I read from tables within my application (I'm not
reading
the
full table, I'm selecting the data, number of records < 5)
What can be done in order to determine the performance consuming
element/object? The network the computer are attached consists of
less
than 5
users (1 GBit backbone).
Are there any configuration aspects which can help to improove the
performance?
Network pack size = 4096
Max. number of concurrent connections = 0
Boost SQL server priority is not checked
Max. server memory = 2 GB
Thanks,
Stephan
.
- Follow-Ups:
- Re: Performance really poor if calling data from sql clients
- From: Stephan (Germany)
- Re: Performance really poor if calling data from sql clients
- References:
- Re: Performance really poor if calling data from sql clients
- From: Andrew J. Kelly
- Re: Performance really poor if calling data from sql clients
- From: Stephan (Germany)
- Re: Performance really poor if calling data from sql clients
- From: Andrew J. Kelly
- Re: Performance really poor if calling data from sql clients
- From: Stephan (Germany)
- Re: Performance really poor if calling data from sql clients
- Prev by Date: Re: Performance really poor if calling data from sql clients
- Next by Date: Re: Performance really poor if calling data from sql clients
- Previous by thread: Re: Performance really poor if calling data from sql clients
- Next by thread: Re: Performance really poor if calling data from sql clients
- Index(es):
Relevant Pages
|