Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't want to be unhelpful and you haven't given any background about your business needs, but you have to decide if your priority is really "fast and secure" or if it's actually "cheap". Replicating changes between multiple databases in a reliable, consistent way is not easy (as you know) and it's highly unlikely that you will be able to develop a solution yourself that has the features, stability and performance of SQL Server replication.</p> <p>SQL Express can be a replication subscriber, by the way, so it's not clear why it doesn't meet your needs. But if it doesn't, you should estimate the cost to your business (or customer) of dealing with issues caused by an unreliable solution: your time, business downtime, finding and correcting incorrect data, customer complaints, lost business etc. Then compare that to the cost of 25 SQL Server licenses (you should certainly be able to get a good discount when you order that volume), additional hardware (if any) and the costs of training, consulting and/or learning how to use replication. Then extrapolate those costs over 5 years or so. You may find that it's cheaper just to buy the solution you need. And of course buying the full SQL Server edition means you get a lot of other new features that might be useful to you.</p> <p>If you (or your boss) is really determined to get something for nothing, you might want to investigate PostgreSQL or MySQL. They both have free replication solutions that seem to be widely enough used to be reliable for many companies. Of course, you then need to calculate the costs of switching to a new database platform.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThe problem is they dont want to pay 7000 USD for the sql license so we are looking for a cheaper solution. Secondly we want to sell the solution to smaller clients who have 1 central server and maybe 2 clients , so for them the high cost of SQL SERVER is a problem. If SQL Express can somehow act like a publisher then that would solve the issue for us
      singulars
    2. COAs I said, you can't look at a single price in isolation. 7000 dollars is nothing compared to the costs that I mentioned and as someone else said, it's a small amount of development time. Calculate how much of your time 7000 dollars buys, then ask yourself (and your boss!) if you can re-create replication and all the other SQL Server features that you might use (SSIS? Service Broker?) in that time. Again, I don't want to sound unsympathetic, but your boss needs to understand a) the relationship between time and money and b) the implications of using commercial software.
      singulars
    3. COYou also can't take the single price in isolation. $7,000 is nothing compared to the costs of provisioning a new server, and moving MSDTC settings, linked server settings, synonym settings, logins, and of course the databases, to the new server. Then there's the hour or 3 of downtime for the business. And then you discover that replication breaks the system when it adds triggers to your database that lead to a complicated chain of trigger recursion. The point being that replication has issues, and you can spend thousands of dollars trying to understand the system that isn't well understood.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload