Hi,
WEhen can I use this procedure? When its recommended and if its safe to use
it while online users are using the database.
Regards,> Hi !
> I want to use differnt logins for accessing database .
> User : for select queries
> Programmer : having full access to only to specific tables / and
> create/drop/alter rights for store procedures /functions/triggers
> Admin : having full access for all database objects .
> My main objective is to disable SA user for all the users of database ,and
> keep a audit of these users.
>
> I have already created these users and roles , Can u pls tell me what can
be
> area of attention while doing this ? what would be the impact while doing
> any activities , specially migration from one server to another , or
> transfering the data using DTS.
> Secondly , I want to implement transactional replication on production
> database , will it have any impact of logins and users of database ?
>
> Regards,
> Swati
>|||aoxpsql,
This can consume large amounts of server resources, mainly disk IO. I
would prefer to run this at a time when the number of users is at a
minimum, say 3am? Try and run it when no other maintenance or overnight
batch jobs are running.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
aoxpsql wrote:
> Hi,
>
> WEhen can I use this procedure? When its recommended and if its safe to use
> it while online users are using the database.
> Regards,
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment