.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Complicated Replication Architecture - Help Needed Please

Posted By:      Posted Date: April 14, 2011    Points: 0   Category :

We have 2 classified networks.  They will only connect with a VPN over fiber. 

The two customers will not agree to directly connect their SQL Server databases to one another without having another server hop between them...on EACH side.

What I'm looking at is this:









|||||||||||| NETWORK A


|||||||||||| NETWORK B











So as you see each SQL Server will never directly communicate with one another.   But they have a table that needs to be transactional replication in both directions.  If an app user gets added or his row updated/deleted in one database it needs to reflect in the other and vice versa.


Can I get some guidance here please?  Like I said the transactions need to replicate fairly quickly (within 5 minutes at the outside, but quicker is better).


View Complete Post

More Related Resource Links

SQL 2008 Replication help needed

Hi Guys

 I have a requirement here to replicate one of the database to SQL Server 2008 to offload the reporting users.

We have  W2k3 server (publisher) with 2 processors( 4 core each ), RAM -8 GB, D Drive - 836 GB (Local). 

SQL Server 2008 (publisher) : only 1 database--- Size-100GB, Memory - 1GB to 6 GB(Max) and mdf, ldf ,tempdb are on the same drive.

we want to do transaction replication (Push) on this database. I want to know how should we approach this if we want to use the same Server as Distributor also.

I mean for best result do we need to separate the Ldf and mdf. Is it possible to add more drive  because  existing drives are local to server.

As i Said it's most busiest database. Will making it distributor affect the performance of the App ? How replication going to affect the performance of the database ?

Need replication architecture assistance (near-real time merge repl across 2 separate companies and


I've read several different replication scenarios and technologies native to SQL Server (we are talking about SQL Server 2005) but have some questions.

I have a project to integrate/replicate two network-separated SQL Server 2005 databases.  Each database resides in a physically separate location at different companies.  They will not have a shared network environment and will not allow direct connection between the two databases.

We need to keep each database in sync as far as customer records.  Near real time is preferable.  There is not master.  One could add/delete/modify a customer record in one database and it needs to reflect in the other database. 


The closest we could get for connectivity architecture looks like this:

1.  Each database is on the separate internal networks for each company.

2.  Each organization HAS agreed to setup a DMZ on their sides specifically for this exchange.  Each respective DMZ will be able to communicate with their own internal SQL Server and have a fiber connect directly connecting each organization's dmz.

SO.... is there a good way to replicate from InternalSQL_1 - DMZ1 - DMZ2 - InternalSQL_2 near real time?

What would your recommendation be?  Pretty sure I'd setup both internal InternalSQL as Pub/Sub/Dist but I'm solici

Architecture Tools in VSTS 2010

Designing new functionality on existing applications can be daunting. There are always differences between the original design and the current implementation.

The new Architecture tools within Visual Studio Team System 2010 help you understand the application you have, design new functionality you need, and validate that your design and your implementation do not deviate.

SharePoint Tutorial - SharePoint Logical Architecture

The SharePoint logical architecure consists of nested and isolated levels. These levels provide benefits for security, navigation, search, branding and ect. depending on the level

SharePoint Farm
The base level for any SharePoint implementation is the SharePoint farm. Physically a farm can consist of one server or many servers. An organization may implement one or more farms. This usually depends on security and performance needs.

SharePoint Tutorial -SharePoint Physical Architecture

The SharePoint physical architecture consists of services running on one or more servers.

There are three types of services that together run the SharePoint farm: web, application and database services. Web services through Internet Information Server is what processes the ASP.Net and sends back the html to a user's browser. Application services is where the "brains" of SharePoint are located. All of the SharePoint specific logic and services are processed there. Database services are run by SQL Server and it's where all the data/content for SharePoint is stored.

MVC Architecture

The main aim of the MVC architecture is to separate the business logic and application data from the presentation data to the user.

Here are the reasons why we should use the MVC design pattern.

They are resuable : When the problems recurs, there is no need to invent a new solution, we just have to follow the pattern and adapt it as necessary.
They are expressive: By using the MVC design pattern our application becomes more expressive.

MVC architecture in ASP.Net using C# and Microsoft Data Access Application block

The Model-View-Controller (MVC) pattern separates the modeling of the domain, the presentation, and the actions based on user input into three separate classes [Burbeck92]:

Model. The model manages the behavior and data of the application domain, responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller).

