Hi all,

I would like to set up permisions in such a way that the
user can only read the database and cannot update it while
running DTS.i.e the user must be able to export data but
not import into production database.What settings would
fulfill this scenario,i have been trying with all
alterations but not able to restrict DTS import.

any help would be appreciated.

thanks
Sudha

In message <c22e01c43846$a7a8f2f0$a501280a (AT) phx (DOT) gbl>, sudha
<anonymous (AT) discussions (DOT) microsoft.com> writes
DTS is really a client side tool, so to run a package in your own
context you need to be able to do whatever the package does. To some
degree this depends on the type of security used in the connections of
the package. if you build a package and use the sa password and give it
to a user, then apart from being silly, it obviously gives them the
ability to connect as sa so it is not going to be read-only.

If using integrated security for the connections then that should be
easy eneough to grasp as me executing a package on my machine through
VB/C# etc or Enterprise Manager means connections to the DB are made as
domain\darren.

Do not confuse the connections inside a package to the connection
information used to load a package from SQL Server storage. Probably
only relevant if you are loading and executing the package through code
yourself.

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Hi Darren

Sorry i confused you with the word user, i should have used DBA,we are 3 of us who can access production database and we login with different id's ,i want to restrict our permissions on production database.we must be able to read the data from production but not delete or write to production through dts

how can i impliment this

Thank
sudha

In message <A4FE1947-C0FD-40AC-97E7-041C8ECA1D6D (AT) microsoft (DOT) com>, sudha
<anonymous (AT) discussions (DOT) microsoft.com> writes

Same principle applies. Don't use logins that have any more permissions
that your require, in this case read-only.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org