I am hoping that some SQL Server version 7 administrators will try something out for me – that is to check the current setting for the remote query timeout on their install by using:
sp_configure ‘remote query timeout’
I am interested in the run_value and config_value.
I am interested in all results, but I am researching whether anyone has ever had the need to change it from the default of zero (0). If they have, then I’m interested to hear about why they did it.
Thanks for your help.
BTW, the reason for asking this is because this setting has been changed on a shared server I have a database on. IT providers changed it to 600 (ten minutes) and this has the unintended result of failing select statements into some linked servers which were set up for downloading data (Microsoft have confirmed this is an issue). The IT providers refuse to change it back to zero, even temporarily once a month because it would present an unacceptable risk to other databases.
sp_configure ‘remote query timeout’
I am interested in the run_value and config_value.
I am interested in all results, but I am researching whether anyone has ever had the need to change it from the default of zero (0). If they have, then I’m interested to hear about why they did it.
Thanks for your help.
BTW, the reason for asking this is because this setting has been changed on a shared server I have a database on. IT providers changed it to 600 (ten minutes) and this has the unintended result of failing select statements into some linked servers which were set up for downloading data (Microsoft have confirmed this is an issue). The IT providers refuse to change it back to zero, even temporarily once a month because it would present an unacceptable risk to other databases.