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 |
|
koup
Starting Member
3 Posts |
 Posted - 2006-11-13 : 14:16:57
|
| I have a driving crazy interesting Problem. I have to connect to a MS-SQL Server over ISDN (64-128 Kbits connection). The Enterprise Manager connects to the IP address but after klicking on the db folder the program do something for about 5-10 min. and writs “(no Elements)” in the db Folder after that. First I’ve tried it, out of my Java program with a jtds driver. I execute a query SELECT * FROM on a Table with more then 25 attributes or a query with complex WHERE statement on a big table. No error, no nothing the program just waiting for something. So I think the same problem happens with the Enterprise Manager when he starts to read the metadata of the DB’s.Now why I am going crazy here: Other Complex queries (almost all) working well. If I connect over Cable or network everything is fine. Some computers, with almost the same configuration, working well over ISDN (Enterprise Manager and queries out of the program). And if I use a SELECT statement with 24 attributes and a simple WHERE (number = ‘1111’) it works fine too. Network configuration, Windows version, and firewall checked-> no new Information gained. For some reason some Computers work over ISDN and some not. It must be some hardware or configuration of the PCs in the Mix with the slow connection and some wrong settings of the server, but I don’t really know. There could be a timeout problem but i am not sure.I have no idea what to do. Any Help would be great here. Thanks a lot for any help koup. |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2006-11-13 : 14:31:08
|
| See if there are any firewall rules in place. You might want to look at the various computers and see if they are all in the same segment. This should be something you work with the network group closely on.Have you ran profiler to see if the "non-working" computers are hitting the SQL Server at all? If not, I would verify. See if you are getting authentication errors. If they are not connecting at all, even to be rejected, you know it's not a SQL Server issue. If they can't authenticate, you have security. It goes on from there. Basic troubleshooting.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
koup
Starting Member
3 Posts |
Posted - 2006-11-13 : 15:19:29
|
| Hi derrickleggett,thx for the quick help. Firewall is definitly not a problem. I even activated a windows firewall once just to be sure, since one system where no problems occured had Windows firewall on. I have an ISDN router and a possibility to get in the network of the company but my Software have to work with isdn routers and this is the place where problems beginn since one comp works and another dont. MS PRofiler? Well yes i get connection and everything working fine till a complex query is executed on the server. The client stucks since the answer is never send or lost and after 3-5 min the connection to the server is lost because no information is transmitted. I havened seen any error on the server. So there must be something else...thx koup |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2006-11-13 : 18:39:50
|
quote:
MS PRofiler? Well yes i get connection and everything working fine till a complex query is executed on the server. The client stucks since the answer is never send or lost and after 3-5 min the connection to the server is lost because no information is transmitted. I havened seen any error on the server. So there must be something else...thx koup
So, you actually ran Profiler and verified things were working and these computers were hitting the SQL Server?MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
koup
Starting Member
3 Posts |
Posted - 2006-11-14 : 06:42:36
|
quote:
So, you actually ran Profiler and verified things were working and these computers were hitting the SQL Server?
Hi,yep all queries reached the server but after THE query no work is done on the server. So perhaps i need a way to get information about the outgoing data from the server. Perhaps some logs reachable from the Enterprise Manager.Thx a lot koup |
|
|
|
|
|
|
|
|
SQL 2000 Problems with ISDN connection