The customer feedback is only the appearance, the measurement is the hard truth

Recently working on a project, the main process of the project is as follows:


1, the customer application of existing systems to the SQL database Interactive data table Insert data


2. Read the data from the interactive data table to the software of the project


3, the project software through the interface to connect the company's existing systems, to achieve data control


4, the control results are echoed into the interactive datasheet


5, the customer's system read results


Roughly more than half a month later, the project software was made, then tested inside the company and then delivered to the customer.


Originally everything went smoothly, but the client side but for a variety of reasons can not be installed according to the requirements of the corresponding environment, such as SQL2005 or above version, the customer has used SQL2000.


No way, the customer is God, customers must use SQL2000, then use it. Fortunately, the previous design of the database, there is no use of SQL2005 or the characteristics of the above version, so the SQL2000 is no problem.


But the problem comes again, the customer uses the project software to connect the SQL2000, but unexpectedly crashes. So the customer feedback, said the software problem. Read the email they sent over, look closely, probably two problems.


Issue 1: When using the WIN7 system connection, you are prompted not to modify the config file.


Problem 2: When using XP system connections, the software crashes because of an exception.


When I got the question, I made an analysis and tentatively concluded that problem 1 was due to WIN7 's own authority management, and later I built a standard user and Admin user on WIN7 to test it. The problem recurs when using standard user actions. Then the problem disappears with the admin user. In this way, the problem is solved.


However, later another thought, we just designed to meet the requirements of the software, is the WIN7 Management authority of the problem is also our pipe. We may think so, but the client will not think so. Customers just know that using our design software is problematic, so the first reaction is software. After our actual test to reproduce the results, we found that it is not our problem, but the client gave the user permissions is not enough. Therefore, some problems, although not our own problems, but because it is the use of our products produced, but also to us to solve, at least to prove that it is not our problem. Fortunately, after the use of WIN7 have encountered such problems, otherwise it will be entangled is not the design problem.


As for the second question, it is even more tangled. First of all, customers have to use SQL2000, the environment is not up to what we require. Now there's a problem, but we're looking for it. What can we do. Have to find the problem. So the cost of a lot of strength under the SQL2000 (the company's slow speed of a tread confused, just spent 4 hours before the end), and then installed on the XP, toss for a long time, found that SQL2000 can run. What is the reason why the problem cannot be reproduced.


Later, I think, I XP is installed on the SQL2008, will not be because of this. At the time of inspection, it was found that SQL2000 was connected to the SQL2008 instance. It's all my fault that I didn't notice when I installed SQL2000. But that doesn't mean anything, because the problem can't be reproduced. So think about it, or simply install a clean environment to test.


Then another toss, finally installed a Win2003 server virtual machine. Install the SQL2000 immediately after the load is finished. I thought, this test should be able to know the problem. But a software test found that SQL2000 's database was not available. What is the reason. Decisive Google, after a pass to find information, and finally found the prospect, because it is from the host to access the virtual machine in the database, is a remote access. While remote access is to open the TCP/IP channel on the SQL2000, it opens immediately on the SQL2000 and sets the default port 1433 for TCP/IP. But still can't even.


What is the reason for this? Grab your head. Grab your head.
Continue to Google, finally checked the n after the article (online article very let the person egg ache, basically is copy paste), finally found the prospect. Said is to play SP3 patch, but I under the SQL2000 is SQL2000SP4 version of Ah, is not the equivalent of a patched it. Entangled for a long time, and finally decided to try. So do not hesitate to download it. Helpless speed, but also nearly 1 hours of waiting, finally finished the patch, loaded up.


Uh.. It's not going to work. why! why! why!


So Google search, after the article sea, finally fished a needle. Said is server2003 to install SP4 patch. Crazy. Crazy. No way, but also nearly 1 hours of download, installation. And then according to the article said, confirm the version, so select @ @VERSION, a check, the version is reached, is 8.0.2039. After the connection, finally OK.


After a turn toss, the project software connection SQL2000 completely OK. So asked the customer is not SQL2000 not patched, customer response is not clear, so the customer asked for SP4 patch installation.


Ben thought, this is finally good. Customers can not complete after the installation, still not.


It's not going to work. No way. No way.


Think and think, thinking and thinking, and finally think that will not be the database user permissions are not enough. Then asked the next customer, said the SQL2000 database administrator to the user. While I was testing the SA user, I further identified the issue of permissions. Then to the customer suggested a high point of access to users, but also immediately by the idea of the actual test, found that really is the issue of permissions. When there is not enough permissions, the program crashes. Just when I confirmed that this was the reason, the customer also gave feedback, elevated the permissions, OK.


After a toss and turn, always solved the problem. But think of these two problems, it seems that is not the software itself, one is the WIN7 of authority management, a SQL2000 of the rights of management caused. But think carefully, there are some reasons for software design defects, such as SQL2000 permissions, should give a hint, but should be the program crashes. This was due to a flaw in my own design of a database access class, which was then adjusted.


From another point of view, the problem of customer feedback is not necessarily the nature of the problem, but only an appearance, must be tested after the actual to confirm. So don't be blinded by the imagery, the actual measurement is the hard truth.