March 19, 2010 at 11:55 am
I have a program written in VB6 that uses ADO to communicate to a SQL Server 2005 Express database on another machine. This works great and fast if the app is running on an XP machine no matter what the SQL Server database is loaded onto. However if the same application is running under windows 7 32bit or 64bit or Vista the app runs very slow processing the same query. No AV is loaded so that is not the issue. I have disabled the Window Auto Tuning Level feature which made no difference. SQL Authentication is used to connect to the database. Is there anything in the OS that is restricting communication to SQL Server that can be disabled or changed?
March 19, 2010 at 12:07 pm
DBA_Help (3/19/2010)
I have a program written in VB6 that uses ADO to communicate to a SQL Server 2005 Express database on another machine. This works great and fast if the app is running on an XP machine no matter what the SQL Server database is loaded onto. However if the same application is running under windows 7 32bit or 64bit or Vista the app runs very slow processing the same query. No AV is loaded so that is not the issue. I have disabled the Window Auto Tuning Level feature which made no difference. SQL Authentication is used to connect to the database. Is there anything in the OS that is restricting communication to SQL Server that can be disabled or changed?
Both Vista and Windows 7 comes with new data access components so you need to manually reference MDAC in code and in x64 you need to make sure Vista is at least SP1 so you can access x86 ODBC because botth MDAC and ODBC are needed to use ADO. I have threads on MSDN if I find the threads I will post it here.
Kind regards,
Gift Peddie
March 19, 2010 at 1:02 pm
I am not sure if I understand your response about manually referencing MDAC. The program is referencing ADO through Microsoft ActiveX Data Objects 2.8 Library which is included with the installation. The app runs without errors it just runs slow(A typical query response of 1 second is now taking 5-10 seconds) so I don't follow how to reference another means of connection.
March 19, 2010 at 1:09 pm
DBA_Help (3/19/2010)
I am not sure if I understand your response about manually referencing MDAC. The program is referencing ADO through Microsoft ActiveX Data Objects 2.8 Library which is included with the installation. The app runs without errors it just runs slow(A typical query response of 1 second is now taking 5-10 seconds) so I don't follow how to reference another means of connection.
The behavior varies sometimes it runs others it will not run but it is Microsoft that provided the code to manually reference MDAC in Vista and it makes it run. I am assuming when the dll is accessed may have to do with the behavior. If I find the thread I can post it what you can do is use the SQL Client it works better with unmanaged code like VB6.
Kind regards,
Gift Peddie
March 19, 2010 at 2:01 pm
I just checked manually reefrencing MDAC relates to the x64 version of both operating systems, but in Windows 7 the advice to use VB6 is to either use XP mode or Virtual PC. Here is Microsoft provided information about VB6.
http://msdn.microsoft.com/en-us/vbrun/ms788708.aspx
Kind regards,
Gift Peddie
March 19, 2010 at 3:55 pm
Based on the last post it sounds like this app should be run under the XP mode. However on the link page from the last post it states under "Supported and Shipping in Windows Vista, Windows Server 2008, and Windows 7" the file used by the ado communication which is "msado15.dll". So I am not buying that this app should be run under XP Mode. If that were true then every application written in VB 6 using ado to communicate to a database would need to run under XP Mode. I believe another solution exists. Although I do not know what it is and therefore the post on this site was initiated. I hope someone else can help shed some light.
Thanks in advance.
DBA_Help
September 27, 2010 at 1:16 pm
We are facing the exact same issue. Has any resolution been discovered?
November 25, 2010 at 4:40 am
Please read this post :
http://www.sqlservercentral.com/Forums/Topic880742-149-1.aspx?Update=1
It may help.
September 29, 2014 at 7:43 pm
Check & enable these configurations in SQL Server Configuration Manager.
1. Make sure that TCP/IP protocol is enabled in SQL Server Network Configuration
2. Make sure that Named Pipes protocol is enabled in SQL Server Network Configuration
3. Make sure that TCP/IP protocol is enabled in SQL Server Native Client Configuration
4. Make sure that Named Pipes protocol is enabled in SQL Server Native Client Configuration
Restart the SQL services and we are done.
February 22, 2016 at 7:43 pm
Thanks for your nice post to teach us more about Windows 7. On here, we can learn more about Windows 7 password bypass. How to get a simple Windows Password Key on Google to bypass Windows 7 password in efficient way. The Windows password recovery software that I got is on here.
See more at: http://www.lostwindowspassword.com
February 22, 2016 at 7:46 pm
Thanks for your nice post to teach us more about Windows 7. On here, we can learn more about Windows 7 password bypass. How to get a simple Windows Password Key on Google to bypass Windows 7 password in efficient way. The Windows password recovery software that I got is on here.
See more at: http://www.lostwindowspassword.com
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply