We currently have a w2003 SQL cluster and would like to add a second cluster
to the infrastructure. Their plan is to have one online serving customers so
the other cluster may have the db restored... Is there a way to get the
databases on both clusters mirrored? We have the cluster to provide HA, I may
need a big hammer to protect the data from developers fingers!
Any suggestions?
Thanks,
Rodney
Rodney,
You might consider log shipping. Here is an article from SQL Server
magazine by Ron Talmage that you might find interesting.
http://tinyurl.com/46h45
Also, transactional replication is used by some to keep another server
refreshed for queries, reporting, etc.
Narayan Kondreddi has a replication FAQ at
http://vyaskn.tripod.com/repl_ques.htm
Russell Fields
"Rodney" <Rodney@.discussions.microsoft.com> wrote in message
news:8A87A93D-889F-477A-9209-C3D5E1EE32F7@.microsoft.com...
> We currently have a w2003 SQL cluster and would like to add a second
cluster
> to the infrastructure. Their plan is to have one online serving customers
so
> the other cluster may have the db restored... Is there a way to get the
> databases on both clusters mirrored? We have the cluster to provide HA, I
may
> need a big hammer to protect the data from developers fingers!
> Any suggestions?
> Thanks,
> Rodney
Showing posts with label w2003. Show all posts
Showing posts with label w2003. Show all posts
Thursday, March 22, 2012
Friday, February 10, 2012
Can not registre SQL in Enterprise Manager
Hello,
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.It's the login timeout you want to try increasing. See my
reply to your post in .connect for steps to do this.
-Sue
On Sat, 17 Apr 2004 12:20:44 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (60
0
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.It's the login timeout you want to try increasing. See my
reply to your post in .connect for steps to do this.
-Sue
On Sat, 17 Apr 2004 12:20:44 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (60
0
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>
Can not registre SQL in Enterprise Manager
Hello,
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.
It's the login timeout you want to try increasing. See my
reply to your post in .connect for steps to do this.
-Sue
On Sat, 17 Apr 2004 12:20:44 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (600
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.
It's the login timeout you want to try increasing. See my
reply to your post in .connect for steps to do this.
-Sue
On Sat, 17 Apr 2004 12:20:44 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (600
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>
Can not register SQLServer2000 in Enterprise Manager
Hello,
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.
Charles,
Try increasing the login timeout used by Enterprise Manager.
In Enterprise Manager, go to the menu to Tools, then select
Options. Click on the Advanced tab and increase the login
timeout from the default 4 seconds. Try 10 or 15 seconds
instead and see if that helps.
-Sue
On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (600
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>
|||Yes !!!! Thanks a lot Sue.
Have a nice day,
Charles.
"Sue Hoegemeier" <Sue_H@.nomail.please> escribi en el mensaje
news:4eg680hvekta8k50ar1c21fadjcsn7p62i@.4ax.com... [vbcol=seagreen]
> Charles,
> Try increasing the login timeout used by Enterprise Manager.
> In Enterprise Manager, go to the menu to Tools, then select
> Options. Click on the Advanced tab and increase the login
> timeout from the default 4 seconds. Try 10 or 15 seconds
> instead and see if that helps.
> -Sue
> On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
> <ccolell@.softeng.es> wrote:
(600
>
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.
Charles,
Try increasing the login timeout used by Enterprise Manager.
In Enterprise Manager, go to the menu to Tools, then select
Options. Click on the Advanced tab and increase the login
timeout from the default 4 seconds. Try 10 or 15 seconds
instead and see if that helps.
-Sue
On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (600
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>
|||Yes !!!! Thanks a lot Sue.
Have a nice day,
Charles.
"Sue Hoegemeier" <Sue_H@.nomail.please> escribi en el mensaje
news:4eg680hvekta8k50ar1c21fadjcsn7p62i@.4ax.com... [vbcol=seagreen]
> Charles,
> Try increasing the login timeout used by Enterprise Manager.
> In Enterprise Manager, go to the menu to Tools, then select
> Options. Click on the Advanced tab and increase the login
> timeout from the default 4 seconds. Try 10 or 15 seconds
> instead and see if that helps.
> -Sue
> On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
> <ccolell@.softeng.es> wrote:
(600
>
Can not register SQLServer2000 in Enterprise Manager
Hello,
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.Charles,
Try increasing the login timeout used by Enterprise Manager.
In Enterprise Manager, go to the menu to Tools, then select
Options. Click on the Advanced tab and increase the login
timeout from the default 4 seconds. Try 10 or 15 seconds
instead and see if that helps.
-Sue
On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (60
0
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>|||Yes !!!! Thanks a lot Sue.
Have a nice day,
Charles.
"Sue Hoegemeier" <Sue_H@.nomail.please> escribi en el mensaje
news:4eg680hvekta8k50ar1c21fadjcsn7p62i@.
4ax.com...
> Charles,
> Try increasing the login timeout used by Enterprise Manager.
> In Enterprise Manager, go to the menu to Tools, then select
> Options. Click on the Advanced tab and increase the login
> timeout from the default 4 seconds. Try 10 or 15 seconds
> instead and see if that helps.
> -Sue
> On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
> <ccolell@.softeng.es> wrote:
>
(600[vbcol=seagreen]
>
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.Charles,
Try increasing the login timeout used by Enterprise Manager.
In Enterprise Manager, go to the menu to Tools, then select
Options. Click on the Advanced tab and increase the login
timeout from the default 4 seconds. Try 10 or 15 seconds
instead and see if that helps.
-Sue
On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (60
0
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>|||Yes !!!! Thanks a lot Sue.
Have a nice day,
Charles.
"Sue Hoegemeier" <Sue_H@.nomail.please> escribi en el mensaje
news:4eg680hvekta8k50ar1c21fadjcsn7p62i@.
4ax.com...
> Charles,
> Try increasing the login timeout used by Enterprise Manager.
> In Enterprise Manager, go to the menu to Tools, then select
> Options. Click on the Advanced tab and increase the login
> timeout from the default 4 seconds. Try 10 or 15 seconds
> instead and see if that helps.
> -Sue
> On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
> <ccolell@.softeng.es> wrote:
>
(600[vbcol=seagreen]
>
Subscribe to:
Posts (Atom)