View. The view manages the display of information.

Controller. The controller interprets the mouse and keyboard inputs from the user, informing the model and/or the view to change as appropriate.

Project Example: ASP.NET MVC + SubSonic Architecture

use of SubSonic to provide the DAL in association with some ASP.NET MVC sites and was waylaid in my original intent to throw up a post summarizing the architecture we're using for the effort. Well I've finally gotten around to it. Recall that in his fake it till you need it post, Dave provided a window on our architecture that I'll build upon here

Three Tier Architecture with ASP.NET

ASP.NET supports layered architecture, and this article will illustrate how it can work with the ASP.NET presentation controls. This article focuses mainly on the GridView control, mostly because it is prevalently used in .NET development. However, the concepts work for other controls as well.

ASP.NET 2.0 (III) Architecture and Tools

In this third article we'll take a look at the changes to the architecture of ASP.NET v2.0. In particular we'll look at the changes to the compilation and deployment model.

High-Performance .NET Application Development & Architecture

It has always been a goal of project architects to plan an effective strategy from the ground up in regards to an new application. All relevant factors are taken into consideration with respect to the application, from its design and layout to a functional website infrastructure. Pre-.NET strategies and design guidelines still effective now were developed with Microsoft's DNA (Distributed interNet Application) platform. This model successfully served the purpose of architecting N(any number of)-Tier (levels) applications. In its basic sense, as in most robust, distributed applications, you'll architect 3 main layers or Tiers: presentation, business rules and data access.

Application architecture in asp .net

Application Architecture is the most important process of developing a good application. Some people tends to jump into coding without any architecture laid. Later we see those people changing the architecture and finally the application had to be developed from the scratch with the correct architecture.

In this article I will describe some details about how you can improve the architecture of you application. This article is targeted to the beginner's audience.

A Low Level Look at ASP.NET Architecture

ASP.NET is a powerful platform for building Web applications, that provides a tremendous amount of flexibility and power for building just about any kind of Web application. Most people are familiar only with the high level frameworks like WebForms and WebServices which sit at the very top level of the ASP.NET hierarchy. In this article I'll describe the lower level aspects of ASP.NET and explain how requests move from Web Server to the ASP.NET runtime and then through the ASP.NET HTTP pipeline to process requests.

Realizing a Service-Oriented Architecture with .NET

This article is meant to be a practical discussion guide to building a .NET application in a service-oriented architecture. We will consider real-world goals, real-world obstacles, and experience-based solutions. I quickly concede the approaches discussed here are not exhaustive or infallible. This paper is focused on application development, not application integration. We will specifically consider architectural issues and component design issues.

The Potential of Web Services

3-tier architecture in C# sample

This article discusses and implements 3-tier architecture using C# and a dummy customer using MS Access database. In this article I am trying to implement a small reusable component that maintains customers in 3-tier architecture. It shows how to add, update and find customer details.

ASP.NET Architecture - ASP.NET Worker Process - HTTP Pipleline - Http Modules and Handlers

"ASP.NET is a powerful platform for building Web applications, that provides a tremendous amount of flexibility and power for building just about any kind of Web application. Most people are familiar only with the high level frameworks like WebForms and WebServices which sit at the very top level of the ASP.NET hierarchy. In this article I'll describe the lower level aspects of ASP.NET and explain how requests move from Web Server to the ASP.NET runtime and then through the ASP.NET Http Pipeline to process requests.

Default ASP.NET Architecture

In providing an architectural approach, some assumptions are made concerning the project goals. These assumptions should be used as a litmus test to determine if the described architecture may be an appropriate fit for your ASP.NET application.
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend