We have a problem with job ownership and permissions that we are trying to
work out. We are running SQL 2000 sp2 on windows 2000.

My take on job ownership is this, only the owner or a system administrator
can view jobs (DTS packages as well.) What do we do when trying to let a
whole development team view and use jobs (and DTS ) created by a user
without setting everyone up as an sql System Admin and compromising
security? We have tried to assign NT groups to the ownership of the job but
this looks like it is not an option in SQL. Any ideas?

Thanks,
Russ

Report this post to a moderator

This might sound cheesy, but maybe you could create a login/user called
DevJob (or something), and that special account could be used to create and
maintain all new jobs during development. Your goal is to have all
developers create/maintain a pool of jobs during development without
allowing developers SA rights?

James

Report this post to a moderator

Hey Russ,

The company I work for is set up the same as you. One development and one
production server set up with Windows 2000 Server & SQL Server 2000. We
have several different groups and accounts set up to access the server.

One of them is that all the developers in my department, only three, are a
part of the PCDevelopers group. This is a group our IS Dept. set up on the
network and was added to the administrators group on the development server.
We use this when we are working through the Enterprise Manager mostly.

We also have 3 specific accounts set up; dbadmin, db01admin, and db02admin
(01 = production, 02 = development). The dbadmin is used only by our DBA,
the other two have been set up slightly different from each other because of
the server they have access to.

The db01admin, belongs to all the Server Roles execpt the System
Administrators. And, since the development server is all ours, db02admin is
a part of the administration group. We use Terminal Service, by signing in
with one of those accounts, and making the modifications we need either
through the Enterprise Manager or SQL Query Analyzer.

I don't know if this helps you or not. But good luck,

Randel




"Russ Neff" <rneff@hometownhealthnet.com> wrote in message
news:O4fmMOFoCHA.1604@TK2MSFTNGP08...
> We have a problem with job ownership and permissions that we are trying to
> work out. We are running SQL 2000 sp2 on windows 2000.
>
> My take on job ownership is this, only the owner or a system administrator
> can view jobs (DTS packages as well.) What do we do when trying to let a
> whole development team view and use jobs (and DTS ) created by a user
> without setting everyone up as an sql System Admin and compromising
> security? We have tried to assign NT groups to the ownership of the job
but
> this looks like it is not an option in SQL. Any ideas?
>
> Thanks,
> Russ
>
>

Report this post to a moderator

Sounds good. I will look at this model and see if it works for us. We
appreciate the help and if ever can be of service to you, just ask.

Thanks,
Russ


"Randel Bjorkquist" <rbjorkquist@coilcraft.com> wrote in message
news:Ob2b46HoCHA.1224@TK2MSFTNGP08...
> Hey Russ,
>
> The company I work for is set up the same as you. One development and one
> production server set up with Windows 2000 Server & SQL Server 2000. We
> have several different groups and accounts set up to access the server.
>
> One of them is that all the developers in my department, only three, are a
> part of the PCDevelopers group. This is a group our IS Dept. set up on
the
> network and was added to the administrators group on the development
server.
> We use this when we are working through the Enterprise Manager mostly.
>
> We also have 3 specific accounts set up; dbadmin, db01admin, and db02admin
> (01 = production, 02 = development). The dbadmin is used only by our DBA,
> the other two have been set up slightly different from each other because
of
> the server they have access to.
>
> The db01admin, belongs to all the Server Roles execpt the System
> Administrators. And, since the development server is all ours, db02admin
is
> a part of the administration group. We use Terminal Service, by signing
in
> with one of those accounts, and making the modifications we need either
> through the Enterprise Manager or SQL Query Analyzer.
>
> I don't know if this helps you or not. But good luck,
>
> Randel
>
>
>
>
> "Russ Neff" <rneff@hometownhealthnet.com> wrote in message
> news:O4fmMOFoCHA.1604@TK2MSFTNGP08...
> > We have a problem with job ownership and permissions that we are trying
to
> > work out. We are running SQL 2000 sp2 on windows 2000.
> >
> > My take on job ownership is this, only the owner or a system
administrator[colo
r=green]
> > can view jobs (DTS packages as well.) What do we do when trying to let a
> > whole development team view and use jobs (and DTS ) created by a user
> > without setting everyone up as an sql System Admin and compromising
> > security? We have tried to assign NT groups to the ownership of the job
> but
> > this looks like it is not an option in SQL. Any ideas?
> >
> > Thanks,
> > Russ
> >
> >
>
>[/color]

Report this post to a moderator