Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Configuration Recomendations

Author  Topic 

JimL
SQL Slinging Yak Ranger

1537 Posts

Posted - 2008-07-17 : 15:50:14

We are considering upgrading from a single server running SQL 2000 to a 2 server SQL 2005 or 2008 system. (Each server would be in a different building connected via fiber optic network)

What would be the best configuration for speed and automatic failover in case of a server crash?

Do we need enterprise version or can we use standard?

Jim
Users <> Logic

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-07-17 : 16:20:24
quote:
Originally posted by JimL


We are considering upgrading from a single server running SQL 2000 to a 2 server SQL 2005 or 2008 system. (Each server would be in a different building connected via fiber optic network)

What would be the best configuration for speed and automatic failover in case of a server crash?
SAN.
Database Mirroring,Clustering or Geographically dispersed Clustering (SQL 2008)

Do we need enterprise version or can we use standard?

Depends on load you have present server. Also consider 64-bit edition.
Jim
Users <> Logic

Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-07-17 : 23:35:10
Speed is based on network bandwitdh. Sql2k5 standard edition comes with 2-node cluster. Keep in mind that win2k8 supports GDC, but it can't failover sql resource automatically in current build.
Go to Top of Page

rlaubert
Yak Posting Veteran

96 Posts

Posted - 2008-07-18 : 13:51:35
Keep in mind that clustering is not load balancing. You will need two copies of the database and a means of keeping them in sync with each other.

Really need a little more information as to what you are trying to accomplish from this set up. If it is failover support than clustering will work. If you are looking to increase the speed of transactions than clustering is not the answer.

Raymond Laubert
MCSE, MCDBA, MCITP:Administration, MCT
Go to Top of Page

JimL
SQL Slinging Yak Ranger

1537 Posts

Posted - 2008-07-18 : 15:56:01
What is the differance between clustering and Mirroring?

Jim
Users <> Logic
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-07-18 : 15:59:43
quote:
Originally posted by JimL

What is the differance between clustering and Mirroring?

Jim
Users <> Logic



Clustering is expensive compared to Mirroring. Mirroring can be used between far locations with automatic failover considering network bandwidth is optimum. But wouldn't recommend it. Mirroring can be done asynchronously too but with no automatic failover.
Go to Top of Page

JimL
SQL Slinging Yak Ranger

1537 Posts

Posted - 2008-07-21 : 10:38:37
quote:
Clustering is expensive compared to Mirroring. Mirroring can be used between far locations with automatic failover considering network bandwidth is optimum. But wouldn't recommend it.


Why not?

Jim
Users <> Logic
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-07-21 : 11:35:24
Performance reasons is a huge issue with synchronous database mirroring. Trust me. We have to use the async option due to how slow sync is on the principal server.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-07-21 : 12:40:03
Synchronous mirroring depends on lot of factor.
1)Your network bandwidth
2)Your edition of SQL server(Bcoz enterprise edition has additional advantage of Redo phase in DB mirroring.
3)The rate of transaction.(If your Transaction rate is very high and if you have bulk insert,massive delete ,huge reindexing operation then performance of DB mirroring will be worst)
Go to Top of Page
   

- Advertisement -