Re: SQL 2000 memory in W2K3

As you know, "Administrators" and "Domain Admins" are different groups.

Besides, using an account which has administrative rights for SQL Server is not recommended. That's why SQL Server 2005 has built-in groups and the service account that you use for SQL Server is added to that group and gain necessary permissions to work properly. Using an account that has administrative rights for SQL Server service is too much. For your information...

It would be enough to add a group that your SQL Server service is a member of to Lock Pages in Memory box in policy.

--
Ekrem Önsoy



"AP" <AP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:CDECC0E0-92CD-4AEC-B0EA-4FA0A8744239@xxxxxxxxxxxxxxxx
Sorry to bug you again. What about modifying the Lock pages in memory policy
on the server? Currently only the Administrator is in the policy. However,
the SQL server is running under the login of a domain user that is a member
of the domani admins group. Do I have to explicitly include this domain user
in the Lock pages in memory policy?



"Ekrem Önsoy" wrote:

Yep, restart it. It will not take effect unless you restart your SQL Server
service.

--
Ekrem Önsoy



"AP" <AP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F6EB314C-BB98-4299-AE3F-CB575CADF25F@xxxxxxxxxxxxxxxx
> One last item. It looks like even though I execute the sp and > reconfigure,
> for the AWE to kick in, I need to stop and re-start SQL, is this > correct?
>
>
>
> "Ekrem Önsoy" wrote:
>
>> Yes, for sure.
>>
>> -- >> Ekrem Önsoy
>>
>>
>>
>> "AP" <AP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:A3A6EAB7-F94F-4E76-81CD-23AE0E30DBBB@xxxxxxxxxxxxxxxx
>> > Tibor,
>> >
>> > However, EE still requires the AWE to be enabled, and the max server
>> > memory
>> > to be set, correct?
>> >
>> > AP
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> Yep. EE can use up to 64 GB (limited by OS and HW). SE is limited >> >> to
>> >> 2GB.
>> >> 2005 is another story.
>> >>
>> >> -- >> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://sqlblog.com/blogs/tibor_karaszi
>> >>
>> >>
>> >> "AP" <AP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:EF425ECB-7690-4730-81A3-2323F6F06ACD@xxxxxxxxxxxxxxxx
>> >> > Hank,
>> >> >
>> >> > The previous reply from Ekrem indicates that SQL 2000 can use >> >> > more
>> >> > than
>> >> > 2 GB
>> >> > of ram.
>> >> >
>> >> > AP
>> >> >
>> >> >
>> >> > "Hank Arnold (MVP)" wrote:
>> >> >
>> >> >> AP wrote:
>> >> >> > Just set up a new Dual Xeon Dual Core with 8 GB of physical >> >> >> > ram.
>> >> >> > It
>> >> >> > is
>> >> >> > running on Windows 2003 Enterprise Edition, and SQL 2000
>> >> >> > Enterprise
>> >> >> > Edition.
>> >> >> > The setup put the /PAE switch in the boot.ini. It only looks >> >> >> > like
>> >> >> > the server
>> >> >> > is using about 1.7 GB of ram at the moment. I have not changed
>> >> >> > any
>> >> >> > settings
>> >> >> > from the standard CD install. How can I be sure that the >> >> >> > server
>> >> >> > will
>> >> >> > utilize
>> >> >> > more of the ram when it requires it? It is not going to be
>> >> >> > running
>> >> >> > anything
>> >> >> > else other than the SQL.
>> >> >> >
>> >> >> > Thanks
>> >> >> IIRC, SQL2000 can't use more than 2GB RAM.....
>> >> >>
>> >> >> -- >> >> >>
>> >> >> Regards,
>> >> >> Hank Arnold
>> >> >> Microsoft MVP
>> >> >> Windows Server - Directory Services
>> >> >>
>> >>
>>


.

Relevant Pages

  • Re: Error 15401 using sp_grantlogin (not addressed by current KB articles)
    ... Restarting Windows 2000 resolved the problem for this particular account, ... confused when it sees a duplicate SID. ... > One way to get SQL Server to agree with the renamed NT ... > Preview (to ensure the script was created), ...
    (microsoft.public.sqlserver.security)
  • Re: SharePoint V3 Install Error
    ... But it our case it had to do with Group Policies that forbid the account of ... WSS FAQ:www.wssv3faq.com/wss.collutions.com ... Event Source: WindowsSharePointServices3Search ... whatever you are installing WSS as sufficient rights to the SQL Server ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: Problems with WebParts
    ... to a database called aspnetdb. ... > The connection string specifies a local SQL Server Express instance using a ... > server account must have read and write access to the applications directory. ... > This is necessary because the web server account will automatically create ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Cannot connect to Query Analyzer
    ... For Query Analyzer, I tried replacing the file as you suggested but had the ... same results (Enterprise Manager starts up fine, ... I created an account on my laptop and changed SQL ... Try replacing the MMC app for SQL Server from the original ...
    (microsoft.public.sqlserver.connect)
  • Re: Does anyone know how to fix this??
    ... > Inside the Active Directory Users and Computers in the folder of SYSTEM I ... Give the site's SMS Service account full control rights to the ... MP encountered an error when connecting to SQL Server. ...
    (microsoft.public.sms.setup)