shahzadq
asked on
Slow MSSQL vs. ACCESS in VB ADODB
Help!
I have a vb app, that was running nice and smooth on an ACCESS database, using ADODB in code.
Now, I exported the tables, and moved it to an SQL database.
It's now running 5 - 10 times slower...
Pinging the server, and accessing it any other way on the network is just fine, it's only from accessing it within the VB app...
any thought?
I repeate... HELP!
I have a vb app, that was running nice and smooth on an ACCESS database, using ADODB in code.
Now, I exported the tables, and moved it to an SQL database.
It's now running 5 - 10 times slower...
Pinging the server, and accessing it any other way on the network is just fine, it's only from accessing it within the VB app...
any thought?
I repeate... HELP!
What does your execution plan look like? Can you run a query in query analyzer can compare the results?
![Avatar of Guy Hengel [angelIII / a3]](https://filedb.experts-exchange.com/files/public/2013/11/25/ddbe0ea6-aa6e-4279-b781-57b735dd3ea0.jpeg){kind=small}
>It's now running 5 - 10 times slower...
this is NOT the problem of SQL Server itself, but ususally missing indexes.
this is NOT the problem of SQL Server itself, but ususally missing indexes.
ASKER
YEah, Query Analyzer is pulling them up just great.
Hmm ... Indexes... let me check something on that... But wouldn't that also slow down Query Analyzer?
Hmm ... Indexes... let me check something on that... But wouldn't that also slow down Query Analyzer?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, I think I'm at the best I can get
Your comments make sense...
The SQL database is poorly written (Hey, it was already setup when I got here).
But yes, I am using a specific connections string... no it's not .Net, I will check on the names pipes thing.
But I think the problem may simply be the machine it's running on. Just too old.
Shahzad
Your comments make sense...
The SQL database is poorly written (Hey, it was already setup when I got here).
But yes, I am using a specific connections string... no it's not .Net, I will check on the names pipes thing.
But I think the problem may simply be the machine it's running on. Just too old.
Shahzad
TCP/IP protocol would be better.