Showing posts with label cluster. Show all posts
Showing posts with label cluster. Show all posts

Monday, March 19, 2012

Dumb Transaction log question.

I know I've been asking a lot of dumb questions here lately but - One must
learn somewhere.
In my test lab cluster that I'm building, W2k3 Cluster admin put each of my
physical disks in its own group. Now I'm keep one for the cluster group, and
one for the MSDTC, which leaves me four. I'm going to use 1 disk for data
and 1 disk for tranaction logs for each instance of sql. Are there any
advantages in putting the disks in the same group. (that is putting 1 disk
for the transaction logs and 1 disk for the data in the same group). I don't
see any advantages, but I'll ask anyway.
Also on transaction logs, where do I go to move the default location of
transaction logs in each instance of SQL.
The physical disk resources need to be in the same group as the SQL server resource that will use them, and the SQL server resource needs to have a dependancy on both physical disk resources.
As to the default locations, they are specified on the "Database Settings" tab of the Server Properties dialog in EM. (Not the "Edit registration properties" near the top of the right-click menu, but the "properties" near the bottom)
If you want to move database files or transaction logs, you can detach the database, move the files, and reattach the database files by specifying the new paths in the attach dialog box. Right-click on the database and select "all tasks >> detach" to detach the database. To attach the database, right click on the "databases" container and select "all tasks >> attach database".
You can also use T-SQL to call sp_detach and sp_attach, but the GUI works fine.
Just make sure that the SQL server resource has the physical disk resource(s) as a dependancy(ies) or you will not be able to attach the files.
Play around until you are comfortable with this stuff before you go live. It's quite geeky fun!
Good Luck
jg

Quote:

Originally posted by Wayne
I know I've been asking a lot of dumb questions here lately but - One must
learn somewhere.
In my test lab cluster that I'm building, W2k3 Cluster admin put each of my
physical disks in its own group. Now I'm keep one for the cluster group, and
one for the MSDTC, which leaves me four. I'm going to use 1 disk for data
and 1 disk for tranaction logs for each instance of sql. Are there any
advantages in putting the disks in the same group. (that is putting 1 disk
for the transaction logs and 1 disk for the data in the same group). I don't
see any advantages, but I'll ask anyway.
Also on transaction logs, where do I go to move the default location of
transaction logs in each instance of SQL.

|||There is no dumb question.
Its a good question. Since you are using one disk for data and another disk for log, both the disk resources will need to be in SAME SQL Server group (along with other SQL Server resources). Infact, if they are on
seperate group SQL Server cannot use it. During installation, we can just specify one disk. After installation, one has to move the second disk to the SQL group, take SQL Server resource offline, add the second disk
as a dependency for SQL Server resource and then take the SQL Server resource online. After that you can use your normal steps/techniques to move the logs on the second disk.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Friday, March 9, 2012

Dual Nics problems with SQL 2000 Cluster

HI,
I have two Dell Servers(For high avaiablity each machines have three intel gigabit Networkcards,one for heatbeat,two for clients link) with a disk array.I have installed Windows2003 and setup the Cluster,it's worked well,then i installed sql server 2000 E
E on them through many articles(I created tow sql ip address because i have two nics on each servers).When one node fail,the resource can shift to another node,the sql service is still available.Ok,but when one switch of the two seperate network is down,t
he sql service is nolonger avaliable,there is no use for another network cards on each node? Is there any articles for sql server's installation for nodes with three nics?
Another problem is that it take about 3 min for sql resource such as sql ip address,sql network name,sql server etc to transmit from one node to another,obviously it's too long,but i can't solve it.
I hope I 1can describe the phenomenas and i need your help,thank you!
You could use NIC Teaming on the 2 common NICs. The two teamed NICs combine to present a third "NIC" to the o/s with a common IP Address. SQL Server sees this common IP and doesn't complain when either of the physical NICs or switches fails. As your NI
C vendor if they support teaming (you'll need some Teaming software).
|||If I set two networks,one is 172.20.1.*and the other is 172.20.2.*,then which network should I config for the third "NIC" for all clients(they all have two NICs) to link?
|||When 2 NICs are teamed, only one is in use at any one time. You don't set the IP Address of each NIC you set the single IP address of the resulting teamed "NIC". So, you could have say NIC1 and NIC2 as your physical NICs. Then team them and call the re
sult "Public Network Connection" (or something more useful) which would have the IP address "172...". When you set up clustering, the public network will be "Public Network Connection" rather than NIC1 or NIC2. Make sure you set "Public Network Connect
ion" as the highest priority in the network advanced=>advanced settings list.

Friday, February 24, 2012

DTS with MSSQL2k failover

Hi,
Is DTS and bcp fully supported for use with MSSQL2k
active/active failover cluster?
--
Many thanks,
OskarI beleive the answer is yes, and I personally have not encountered any
problems... However your hardware must come from the Clustered HCL for ANY
clustering to be supported.
--
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
"Oskar" <anonymous@.discussions.microsoft.com> wrote in message
news:5b0401c48a89$6b26bcf0$a301280a@.phx.gbl...
> Hi,
> Is DTS and bcp fully supported for use with MSSQL2k
> active/active failover cluster?
>
> --
> Many thanks,
> Oskar
>

Sunday, February 19, 2012

DTS with MSSQL2k failover

Hi,
Is DTS and bcp fully supported for use with MSSQL2k
active/active failover cluster?
--
Many thanks,
OskarI beleive the answer is yes, and I personally have not encountered any
problems... However your hardware must come from the Clustered HCL for ANY
clustering to be supported.
--
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
"Oskar" <anonymous@.discussions.microsoft.com> wrote in message
news:5b0401c48a89$6b26bcf0$a301280a@.phx.gbl...
> Hi,
> Is DTS and bcp fully supported for use with MSSQL2k
> active/active failover cluster?
>
> --
> Many thanks,
> Oskar
>