Re: Networking

http://blogs.techrepublic.com.com/networking/?p=460

The DNS CNAME record is probably the greatest tool as an administrator
that we can use to facilitate moves and changes in the backend when
using Active-Directory integraded DNS. Using the CNAME record for
database connectivity is a new strategy I have started to use to
facilitate server moves simply with the DNS change. Take the following
example:

FQDN Server Name: DATASERVER1.AMCS.TLD
Associated CNAME: CORPDB.AMCS.TLD

Now, DATASERVER1 is a Windows cluster for Microsoft SQL Server with a
disaster recovery site with the databases mirrored. If that is needed
to be used, the CORPDB record points to DATASERVER2 to redirect client
traffic to that database server. But, the management does not stop
there. This accomodates for a single change in DNS to point the server
in question to the remote data center (RDC) database engine as a
different FQDN name. But, I’ve been taking this a step further with
CNAME use. For each database, I have been creating a CNAME record that
points to the relevant server or DNS CNAME that the database is
currently housed upon. Further, I make these CNAME records self-
documenting in their nomenclature so that looking at the DNS records
tells you everything needed. Here is an example:

Associated CNAME: DB-DATABASENAME-STATE.AMCS.TLD
FQDN server name of target host: CORPDB.AMCS.TLD

In this example, DB indicates a database, DATABASENAME would be the
application name and STATE would refer to the implemenation level
(Live, Test, etc.). All of these relevant records starting with DB-
helps in alphabetical sorting in the DNS console. By using CNAME
records in this fashion, all client connectivity is pointed to the DNS
record instead of the server name. This permits a move of the server
and a move of the individual database to be transparent of any
configuration outside of DNS record management. By pointing all client
connectivity to the CNAME record, configuration changes are not
required (other than clearing a DNS cache) on the clients accessing
the databases.



On May 15, 9:51 pm, "Arvin Meyer [MVP]" <a...@xxxxx> wrote:
Son, go find somewhere else to play. You have no idea what you're talking
about. I can't image any responsible DBA doing that. DNS records are used to
publish domain and mail server IPs, and that's it.

The number of inaccurate answer you post is nothing short of phenomenal. It
sounds like you've read a book or 2 and remember some key words but nothing
else. We all know better. Do us all a favor and take your nonsense somewhere
where no one has any idea what you are talking about and thinks you might be
intelligent. How about alt.abuse.offender? Perhaps you can learn some
manners and good sense there as well.
--
Arvin Meyer, MCP, MVPhttp://www.datastrat.comhttp://www.mvps.org/accesshttp://www.accessmvp.com

<aaron.ke...@xxxxxxxxx> wrote in message

news:8230d2d2-930d-4714-be8c-4ef39710b7f8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
and for the record, I usually implement DNS C Names in order to use
pointers for all my apps.
Then instead of changing the connection string (IN ONE PLACE) I just
change the DNS pointer.

now _THAT_ is an enterprise level idea!

-Aaron

On May 15, 1:07 am, "Arvin Meyer [MVP]" <a...@xxxxx> wrote:



Linking an ADP is no different than linking an MDB to SQL-Server or any
other RDBM for front-end changes. It isn't easier at all since if one
moves
the server, because one needs to build a new DSN or rewrite the connection
strings, and one only needs to relink to the native JET DBMS.
--
Arvin Meyer, MCP,
MVPhttp://www.datastrat.comhttp://www.mvps.org/accesshttp://www.accessmv....

<aaron.ke...@xxxxxxxxx> wrote in message

news:4cb4f3b0-5ad5-4f67-bbaa-a1860bbc2ca6@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
yes, if you change a table, then you've got to relink it in 5
different places.

that is why it is considerably easier to move to SQL Server / ADP.

-Aaron

On May 8, 3:55 am, Roger Bell <RogerB...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

I have designed a data base which I wish to install on 5 remote
computers.

My idea is to link the Backend (Tables). My question is if i change any
reports/mailing labels etc on the server data Base, do I then have to
change
the design on each of the remotes.

Is there any difference between splitting and linking, or is there a way
to
change any report designs that will automatically update on the remotes.

Many thanks for any help- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -

.

Relevant Pages

  • Re: Networking
    ... any database with under a hundred users. ... change the server names on 99 different ... ALL servers within that domain share that CName. ... The DNS CNAME record is probably the greatest tool as an administrator ...
    (microsoft.public.access.gettingstarted)
  • Re: Networking
    ... DNS records are used to ... publish domain and mail server IPs, ... The DNS CNAME record is probably the greatest tool as an ... traffic to that database server. ...
    (microsoft.public.access.gettingstarted)
  • Re: Help with anonymous access
    ... If you change it in the database, ... That sharepoint central administrator url is populated by whatever you have ... Go to iis administrator on the server. ... You want the IP address of this server, port 80, and the DNS* you will be ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Rebooting server causes PC to lose connection
    ... I would think the same like you, but maybe the connection to the database does not completely needs DNS during work. ... until the server comes back up. ... "Meinolf Weber" wrote: ...
    (microsoft.public.windows.server.general)
  • Re: Major AD / DNS Failure - need to find solution
    ... Try renaming the existing WINS database, then restart the server (or just ... Here is the DNS Log. ...
    (microsoft.public.windows.server.sbs)