I'm planning on installing SQL 2000 on a 2 node Windows
Server 2003. I want to have both nodes to be active SQL
servers and they will both be available for each other in
the case of a Failure. Any issues regarding this tipe of
setup?
Is there a way to setup the second node without having to
create a new instance on the second node? I would prefer
only to have different Computer names?
Thanks
Christian Poupart
chpoupart@.ogilvyrenault.com
Each instance of a cluster requires a separate virtual server. IF you want
two SQL instances, you will need two virtual servers, each containing its
own instance.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Christian Poupart" <chpoupart@.ogilvyrenault.com> wrote in message
news:1f94f01c4588a$e49752b0$a601280a@.phx.gbl...
> I'm planning on installing SQL 2000 on a 2 node Windows
> Server 2003. I want to have both nodes to be active SQL
> servers and they will both be available for each other in
> the case of a Failure. Any issues regarding this tipe of
> setup?
> Is there a way to setup the second node without having to
> create a new instance on the second node? I would prefer
> only to have different Computer names?
> Thanks
> Christian Poupart
> chpoupart@.ogilvyrenault.com
Showing posts with label planning. Show all posts
Showing posts with label planning. Show all posts
Thursday, March 22, 2012
Sunday, March 11, 2012
Active Active Clustering
I am planning to install Multiple Instance SQL Server 2000 cluster (two instances) on Windows 2000 Advanced servers (two nodes). All the examples I have seen deal with Single Instance SQL Servers. What I have read that in case of a Multiple Instance ins
tallation you merely run the SQL Server setup program another time after the installation of the first virtual server is completed. I have also read that during the install you chose one of the nodes (one of the two Windows boxes) as the owner of one virt
ual SQL Server instance. Then when you run the SQL Server setup program a second time, you specify the other node as the owner of the other SQL Server virtual instance.
My question is this: where do I specify a node as the owner of a particular SQL Server instance? On the SQL Server 2000 Failover Clustering white paper, Appendix B, http://www.microsoft.com/technet/pro...x?pf=true#XSLT
section133121120120 step 10 shows a dialog box where you specify the configured nodes. Do I specify only one node as the Configured Node? Is that how I identify the node that owns the particular SQL Server instance? Or do I we identify it some other way
? Thanks.
I am sorry that I used the old terminology from SQL Server 7.0. Thanks in advance for your help.
|||You have a preferred owners list on the properties page of the resource
group. The host nodes are listed in preferred order. The actual ownership
can be changed by moving the group to a particular host. During setup, you
install SQL from the node that owns the disk resource where you intend to
put SQL. The dialog box you refer to selects the nodes that SQL is allowed
to run on. Once SQL is installed, the instance can be moved to any allowed
node.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"EY" <shafaqrahim@.hotmail.com> wrote in message
news:69BBB5B8-E23A-451F-B8FE-EAADD88A8E56@.microsoft.com...
> I am planning to install Multiple Instance SQL Server 2000 cluster (two
instances) on Windows 2000 Advanced servers (two nodes). All the examples I
have seen deal with Single Instance SQL Servers. What I have read that in
case of a Multiple Instance installation you merely run the SQL Server setup
program another time after the installation of the first virtual server is
completed. I have also read that during the install you chose one of the
nodes (one of the two Windows boxes) as the owner of one virtual SQL Server
instance. Then when you run the SQL Server setup program a second time, you
specify the other node as the owner of the other SQL Server virtual
instance.
> My question is this: where do I specify a node as the owner of a
particular SQL Server instance? On the SQL Server 2000 Failover Clustering
white paper, Appendix B,
http://www.microsoft.com/technet/pro...on133121120120
step 10 shows a dialog box where you specify the configured nodes. Do I
specify only one node as the Configured Node? Is that how I identify the
node that owns the particular SQL Server instance? Or do I we identify it
some other way? Thanks.
>
|||Thanks Mr. Hitten for answering my question so promptly.
tallation you merely run the SQL Server setup program another time after the installation of the first virtual server is completed. I have also read that during the install you chose one of the nodes (one of the two Windows boxes) as the owner of one virt
ual SQL Server instance. Then when you run the SQL Server setup program a second time, you specify the other node as the owner of the other SQL Server virtual instance.
My question is this: where do I specify a node as the owner of a particular SQL Server instance? On the SQL Server 2000 Failover Clustering white paper, Appendix B, http://www.microsoft.com/technet/pro...x?pf=true#XSLT
section133121120120 step 10 shows a dialog box where you specify the configured nodes. Do I specify only one node as the Configured Node? Is that how I identify the node that owns the particular SQL Server instance? Or do I we identify it some other way
? Thanks.
I am sorry that I used the old terminology from SQL Server 7.0. Thanks in advance for your help.
|||You have a preferred owners list on the properties page of the resource
group. The host nodes are listed in preferred order. The actual ownership
can be changed by moving the group to a particular host. During setup, you
install SQL from the node that owns the disk resource where you intend to
put SQL. The dialog box you refer to selects the nodes that SQL is allowed
to run on. Once SQL is installed, the instance can be moved to any allowed
node.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"EY" <shafaqrahim@.hotmail.com> wrote in message
news:69BBB5B8-E23A-451F-B8FE-EAADD88A8E56@.microsoft.com...
> I am planning to install Multiple Instance SQL Server 2000 cluster (two
instances) on Windows 2000 Advanced servers (two nodes). All the examples I
have seen deal with Single Instance SQL Servers. What I have read that in
case of a Multiple Instance installation you merely run the SQL Server setup
program another time after the installation of the first virtual server is
completed. I have also read that during the install you chose one of the
nodes (one of the two Windows boxes) as the owner of one virtual SQL Server
instance. Then when you run the SQL Server setup program a second time, you
specify the other node as the owner of the other SQL Server virtual
instance.
> My question is this: where do I specify a node as the owner of a
particular SQL Server instance? On the SQL Server 2000 Failover Clustering
white paper, Appendix B,
http://www.microsoft.com/technet/pro...on133121120120
step 10 shows a dialog box where you specify the configured nodes. Do I
specify only one node as the Configured Node? Is that how I identify the
node that owns the particular SQL Server instance? Or do I we identify it
some other way? Thanks.
>
|||Thanks Mr. Hitten for answering my question so promptly.
Thursday, February 9, 2012
Accessing mySQL from .NET
Hello all,
We are planning to migrate an application written in Perl + mySQL to .NET + MS-SQL Server. The test machine now has SQL Server running. During the development phase in .NET, we would want to access the mySQL database which is being updated at real time, from the Windows box. This is how I think it has to be done:
1. Use DTS to migrate data from mySQL. Does DTS take care of migrating schema and the difference in data types between the mySQL and MS-SQL? Is there any 3rd party software out there that takes care of the migration without any manual labor?
2. Synchronize the data between 2 DBs by creating some kind of a batch job? If so, whats the best way of doing this?
Instead, is it easier to access the live mySQL database on the Linux box from the .NET code and move the DB only after development in the new environment is completed?
Any help/ideas is greatly appreciated.
TIAIn order to handle the schema, you use the transformation portion of dts(data transformation task). Do you need to have "live" information in the sql server database while you are creating the application in .Net ? If not, just take a snapshot of the data from mysql to sql server and perform the complete migration when you are ready to switch database servers.|||Ok, so if you have an ODBC driver for mySQL you should be able to use DTS to do SQL-92 compliant stuff with your old db.
In all honesty I would suggest that you move these two things one at a time, move either your database or your code but not both at the same time, your testing and debugging will be a nightmare otherwise.
Dan
We are planning to migrate an application written in Perl + mySQL to .NET + MS-SQL Server. The test machine now has SQL Server running. During the development phase in .NET, we would want to access the mySQL database which is being updated at real time, from the Windows box. This is how I think it has to be done:
1. Use DTS to migrate data from mySQL. Does DTS take care of migrating schema and the difference in data types between the mySQL and MS-SQL? Is there any 3rd party software out there that takes care of the migration without any manual labor?
2. Synchronize the data between 2 DBs by creating some kind of a batch job? If so, whats the best way of doing this?
Instead, is it easier to access the live mySQL database on the Linux box from the .NET code and move the DB only after development in the new environment is completed?
Any help/ideas is greatly appreciated.
TIAIn order to handle the schema, you use the transformation portion of dts(data transformation task). Do you need to have "live" information in the sql server database while you are creating the application in .Net ? If not, just take a snapshot of the data from mysql to sql server and perform the complete migration when you are ready to switch database servers.|||Ok, so if you have an ODBC driver for mySQL you should be able to use DTS to do SQL-92 compliant stuff with your old db.
In all honesty I would suggest that you move these two things one at a time, move either your database or your code but not both at the same time, your testing and debugging will be a nightmare otherwise.
Dan
Subscribe to:
Posts (Atom)