Hi all,
I've got an unusual problem and I'm looking for some feedback! I am also going to open a support ticket with Tess in hopes that they can help.
We recently installed T-Stats and it was brought to my attention that recent ticket order and contribution data was not complete (since early October). I assumed this was a T-Stats issue and opened a help ticket with JCA. We spent some time trying to figure it out but discovered that it was actually data missing from the Tess tables we were working with.
I had a bit of a panic attack but tried finding the same data through different means and it is all there as it should be. But for some reason I'm unable to access that data the way I want to.
Here's the basic scenario I had in a nutshell:
1) I did a remote desktop connection to my TEST server. From there I linked to my live database through SQL Server Management Studio. I ran a select script on the T_ORDER table for a time frame and received 10 rows.
2) I did a remote desktop connection to my LIVE server. I linked to my live database through SSMS and ran the same script. This gave me 8883 rows.
3) I accessed SSMS through my desktop machine and connected to my live database. I ran the same script and received 8883 rows.
So something is going on with my test server trying to access my live data (which is why our T-Stats information is not complete).
Does anyone have any idea why this would be happening? Any ideas would be great!
Thanks,
Beth
The wonderful JCA team has helped me resolve this dilemma. There was a line in the hosts file on our test server that was causing it to loop back to our test server rather than continue on to the live server. We removed the line and now our test server is able to access our live data!