Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
michaeljeffrey
Starting Member
2 Posts |
 Posted - 2010-02-10 : 08:57:40
|
| I have a small program written in Delphi used for our church's administration which uses an SQL2000 database. Other churches now use it as well. 2 years ago I installed it on a computer with Vista, and as a result I had to use SQL 2005 for the first time. We had found it to be horribly slow in all functions, with a sample procedure that would take less than 1/2 a second to be perfomed on an XP/SQL2000 machine (Pentium 4) taking over 17 seconds to be performed on this dual core machine with Vista/SQL 2005. Now I have a church with a brand new computer running Windows 7 for which I used SQL 2008. I had the same problem, with this sample procedure taking over 17 seconds. From this I surmise that it is a problem with SQL's communication with Vista or Windows 7.I have found other people complaining about the same problem with Vista. Some people have found a fix by disabling the Receive Window Auto Tuning Level for TCP/IP communications as described on this page (http://www.vistax64.com/tutorials/72308-auto-tuning-tcp-ip-receive-level.html). Unfortunately trying any of these options (disabled, restricted or high tuning levels) did not have any impact for my program. I also understand that you can get around it by running an XP emulator in Vista or Windows 7 and installing the program under that. That seems to provide further proof that it is something that the Windows 7/Vista operating system is going with SQL communications since an XP running within those operating systems is not impacted. I want to try to avoid this work around as it seems a bit messy to me especially with users that are not that sophisticated at computer use.I would be grateful if anyone who had this issue and solved it would provide me with some assistance on this. |
|
|
tripodal
Constraint Violating Yak Guru
259 Posts |
Posted - 2010-02-10 : 11:12:09
|
| Before assuming your problem is identical to "other people"I would suggest checking out your hardward / firewall settings. I always get cause when I dont check the easiest things first.Then possibly check performance monitor, your 17 second query should show some kind of activity HD CPU Sql row locking. There is also the possiblity the indexs your database was using in SQL2000 will need to be rebuilt as I understant this may not alwasy happen automatically. Im certain someone here can tell you the proper sql to do that. |
 |
|
|
michaeljeffrey
Starting Member
2 Posts |
Posted - 2010-02-11 : 13:34:13
|
| Thanks for the reply. I had forgotten to say that in all cases I am using 32 bit versions of all the software and I am using SQL Express 2008 (the free version). I have port 1433 open in the Windows Firewall. The database has only 2 tables, both newly created by importing data from excel. Neither table has indexes. One table is customer info consisting of about 30 fields and it curently has 330 records in it. The second is a list of receivables with only 16 records in it. My test procedure that I mentioned runs through the customer table and does a count of who is a member of the church and who isn't. Taking 17 seconds to count through 330 records is scary (a blistering pace of 19 records per second). I have now installed the XP virtualization within Windows & and installed SQL Express 2008 within that. The procedure then takes about 5 seconds to run in the XP virtualization as compared to the 17 seconds running within Windows 7. That is still slower than running it in native XP. |
|
|
|
tripodal
Constraint Violating Yak Guru
259 Posts |
|
|
|
|
|
SQL communication slow with Vista and Windows 7