Precedence Question: domain vs local password policy

When running SQL2K5 on W2K3 and creating a sql server login w/ both
CHECK_EXPIRATION and CHECK_POLICY set to ON, which password plicy will take
effect if there is both a local policy on that server and a domain policy
affecting that server? Generally, domain policy will take precedence over a
local policy, but SQL2K5 does not address this detail and which will take
effect. I've hunted down lots of documentation, but none of it seems clear.
Thanks.SQL Server doesn't deal with this issue. It simply hits the security API.
The domain policy will override the local policy which is by design in
Windows. SQL Server simply abides by what Windows enforces.
Mike Hotek
MHS Enterprises, Inc
http://www.mssqlserver.com
"DisgruntledTechGuy" <DisgruntledTechGuy@.discussions.microsoft.com> wrote in
message news:12CC258C-C990-47C0-A36D-6EEC39E42A03@.microsoft.com...
> When running SQL2K5 on W2K3 and creating a sql server login w/ both
> CHECK_EXPIRATION and CHECK_POLICY set to ON, which password plicy will
> take
> effect if there is both a local policy on that server and a domain policy
> affecting that server? Generally, domain policy will take precedence over
> a
> local policy, but SQL2K5 does not address this detail and which will take
> effect. I've hunted down lots of documentation, but none of it seems
> clear.
> Thanks.|||Thanks Mike. That's what I figured, but documentation out there was ambiguo
us.
"Michael Hotek" wrote:

> SQL Server doesn't deal with this issue. It simply hits the security API.
> The domain policy will override the local policy which is by design in
> Windows. SQL Server simply abides by what Windows enforces.
> --
> Mike Hotek
> MHS Enterprises, Inc
> http://www.mssqlserver.com
>
> "DisgruntledTechGuy" <DisgruntledTechGuy@.discussions.microsoft.com> wrote
in
> message news:12CC258C-C990-47C0-A36D-6EEC39E42A03@.microsoft.com...
>
>sql

Possible SQL 2000 Performance Issue

We have a SQL 2000 SP3 Server hosting the MOM 2000 application. We are
running the MSSQLSERVER service and SQLSERVERAGENT service using a Domain
service account.
Our audit level is set to All - this is in accordance with the customer's
requirements.
The application log is constantly being written to with mssqlserver events -
service account successful logon - we would expect this as we have the full
auditing enabled.
However, the MOM application is reporting the following is part of an error
in the application log;
"Not enough storage is available to process this command"
The server has 2GB RAM and the Sqlservr process runs at about 1.5Gb of this
- is it likely to be the amount of auditing that is causing the error or not
enough RAM or combination of the two ?Any problem observed in the SQL server error log? Is ounds more like you are
running low/out of disk space.
"georgejuggins" wrote:
> We have a SQL 2000 SP3 Server hosting the MOM 2000 application. We are
> running the MSSQLSERVER service and SQLSERVERAGENT service using a Domain
> service account.
> Our audit level is set to All - this is in accordance with the customer's
> requirements.
> The application log is constantly being written to with mssqlserver events -
> service account successful logon - we would expect this as we have the full
> auditing enabled.
> However, the MOM application is reporting the following is part of an error
> in the application log;
> "Not enough storage is available to process this command"
> The server has 2GB RAM and the Sqlservr process runs at about 1.5Gb of this
> - is it likely to be the amount of auditing that is causing the error or not
> enough RAM or combination of the two ?
>