Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Failover configuration landscape

Status
Not open for further replies.

onpnt

Programmer
Dec 11, 2001
7,778
US
I'm in the process of writing up a landscape for a new SQL environment. I just wanted to throw a few things at all of you to make sure I'm on a level playing field here.

I'm fighting with the operations manager on SQL versions which is starting to get rediculous also. My argument is Standard has it's place here and Enterprise editions is pretty much a waist of money for this environments purposes.

Brief setup

First location.
Server 1: Main production server. Unlimited space on the san (unlimited is in reality limited of course:)) SQL2005 Standard edition. 20-25 databases. One with replication to off-site instance.

Server 2: Failover server. Unlimited space on the san (unlimited is in reality limited of course:)) SQL2005 Standard edition.

Server 1 will be mirrored to Server 2 for failover with a SQLExpress witness in the middle for automation.

Server 3: Off-site location. Replication will be setup for this server between Server 1 to supply an application at the off-site location.

Server 4: Development box. Mirrored to Server 1 in hardware.

They want X64 systems for the memory abilities. Personally I would like to see 32 so there are no conflicts but I'm not arguing this stance with them.

I've checked all my notes and Standard allows 2 nodes on failover so I am covered. The only limitation I see in the version with what I am doing is the CPU #'s supported. Of course Standard ends at 4 with mutli-core support.

Hardware isn't really an issue. We have that covered and the budget is there for very good machines.

This setup is simple to be honest. I don't see any issues with Standard edition for it. Does anyone else? I have not looked at issues with Replication and Mirroring on the same database. I'm going to start looking into this now to satisfy questions that have come up.

Your thoughts?

Thanks



[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]
 
for server 4 purchase the developer license. it's only $50.00 so you can save some money there. It supports the same functionality as Enterprise.

- Paul
10qkyfp.gif

- If at first you don't succeed, find out if the loser gets anything.
 
I don't see where you are clustering. Based on your description you are using mirroring between Server 1 and Server 2.

The only thing that Enterprise will get you is More CPUs, Clusters that have 3 or more nodes, and online indexing.

If this was my setup I'd use Server 1 and Server 2 for clustering. Server 3 for DR with mirroring. Server 4 for Dev, and a Server 5 for QA.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top