> 1. Make sure the MSDE is installed correctly;
> 2. Make sure the MSDE runs as expected. You log on user laptop as an Admin
> user (in order to check the "Services" applet and make changes if
> necessary), go to "Services" applet. Make sure the "MSSQLServer" is set to
> "Automatic starts". And its "Log on" account should be set to "Local
> System" (unless you have some specific concerns that make you choose other
> account, I do not see why, in your case).
>
> After this two steps, the MSDE should be running whenever you laptop turns
> on, and ready to be accessed, no matter which user account you log on to
> the laptop. That is, MSDE, as a Windows service, should run whether there
> is user logged onto this computer or not, or logged on with different user
> account. This has nothing to do with SQL Server's security (Authentication
> mode, Windows integrated, or SQL Server security).
>
> Then you start to worry about MSDE's security:
>
> By default, only Windows authentication is used (that is, you do not need
> username/password pair once you log onto your laptop). When you log on as
> an Admin user, you automatically gain the access to MSDE. However, when
> you log on as non-admin user, MSDE knows who you are (because of Windows
> authentication of MSDE in use), and grants/denies your access accordingly.
> You need to create a SQL Server login in MSDE that maps a user
> account/group of your laptop, and make this login a user to given
> database. With that given database, you can make a user play different
> role (public user, db owner...), or assign different level of access to
> server objects (tables, views, SPs...)
>
> General approach is to log onto your laptop as Admin, install/set up MSDE
> properly, assign specific SQL Server login as user of certain databases,
> assign appropriate permissions to the databases, and log off as Admin, log
> on again as a standard user. Now, you can use the MSDE fairly safely.
>
>
> "Peter Hartlén" <peter@data.se> wrote in message
> news:uWyej71THHA.5068@TK2MSFTNGP03.phx.gbl...
>> Hi!
>>
>> I've installed MSDE 2000 on a laptop using a admin account. I then logon
>> using a user account. Now MSDE isn't started, and as I don't have admin
>> privileges I cannot access services etc.
>>
>> If I am logged on as both user and admin (switching between the accounts)
>> the MSDE icon in the activityfield has a green arrow when I log on as
>> admin but it's an empty white circle when I am logged on as user.
>>
>> Shouldn't you be able to install MSDE as admin and then use it as user?
>>
>> / Peter
>>
>
>

> General approach is to log onto your laptop as Admin, install/set up MSDE
> properly, assign specific SQL Server login as user of certain databases,
> assign appropriate permissions to the databases, and log off as Admin, log
> on again as a standard user. Now, you can use the MSDE fairly safely.

"Peter Hartlén" <peter@data.se> wrote in message
news:uWyej71THHA.5068@TK2MSFTNGP03.phx.gbl...
> Hi!
>
> I've installed MSDE 2000 on a laptop using a admin account. I then logon
> using a user account. Now MSDE isn't started, and as I don't have admin
> privileges I cannot access services etc.
>
> If I am logged on as both user and admin (switching between the accounts)
> the MSDE icon in the activityfield has a green arrow when I log on as
> admin but it's an empty white circle when I am logged on as user.
>
> Shouldn't you be able to install MSDE as admin and then use it as user?
>
> / Peter
>

"Peter Hartlén" <peter@data.se> wrote in message
news:Olg73N4THHA.4928@TK2MSFTNGP03.phx.gbl...
>> General approach is to log onto your laptop as Admin, install/set up MSDE
>> properly, assign specific SQL Server login as user of certain databases,
>> assign appropriate permissions to the databases, and log off as Admin,
>> log on again as a standard user. Now, you can use the MSDE fairly safely.
>
> After reading your post again I realized one thing wasn't really clear to
> me.
>
> Can I use "Integrated security for Windows NT" for this non-admin user, or

> do I need to set the security mode of MSDE to accept both "Integrated sec"
> and "SQL Server login"?

>
> Thanks,
>
> Peter
>