Hi,
I've configured mirroring on the database and selected the high safety
without automatic failover. It all seems fine.
Now the problem is in the mirroring screen I can't select the High
performance mode (Asynchronous ). I would like to test this option as well. I
know I can't select the automatic failover option cause I don't have a
witness set-up but why I can't select Asynchronous mode? Any ideas? Thanks.
Panos.
Panos.
Hello Panos,
It is only available in Enterprise edition or Developer edition
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> Hi,
> I've configured mirroring on the database and selected the high safety
> without automatic failover. It all seems fine.
> Now the problem is in the mirroring screen I can't select the High
> performance mode (Asynchronous ). I would like to test this option as
> well. I know I can't select the automatic failover option cause I
> don't have a witness set-up but why I can't select Asynchronous mode?
> Any ideas? Thanks.
> Panos.
> Panos.
>
Showing posts with label ive. Show all posts
Showing posts with label ive. Show all posts
Wednesday, March 28, 2012
Mirrored db - Witness server multiple networks
All,
I've just completed setting up a mirrored db with 2 servers that reside on
different networks. All the appropriate routes are added and the boxes see
each other fine both at the OS level and the SQL server level. My witness
server is a machine with 2 nics, each can talk to each network and it sees
both sql servers just fine. IP Forwarding is enabled. I've succesfully
configured the Primary to use the witness server and it sees it fine. However
the Mirror server is constantly reporting that the witness server is
disconnected. I can connect through management studio and every other just
fine. Anything I need due to the fact that the primary and the mirror are on
different networks when it comes to the witness box? Any suggestions
appreciated. There are no firewalls in play.
Thanks.
Hi
I am not sure why you have not configured these on their own subnet? I would
contact PSS to see if this is possible.
John
"sqlboy2000" wrote:
> All,
> I've just completed setting up a mirrored db with 2 servers that reside on
> different networks. All the appropriate routes are added and the boxes see
> each other fine both at the OS level and the SQL server level. My witness
> server is a machine with 2 nics, each can talk to each network and it sees
> both sql servers just fine. IP Forwarding is enabled. I've succesfully
> configured the Primary to use the witness server and it sees it fine. However
> the Mirror server is constantly reporting that the witness server is
> disconnected. I can connect through management studio and every other just
> fine. Anything I need due to the fact that the primary and the mirror are on
> different networks when it comes to the witness box? Any suggestions
> appreciated. There are no firewalls in play.
> Thanks.
|||You won't be able to use Windows authentication across networks - you will
need to use certificates.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:6605AA68-D48F-4827-A583-1302CBEB55C5@.microsoft.com...
> All,
> I've just completed setting up a mirrored db with 2 servers that reside on
> different networks. All the appropriate routes are added and the boxes see
> each other fine both at the OS level and the SQL server level. My witness
> server is a machine with 2 nics, each can talk to each network and it sees
> both sql servers just fine. IP Forwarding is enabled. I've succesfully
> configured the Primary to use the witness server and it sees it fine.
> However
> the Mirror server is constantly reporting that the witness server is
> disconnected. I can connect through management studio and every other just
> fine. Anything I need due to the fact that the primary and the mirror are
> on
> different networks when it comes to the witness box? Any suggestions
> appreciated. There are no firewalls in play.
> Thanks.
|||By "different networks" I meant different subnets.
"Roger Wolter[MSFT]" wrote:
> You won't be able to use Windows authentication across networks - you will
> need to use certificates.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
> news:6605AA68-D48F-4827-A583-1302CBEB55C5@.microsoft.com...
>
>
I've just completed setting up a mirrored db with 2 servers that reside on
different networks. All the appropriate routes are added and the boxes see
each other fine both at the OS level and the SQL server level. My witness
server is a machine with 2 nics, each can talk to each network and it sees
both sql servers just fine. IP Forwarding is enabled. I've succesfully
configured the Primary to use the witness server and it sees it fine. However
the Mirror server is constantly reporting that the witness server is
disconnected. I can connect through management studio and every other just
fine. Anything I need due to the fact that the primary and the mirror are on
different networks when it comes to the witness box? Any suggestions
appreciated. There are no firewalls in play.
Thanks.
Hi
I am not sure why you have not configured these on their own subnet? I would
contact PSS to see if this is possible.
John
"sqlboy2000" wrote:
> All,
> I've just completed setting up a mirrored db with 2 servers that reside on
> different networks. All the appropriate routes are added and the boxes see
> each other fine both at the OS level and the SQL server level. My witness
> server is a machine with 2 nics, each can talk to each network and it sees
> both sql servers just fine. IP Forwarding is enabled. I've succesfully
> configured the Primary to use the witness server and it sees it fine. However
> the Mirror server is constantly reporting that the witness server is
> disconnected. I can connect through management studio and every other just
> fine. Anything I need due to the fact that the primary and the mirror are on
> different networks when it comes to the witness box? Any suggestions
> appreciated. There are no firewalls in play.
> Thanks.
|||You won't be able to use Windows authentication across networks - you will
need to use certificates.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:6605AA68-D48F-4827-A583-1302CBEB55C5@.microsoft.com...
> All,
> I've just completed setting up a mirrored db with 2 servers that reside on
> different networks. All the appropriate routes are added and the boxes see
> each other fine both at the OS level and the SQL server level. My witness
> server is a machine with 2 nics, each can talk to each network and it sees
> both sql servers just fine. IP Forwarding is enabled. I've succesfully
> configured the Primary to use the witness server and it sees it fine.
> However
> the Mirror server is constantly reporting that the witness server is
> disconnected. I can connect through management studio and every other just
> fine. Anything I need due to the fact that the primary and the mirror are
> on
> different networks when it comes to the witness box? Any suggestions
> appreciated. There are no firewalls in play.
> Thanks.
|||By "different networks" I meant different subnets.
"Roger Wolter[MSFT]" wrote:
> You won't be able to use Windows authentication across networks - you will
> need to use certificates.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
> news:6605AA68-D48F-4827-A583-1302CBEB55C5@.microsoft.com...
>
>
Monday, February 20, 2012
Migrating Sybase to SQL Server 2000
I'm currently involving in a project in migrating from
Sybase to SQL Server 2000. I've been able to
successfully (and conveniently) import my tables/data.
My question involves the Stored Procedures. Can these
stored procedures be import w/ a wizard (i.e. the way my
tables/data have been converted)? Or must I manually
create new SP's in SQL Server, making the necessary
changes (Rollback trigger, transaction isolation levels,
etc.) on the fly?
I think that you must to do the necessary changes.
The sybase code is not totally compatible with sql2k.
After this forget sybase, please.
<anonymous@.discussions.microsoft.com> escreveu na mensagem
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
|||Hi,
Have a look into the below article from MS:-
http://www.microsoft.com/resources/d...reskit/en-us/p
art2/c0661.mspx
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
|||Yes, you must make the changes manually, but there should not be a whole lot
of changes...They are doc'd in the article mentioned previously.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
Sybase to SQL Server 2000. I've been able to
successfully (and conveniently) import my tables/data.
My question involves the Stored Procedures. Can these
stored procedures be import w/ a wizard (i.e. the way my
tables/data have been converted)? Or must I manually
create new SP's in SQL Server, making the necessary
changes (Rollback trigger, transaction isolation levels,
etc.) on the fly?
I think that you must to do the necessary changes.
The sybase code is not totally compatible with sql2k.
After this forget sybase, please.
<anonymous@.discussions.microsoft.com> escreveu na mensagem
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
|||Hi,
Have a look into the below article from MS:-
http://www.microsoft.com/resources/d...reskit/en-us/p
art2/c0661.mspx
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
|||Yes, you must make the changes manually, but there should not be a whole lot
of changes...They are doc'd in the article mentioned previously.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
Subscribe to:
Posts (Atom)