Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Prevent accessing Data Directly using Enterprise M

Author  Topic 

Aiby
Yak Posting Veteran

71 Posts

Posted - 2010-06-27 : 07:30:11
Can we prevent Opening a specific Database Using Enterprise Manager or SQL Query Analyser, Rather than Front End Application.
Or
Can we get that information a Particular Database data is viewed or edited directly accessing the Tables using Enterprise Manager or Query Analyser!!

SD_Monkey
Starting Member

38 Posts

Posted - 2010-06-27 : 12:05:01
Yes we can view it on the management on the Enterprise Manager under the management node....

A maze make you much more better
Go to Top of Page

tosscrosby
Aged Yak Warrior

676 Posts

Posted - 2010-06-28 : 16:30:48
quote:
Originally posted by Aiby

Can we prevent Opening a specific Database Using Enterprise Manager or SQL Query Analyser, Rather than Front End Application.



Setting security, sure (checkout BOL). How are the users logging in? I sure hope you don't say "sa"....

quote:
Originally posted by Aiby

Can we get that information a Particular Database data is viewed or edited directly accessing the Tables using Enterprise Manager or Query Analyser!!


I don't know about viewed but auditing will allow you to see what's been edited if you identify the tables you want audited and set up auditing appropriately. Profiler (SQL2000) may also lend itself to this but it is more defficult to pull the prcise information you may be seeking.

Terry

-- A word to the wise ain't necessary - it's the stupid ones that need the advice. -- Bill Cosby
Go to Top of Page

Aiby
Yak Posting Veteran

71 Posts

Posted - 2010-07-03 : 13:56:11
Thank you Terry,

Yes,you are right, they connect with 'sa' user!!! - Thats why i am Worried.
I think as you said Auditing can be try out.

quote:
Originally posted by tosscrosby

quote:
Originally posted by Aiby

Can we prevent Opening a specific Database Using Enterprise Manager or SQL Query Analyser, Rather than Front End Application.



Setting security, sure (checkout BOL). How are the users logging in? I sure hope you don't say "sa"....

quote:
Originally posted by Aiby

Can we get that information a Particular Database data is viewed or edited directly accessing the Tables using Enterprise Manager or Query Analyser!!


I don't know about viewed but auditing will allow you to see what's been edited if you identify the tables you want audited and set up auditing appropriately. Profiler (SQL2000) may also lend itself to this but it is more defficult to pull the prcise information you may be seeking.

Terry

-- A word to the wise ain't necessary - it's the stupid ones that need the advice. -- Bill Cosby




Analyst Programmer
DiB P.Ltd.
Kerala, India
Email: Aiby@hotmail.com
Go to Top of Page

tosscrosby
Aged Yak Warrior

676 Posts

Posted - 2010-07-06 : 08:19:34
Create a role that has the necessary rights for the user group. Grant the role to the users (creating the users if necessary) and change the sa password - sometimes a little more complex to do, depending on if it's embedded in an application (don't do it!). It will help you to sleep better at night. As far as auditing, you have to identify the tables you'd like to audit and set auditing up. It doesn't "just occur".

Terry

-- A word to the wise ain't necessary - it's the stupid ones that need the advice. -- Bill Cosby
Go to Top of Page
   

- Advertisement -