Re: Developer design Best Practices

From: Gkurtas (Gkurtas_at_discussions.microsoft.com)
Date: 09/10/04


Date: Fri, 10 Sep 2004 06:51:14 -0700

Answers and more questions:

Peter: I am consolidating a list of 23 servers that host individual or
multiple smaller databases that were created adhoc on those servers for the
sake of an application that was hosted on the box. Multiple people installed
SQL on these machines and than installed their application and pointed it
locally. All of these will now be collapsed (if feasible) onto the new design
of development and production servers, which are beefier and faster and
hopefully more secure.

Amanda defined the issue I was asking about in better detail.
The developers have had free reign over SQL for a long time including
production machines. Many of the objects in these databases are owned by not
only long gone developers but sometimes third party vendor accounts who also
do not provide the passwords for these accounts.

I am trying to find out the best method for allowing developers to develop
freely on the development machines while limiting or denying access to
production. This is probably not so easily answered in a newsgroup format but
some pointers to a whitepaper or other resource for this information would be
most helpful. All of the posts so far are accurate and I appreciate the the
input but I need more detail on how exactly to configure this environment. I
am not looking for hardware - cluster - platform configuration info but more
on the permissions and roles and access level stuff.

My plan is to have 4 machines in use - two for development and two for
production with a fifth machine in use on our DMZ for that rare external
database.



Relevant Pages

  • Re: 64 Bit Linux on Pentium III Xeon?
    ... | We have a set of shiny new top end servers for our production ... | we had to scrape the bottom of the barrell for test servers. ... You should have one or more additional shiny new top end servers for your ... production environment to serve two functions: as fallback machines in case ...
    (comp.os.linux.development.system)
  • Re: DR setup questions
    ... which ESX doesn't address.Neverfailcan do apparently do either p2v or p2p replication but can't work ... with clustering and we cluster our production SQL servers. ... located and will house multiple small (6-12 machines), ...
    (microsoft.public.windows.server.general)
  • RE: Moving SQL Server 2000 to a new machine
    ... Currently I do have a test domain which is isolated from our production ... The 2003 servers running SQL Server 2000 will be name the same as ... databases and selected user databases on the production servers are being ...
    (microsoft.public.sqlserver.server)
  • Re: Old Possums book of practical hosts.
    ... We have some servers with carefully constructed names so ... production services and the hardware has been moved so it is ... fail-over cluster should be called Tom and Jerry or Bill and Ben. ... Since fail-over machines are traditionally fall-over machines, ...
    (alt.sysadmin.recovery)
  • Re: Old Possums book of practical hosts.
    ... We have some servers with carefully constructed names so ... production services and the hardware has been moved so it is ... fail-over cluster should be called Tom and Jerry or Bill and Ben. ... Since fail-over machines are traditionally fall-over machines, ...
    (alt.sysadmin.recovery)

Loading