Re: MSDE does not work for XP power user


"Peter Hase" <spam_sucks_@xxxxxxx> wrote in message news:1jq8p35pq3p1usq5inbvv8baqoct2em2kk@xxxxxxxxxx
Hi,

thanks for your response.

SQL Server/MSDE is a complicated server software, not something you can do
double-clicking installing and using. You need a lot of knowledge/skill to
set it up properly before using it.

yes, but maybe I've been a bit misunderstood. In the LAN environment
the security is set to 'SQL Server security' and the default user's
'sa' login is used (as MS has recommended in former times -> btw, data
security is not a main task for this application).
That's what I mean as I wrote "loginmode = sqlserver".
This will be provided by connectionstring data and works as I've
mentioned.
The same(?) configuration does not work on a local machine what looks
weird for me, but I'm not sure wheather it's really identically
because the costumer did this 'deployment' on his own.

If your MSDE is SQL Server2000 SP3 or later, "sa" account cannot be used by default installation (i.e. SQL Server's mixed mode is not enabled). You need to explicitly enable it during installation or after installation, until then, the "sa" user name and password cannot be used to connect to SQL Server MSDE.

You could use Enterprise Manager, SSMS/Express... to check/enable mixed security mode. Or look into registry to determine if mixed mode is enabled. However, do not use "sa" for any reason in application level. If you enabled mixed mode, you can simply and easily create a SQL Server login and give it whatever user name/password. Using "sa" with application is well known bad practice, and there is absolutely no reason to use it.



Nevertheless you are right, it is a good approach to configure certain
user/roles with corresponding permission sets.

Peter

.

Relevant Pages

  • Re: MSDE does not work for XP power user
    ... the security is set to 'SQL Server security' and the default user's ... You need to explicitly enable it during installation or after installation, until then, the "sa" user name and password cannot be used to connect to SQL Server MSDE. ... Or look into registry to determine if mixed mode is enabled. ...
    (microsoft.public.sqlserver.msde)
  • Re: Regarding setup for SharePoint Services 2.0...
    ... that means it's OK to set up SQL Server ... authentication as mixed mode when installing WSS? ... > following the single-server installation guide for that product. ... > mode or when wondering if mixed mode is a solid solution. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Regarding setup for SharePoint Services 2.0...
    ... For what it's worth I've just done a Project Server 2003 installation ... to the SQL Server 2K installation part of the guide it stressed that SQL ... Server 2K must be installed in mixed mode because you were going ... > advantages to Microsoft from a security perspective moving to a Windows ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Regarding setup for SharePoint Services 2.0...
    ... But after installation, all WSS functionality will ... continue to work if you switch back to Mixed Mode. ... like) that get real flaky if you are not running in Windows Only SQL Server ... advantages to Microsoft from a security perspective moving to a Windows Only ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Install Microsoft SQL Server 2000 Desktop Engine
    ... the command line and there's a /SAPWD switch that must be included on the ... After installation, make sure you go to microsoft.com and download the ... MS03-031 security patch. ... dying SQL Server service, I was somewhat shocked to find that MS hadn't ...
    (microsoft.public.fox.programmer.exchange)
Loading