Re: Replication with SQL 2005 Standard

I take it the guys telling you this are consultants or a vendor who are going to get a piece of the added revunue required to purchase licenses you do not need.

Where they may be confused is think you need to use peer-to-peer replication which requires the enterprise edition. You can use bi-directional transactional on standard and workgroup editions. You might also want to use log shipping or database mirroring instead of replication. These will not require licensing the standby server for up to 30 days after the role change. Note this only applies to SQL Server licensing, you will require OS licensing on the standby server wether it is in a standby role or primary role.

One thing you should keep in mind is you will need appropriate licenses to match the # of users. When I see the word DMZ I think web which may mean a per processor license.

Another thing to consider before purchasing another machine and licenses is are your performance problems due to poor code, indexing, etc? I would spend some money trying to resolve these issues before spending a lot more money on more hardware and licensing and adding another layer of complexity and point of failure to your topology.

There could be very valid other reasons for running Enterprise Edition however. For example online indexing, etc.


"Allyn" <Allyn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:570102D1-7787-4344-9141-0770787A22E0@xxxxxxxxxxxxxxxx
I'm trying to validate what I've been told, and after going through many
posts, I think things are close to be squared out but I need to make sure.

We have a web server in the DMZ running custom .NET applications and a SQL
2005 standard on the internal network. We need something more than backups as
we can't be off line for hours while restoring the server. Additionally, the
SQL server is getting pretty heavily loaded, so what we'd like to do is to
purchase another SQL server, make connections to both, and keep the databases
synchronized. The guys driving this project insist SQL Enterprise is required
to do this. I'd appreciate feedback on this. Also, would bidirectional,
transactional replication fit the bill?

Thank you.

.

Relevant Pages

  • Re: Upgrading from Windows 2000 NAS Server to Windows Storage Server 2003
    ... Windows Storage Server 2003 R2, was unable to obtain one, and unable ... Chances that our company will EVER purchase another piece of Northern ... I was having Deja Vu as the Microsoft Tech bristled at the suggestion ... It seems that your question is about licensing or product order issue. ...
    (microsoft.public.windows.server.migration)
  • Re: Writing Remote Desktop Server or Remote Terminal Server
    ... You'd need to purchase one copy of the development environment for EACH ... the idea of free licensing may not apply. ... > I need to write an server application which will work Windows Remote ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Additional instances and licensing...
    ... Is that a change from the SQL 2000 licensing model? ... Q. How does licensing work with the multi-instance feature in SQL Server ... You can run multiple instances of SQL Server 2005 on a single computer. ...
    (microsoft.public.sqlserver.setup)
  • Re: "Cult of the Wintel PC" raises head at AWCs switch to Macs
    ... all the clients are Macs running the native VIPS app. ... what you're runnning on the SERVER that determines whether you have to ... Then they have no licensing fees to pay over what ever life ... I went to M$ page on SQL server along with reading the article. ...
    (comp.sys.mac.advocacy)
  • Re: How many Remote Desktop sessions allowed ?
    ... SBS 2000 = unlimited TS sessions if the server is set as a TS licensing ... server and the appropriate number of TS CALs are purchased and installed. ... Was not and is not a good idea to run user sessions on your DC. ... that SBS2003 with Exchange will only allow 2 and that I can't purchase ...
    (microsoft.public.windows.server.sbs)
Loading