Re: Security and Tables!
From: Mary Chipman (mchip@nomail.please)
Date: 05/23/02
- Next message: Trayce Jordan: "Re: major security concern - any sql user with minimal permission can see code for all stored procs and triggers"
- Previous message: Trayce Jordan: "Re: dbo.objectname instead of username.objectname"
- In reply to: Ion Hatzithomas: "Re: Security and Tables!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Mary Chipman <mchip@nomail.please> Date: Wed, 22 May 2002 18:29:19 -0400
No, there's nothing you can do to reconfigure Access, if that's what
you mean. Your best best is understanding how SQLS security works. If
you're uninformed on this topic, you can make your entire network, not
just a single database, vulnerable to attack. When you have an
unsecure Access/Jet database, the worst that can happen is that
someone can steal the data in the mdb. With an unsecured SQL Server,
malignant attackers have access to network and file resources beyond
SQLS itself. What it all boils down to is this: if you bury your head
in the sand on this issue and choose to remain ignorant, you're
leaving your *** exposed and relying on a higher power to protect
your enterprise. For additional resources, see
www.microsoft.com/security, and www.sans.org.
-- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446
On Wed, 22 May 2002 14:36:14 -0400, "Ion Hatzithomas"
<ihatzi@gerbertours.com> wrote:
>Ok... I had a look at the security... I am a bit green wwhen it comes to
>this aspect of SqlServer!
>
>I had a look online, but have yet to find the solution...
>Do you know if there is a way to reconfigure our users in order to remove
>the (dbo) from the table names?
>
>Thanks again!
>Ion
>
>
>
>"Mary Chipman" <mchip@nomail.please> wrote in message
>news:0veneuonttoub7ig604boej74is5q2jd36@4ax.com...
>> It has everything to do with security. Access won't display tables or
>> objects that the connected user does not have permissions on. The
>> reason you don't see this when logged on as an administrator is that
>> administrators have permissions to everything. Other users must be
>> explicitly granted permissions. See SQL BooksOnline for more info on
>> permissions.
>>
>> -- Mary
>> Microsoft Access Developer's Guide to SQL Server
>> http://www.amazon.com/exec/obidos/ASIN/0672319446
>>
>> On Wed, 22 May 2002 11:06:38 -0400, "Ion Hatzithomas"
>> <ihatzi@gerbertours.com> wrote:
>>
>> >Ok... I am using SQLServer2000 on WindowsServer2000...
>> >
>> >I have a db that I created and work on from a client machine... I log
>onto
>> >that machine as administrator. But when I log onto a client as someone
>> >other than administrator, all the table names become appended with
>"(dbo)"
>> >
>> >I am using MSAccess2000 for the front end... This seems to mess up the
>front
>> >end since now tables and views aren't always found! I assume this has
>> >something to do with security.
>> >
>> >ie. Employees -> Employees (dbo)
>> >
>> >Is there a way to prevent or fix this?
>> >
>> >Thanks in advance
>> >Ion
>> >
>>
>
- Next message: Trayce Jordan: "Re: major security concern - any sql user with minimal permission can see code for all stored procs and triggers"
- Previous message: Trayce Jordan: "Re: dbo.objectname instead of username.objectname"
- In reply to: Ion Hatzithomas: "Re: Security and Tables!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]