UkDraxion

Hi all, I have astrange one here, so let me explain. I have a sql 2005 Instance which has been running for some time now. One of our users has had connection issues starting recently, he has been able to connect when the instance was first setup no problems, but of late he has been unable to connect, and gets a message saying 'Tomeout Expired. The timeput period elapsed prior to completion of the operation or the server is not responding'. I tried it myself and it connected instantly. We did some testing, and it seems his initial connection attempt time's out as before, but if we cancel that connection and try again withought closing the console it goes in straight away and he can work as normal. But if we cancel that connection and open a new console and try again it too times out with same error message, this is such a bizzare issue. Has anyone come accross this before? Cheers

Hi all. We have in our organisation an application which has been running for years, and suddenly over the last month or so it's been steadily grinding to a halt. Simple queries (two in particular to be precise) which take seconds to run in QA, sometimes take hours from the application front-end. One is so simple. Select column a, b, c, d from table 1 order by column a desc. The second is just a plain ordinary select a, b, c, d from table 1. On each occassion it's the same table 1. As far as I am aware no upgrades or changes have been made to the DB or front-end application in the past year or so. I have so far reindexed the DB, checked with index tuning wizard (no issues found there), checked the server, that appears to be running ok, no additional stress there. We see some blocking against that particular DB, but mostly long running queries. The sql server back-end has other DB's on it, but non of the customers are complaining about those. Not sure what else i could try on this occassion. Cheers.

Hi all, I found the issue. We had not opened up the UDP port 1434, once that was opened it worked fine. Cheers

Hi all, this is my first post so please be gentle. I have a problem connecting to an instance on one of our sql servers. The sql server currently has a number of other instances on it which seem to be working fine, but this one instance is proving a little awkwards. I was able at one point to access the instance from sql management studio on my laptop, but then it was left for a while with no use and this morning I tried again and could not connect from anything outside the server. I have checked the services are running ok. I cannot ping the instance directly, but our server team guys can, I can still map a drive to the instance but that about all. Getting the error message 'sql network interfaces error 26 error locating server instance specified microsoft sql server' when I try to connect from the management console. is there any reason why it should stop working afte a period of time, and what could be causing this issue? Cheers