Slightly OT: DBA duty assignments...

From: Norman Dunbar <Norman.Dunbar_at_lfs.co.uk>
Date: Fri, 20 Jun 2003 12:31:50 +0100
Message-ID: <E2F6A70FE45242488C865C3BC1245DA703D0B197@lnewton.leeds.lfs.co.uk>

Ummmm,

I've got me and only me.

I therefore know of any changes I want to make, but if those changes are something that will affect developers, then I obviously have to communicate with said devlopers - or at least, their team leaders.

Cheers,
Norm.

--

---

The Lone DBA.
Norman Dunbar (at home on Linux)
Oracle_at_mssqlBountifulSolutions.co.uk

(Delete a Microsoft database name to reply - clue, mssql !)

---

-----Original Message-----

From: stephen.howard_at_us.pwcglobal.com (Steve Howard) [mailto:stephen.howard_at_us.pwcglobal.com] Posted At: Thursday, June 19, 2003 7:02 PM Posted To: server
Conversation: Slightly OT: DBA duty assignments... Subject: Slightly OT: DBA duty assignments...

Hello All,

This is more of an administration post, but I assume this affects all of us on some level.

For those of you with DBA's in different locations, how do you deal with who makes what changes where? We have about 100 databases that we manage, with two DBA's in one state and one other in another state.  We have boxes in both locations.

Do you assign lead DBA's to each database?

If so, what does that mean (i.e., who can do what?)

Can each DBA make a change in another "leads" database and then inform him/her?

What success/failures are probable in any given scenario?

You get the drift...

Thanks,

Steve Received on Fri Jun 20 2003 - 06:31:50 CDT