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]
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]