Can't connect to database...

[cusimar9]

I'm using Dreamweaver MX 2004, using ASP .net and MS SQL Server, and I can't retrieve the list of stored procedures from the database

The database connects fine, I can get the list of tables and views, but when I try and get the list of stored procedures I get a 'Loading Database Schema...' message for ages then it just comes back and says it couldn't find any.

This was working fine yesterday, there's lots of stored procedures so it took about a minute to retrieve the list. Now it just looks like its timing out and not retrieving anything.

Any ideas?

[phpnovice]

Possibly more stored procedures were added -- pushing you over the limit on your script or database timeout setting.

[cusimar9]

Well how do I change this timeout setting?

I found this page:

http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_14438

But it hasn't made any difference

[phpnovice]

There are at least three different, and possibly other, timeout settings that must be considered. There is a session timeout (but, probably, not part of your problem), a script execution timeout, and a database connection timeout -- all of which are minded by the server involved (web server vs. database server). Plus, there are usually two different ways to set these timeouts -- from the server (a default for all applications) and from the client (in script only and for use with that application only).

If your application is running in a local environment only (includes having the server on the same machine as the client application), then that registry setting would be efficacious. If your application is running in client-server mode, and the server is not on your local machine, then that registry setting would have to be changed on the server machine -- not on your local machine.

I recommend that you get your server and database administrators involved in the issue.

[cusimar9]

Dreamweaver isn't installed on the server, its installed on my machine. So obviously that registry key won't exist on the server.

[phpnovice]

That doesn't answer the question of where is the database server? ...and, if using a browser, where is the web server?

[cusimar9]

Sorry I can't be making myself clear:

There's a server called ST1 which has the database and IIS installed. I access the website from my laptop through my web browser. I develop the website from my laptop.

[phpnovice]

OK, then the *only* thing you can do from your PC, is to code whatever timeout settings are available to be changed from the client end. I'm not familiar with ASP.NET, so I can't tell you what all to which you have access. With Classic ASP, it is easy to set your own session timeout (Session.Timeout (http://msdn.microsoft.com/library/en-us/iissdk/html/a3b9a343-7704-4607-becb-ba143d3d62b9.asp)) -- but I don't think that one is your problem. You can also set your own script execution timeout (Server.ScriptTimeout (http://msdn.microsoft.com/library/en-us/iissdk/html/429c1800-7d19-4011-a1ca-482a43b1abef.asp)). For the database connection (Classic ADO), there is both a connection timeout (ConnectionTimeout (http://msdn.microsoft.com/library/en-us/ado270/htm/mdproconnectiontimeout.asp)) and a command execution timeout (CommandTimeout (http://msdn.microsoft.com/library/en-us/ado270/htm/mdprocommandtimeout.asp)).

[cusimar9]

Possibly another area of confusion... it isn't the webpage that times out... that works fine

Its in the dreamweaver environment. When Dreamweaver tries to connect to the database to retrieve the list of stored procedures it times out.

I think that's why we're both confused!

[phpnovice]

I'm not confused. ;) All I've said, from the beginning, is that it is probably either a script timeout or a database connection timeout. It doesn't matter whether you want to talk about your web page, your browser, or your development application environment. All three of these can suffer from the same problem when it comes to accessing either the web server (IIS) or the database server. The script timeout affects your access of the web server and the connection/command timeout affects your access of the database server. Normally, you have to go through the web server to get to the database server -- as it is the web server that is executing your server-side script which accesses the database.