Re: Branch Office Deployment

Hi Darryl,

There is a lot going on in your question and I'll get to those pieces as
best as I can. The question you are really asking goes beyond AD and SQL
making it an application architecture question.

If you are using AD or ADAM for your authentication and authorization
source, you can certainly put a DC at each site and let the application
running locally at each site authenticate locally. You would authenticate
against the domain and allow the DNS to return the local provider. This
would also provide some redundancy against a failed/ busy/ unavailable DC as
it would hop across your T1s. As the application would be authenticating
locally the failure of the T1 becomes moot.

With SQL replication you would be able to decentralize SQL to an extent and
hit the databases locally -- especially if you are primarily relying on read
access. If this is a highly transactional environment where you would need
immediate access to data and transactions would need to be committed across
the enterprise to be complete this may not be the solution for you. I would
certainly talk with the application architects to look at the effects of
distributed transactions and locking before going that route. Some apps do
well in this scenario, however.

UI and access to other resources would have to be balanced and tested to
ensure that they can work in a disassociated fashion. If they have to cross
the wire for everything, the performance will suffer. If they never cross
the wire, you could un into transaction conflicts. This should be carefully
architected and tested.

Finally, for something like this, you may want to consider one of the
standards-based architectures that will help you past a lot of these issues.
I would suggest CSLA, but then I am a bit biased too. It is free, however
and widely used.

Hope this helps.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
http://www.techsterity.com
Chicago, IL

Remember: Marking helpful answers helps everyone find the info they need
quickly.


"Darryl" wrote:

Thanks for the response. Interaction would be the logging on of network users
and accessing the client/server app in addition to the files stored on the
network. I would think local processing at each site would be better as a
whole. As far as bandwidth...I don't know "exactly" but it is an application
that has a small client that installs on the local machine. So I wouldn't
think it is too nasty. We want the app to be available in the event the link
goes away to the main office. Each site would operate independently and
transfer the data when appropriate. That is one of the questions - What would
be the best way to replicate that data back to corporate?

"Al Mulnick" wrote:


Some questions:
What is the interaction of the app and AD? That's not clear from your post.
What are the bandwidth requirements of the app?
If your wan link goes away, what is the value of the app? does it continue
to function without a WAN link to the central and just queue everything up?
Or ?

Al

"Darryl" <Darryl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1C616B42-2A0D-4AFA-B2FE-2F6CA4546513@xxxxxxxxxxxxxxxx
I asked a similar question in the Windows Server 2003 group but realized I
probably should have posted here instead so here goes and I apologize for
double posting.

I have a new custom app we are rolling out very soon and we currently have
a
total of 9 sites - one of which is corporate where the app is being
developed. The app is written in .Net, VB and backended by SQL 2005. We
will
of course also use the reporting services included in SQL 2k5. I think
creating sites and having a server local at all remote offices not only
makes
the app more responsive but also provides a bit of a disaster plan in the
event the T1 goes down. Extend AD to all the sites, create a DC at each
site,
all share one domain and Replicate.

My question is this: Is this the best practice for offering the
application
to all the branch offices? What about replication? SQL won't be a problem
as
far as replication goes? Does replication care whether it's SQL or plain
files or ????

I'm a bit of a newbie when it comes to this so please forgive me.

Thanks in advance for any help. I really need it.

DL



.

Relevant Pages

  • Branch Office Deployment
    ... I asked a similar question in the Windows Server 2003 group but realized I ... total of 9 sites - one of which is corporate where the app is being ... The app is written in .Net, VB and backended by SQL 2005. ... What about replication? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Branch Office Deployment
    ... there may be some value in using the SQL replication engine. ... We want the app to be available in the event the ... If your wan link goes away, what is the value of the app? ... The app is written in .Net, VB and backended by SQL 2005. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cancel SQL CE Replication gracefully?
    ... I have already deployed a Field Service app and a Delivery App ... One uses Merge Replication ... I work closely with the MS SQLMobile and CF ... After two dozen CF apps using SQL CE, I have learned to keep my usage ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Access vs SQL
    ... from Access, tweaked my app a bit, and viola, everything works. ... MSDE 2000 adds a bit of complexity, but I have to say, compared to ... > (above and beyond what they pay for my engineering services). ... > Now, still using C1 components, I know I can upsize to MSDE or SQL ...
    (microsoft.public.dotnet.languages.vb)
  • Re: SQl Data Provider Performance Issues
    ... Can you provide a complete sample app ... selects with a single inner join perforn OK. ... When I run the query from SQL ...
    (microsoft.public.dotnet.languages.csharp)