![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We had a trojan downloader infect our network and in the process of look at the network traffic I discovered that I was getting many syntax errors where the asp/web front end was making a call to a 2005 back end database and it would chop part of the next query or shorten the current query. What is really weird is that the .net client seems to be compensating for this and re-issueing the query another way so the app (app is .net 2.0 with sp2) continues to function with no visible errors. |
#3
| |||
| |||
|
|
We had a trojan downloader infect our network and in the process of look at the network traffic I discovered that I was getting many syntax errors where the asp/web front end was making a call to a 2005 back end database and it would chop part of the next query or shorten the current query. What is really weird is that the .net client seems to be compensating for this and re-issueing the query another way so the app (app is .net 2.0 with sp2) continues to function with no visible errors. I have checked the database compatiblity layer which is 90 or 2005 on the database that we are running the queries to. Also it is 2005 server. The asp server has sql express 2005 on it and it looks like it might need a service pack because its build # is smaller than that on my 2005 standard server. I am not sure if this problem preexisted the virus but the system is now running a bit sluggishly also other departments are reporting the back end sql server is now running slow. I am now running benchmarks with perfmon to get some ideas and I think i have some old perfmon results to compare with on the back end sql server. I have done numerous searches but most incorrect syntax errors are because of programming mistakes. That is not the case here. The problem is across multiple sql requests from different components and it appears to be working in the app. |
![]() |
| Thread Tools | |
| Display Modes | |
| |