Re: Change Management

["McCoy, Ken D (INPO)" <McCoyKD@INPO.ORG>]

Try SourceSafe (MicroSoft product) . We use it here for VB apps
and for SqlServer procs.


> -----Original Message-----
> From: Allen, David [SMTP:AllenD@MAIL.CI.TLH.FL.US]
> Sent: Friday, September 04, 1998 12:25 PM
> To:   Multiple recipients of list SQR-USERS
> Subject:      Change Management
>
> Hello,
>         I am looking for a good method to handle "change management"
> and SQR
> security.  I need something that will let me
> know where an SQR is - on a programmer's desk or in production, i.e.,
> If I
> am on a team of 5 people modifying and creating SQR's
> how can I be sure who has an SQR (modifying or creating) when a
> functional
> user requests changes.  How should formal requests
> be handled, should it be by funcitonal area, assigning "PAYROLL SQR's"
> to a
> specific payroll SQR programmer ?
>         Should the SQR developer be allowed to implement their changes
> or go
> through a "secure" method of change implementation?
>          I am open for suggestions.  Any help will be appreciated.
> Thank
> you.