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 |
|
sduclosson
Starting Member
6 Posts |
 Posted - 2009-05-18 : 16:19:06
|
| Hi, I´m working with SQLServer 2005 and I´m having the following issue. When I install my software (wich connects to an SQLServer database) in a machine that has the SQLServer database locally the program runs fine, the problem is when I install the program on a machine that conects to the SQL Server trought a network, in this case some features of my program work but others don´t, for example it reads data from the database and does some inserts correctly but others not.Thanks in advance. |
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2009-05-18 : 17:13:46
|
| Generally speaking to trouble shoot an application you need to catch and report all the errors you encounter. Sometimes unhandled exceptions will be logged in the event log of the machine running the application. Look there as well. Often sql errors come down to permissioning problems. You can also capture the exact sql you are sending to the sql server using Sql Profiler. Other common problems are that the statements actually sent are not what the developer intended. You can see those problems using profiler.Be One with the OptimizerTG |
 |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2009-05-18 : 17:14:13
|
| Is this a program you wrote or that you bought? If it's one you bought, go back to the manual or call their tech support, because this is not a SQL Server error.If it is one that you wrote, then you need to capture error messages and find out what's going on, because somewhere you are not correctly connecting to the server you think you are. Typically, you want one central bit of code that handles the connectivity so you know your whole app is working or is not.--------------------------------------------Brand yourself at EmeraldCityDomains.com |
|
|
|
|
|
|
Help! Can´t find the problem