MS SQL Server 2005 timeout error when using Management Studio

Does anyone know, how to solve "timeout period elapsed prior to the
completion of the operation" problem which occured when I tried to update a
column value using MS SQL Server 2005 Management Studio (SMS).
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
Thanks
Hi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:

> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
>
|||Venkat N wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
The simple answer, and the one you're likely to get from this group, is
to not modify your tables using the GUI. It's simply not intended for
that use.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

MS SQL Server 2005 timeout error when using Management Studio

Hi,
When I try to update a column value using MS SQL Server 2005 Management
Studio (SMS), I am getting "timeout period elapsed prior to the completion
of the operation".
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
Thanks
VN
Hi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:

> Hi,
> When I try to update a column value using MS SQL Server 2005 Management
> Studio (SMS), I am getting "timeout period elapsed prior to the completion
> of the operation".
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
> VN
>
>

MS SQL Server 2005 timeout error when using Management Studio

Hi,
When I try to update a column value using MS SQL Server 2005 Management
Studio (SMS), I am getting "timeout period elapsed prior to the completion
of the operation".
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
Thanks
VNHi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:

> Hi,
> When I try to update a column value using MS SQL Server 2005 Management
> Studio (SMS), I am getting "timeout period elapsed prior to the completion
> of the operation".
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where eve
r
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having an
y
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
> VN
>
>sql

MS SQL Server 2005 timeout error when using Management Studio

Does anyone know, how to solve "timeout period elapsed prior to the
completion of the operation" problem which occured when I tried to update a
column value using MS SQL Server 2005 Management Studio (SMS).
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
ThanksHi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:

> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update
a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where eve
r
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having an
y
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
>|||Venkat N wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update
a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where eve
r
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having an
y
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
The simple answer, and the one you're likely to get from this group, is
to not modify your tables using the GUI. It's simply not intended for
that use.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

MS SQL Server 2005 timeout error when using Management Studio

Does anyone know, how to solve "timeout period elapsed prior to the
completion of the operation" problem which occured when I tried to update a
column value using MS SQL Server 2005 Management Studio (SMS).
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
ThanksHi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
>|||Venkat N wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
The simple answer, and the one you're likely to get from this group, is
to not modify your tables using the GUI. It's simply not intended for
that use.
Tracy McKibben
MCDBA
http://www.realsqlguy.com