Post reply

Using SQL 2005 Server Management Studio for SQL 2000 based servers.

  • August 5, 2008 at 11:14 am

    #210899

    I'm probably not alone on this one and I have searched but I can't seem to find the setting I need to stop the View from timing out. This happens when using 2005 Server Management Studio to view/edit views based on a remote SQL 2000 server. The quick solution is to use SQL 2000 enterprise manager to view/edit the views but I like the interface of 2005. As well if I copy and paste the code into a new 2005 query window it executes fine, no time outs? Has anyone here run across the setting to adjust the execution time for views?

    Thanks

  • August 5, 2008 at 11:26 am

    #853361

    In the options menu, there's an option for forcing a timeout after a certain amount of execution time.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • August 5, 2008 at 11:27 am

    #853362

    There are not timeouts for objects, it's a connection timeout or query timeout that you need to set.

  • August 5, 2008 at 12:09 pm

    #853396

    Here is a screen shot of my 2005 server options.

    What I do not understand is how the same SQL code works in a query window but times out in the view designer. There must be a separate setting for "time out" when using 2005 view designer.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply