connect to server name 2005!

First time I am using sql server 2005.
What is the default server name' I can not see anything in managment
studio.
whenever i tried to connect OR create database through SQL sever
Management studio, it asked me:
server type: (here i select Database Engine)
server Name : ( '')
Authentication : which one I have to use? (Windows Authentiction is by
default, another is SQL server Authentication,)...
I don't know what to do with server name . Please advise.Hi,
please do not mulitpost, answered in public.sqlserver
HTH, jens Suessmeyer.
http://www.sqlserver2005.de
--

connect to server name 2005!

First time I am using sql server 2005.
What is the default server name' I can not see anything in managment
studio.
whenever i tried to connect OR create database through SQL sever
Management studio, it asked me:
server type: (here i select Database Engine)
server Name : ( '')
Authentication : which one I have to use? (Windows Authentiction is by
default, another is SQL server Authentication,)...
I don't know what to do with server name . Please advise.Hi,
please do not mulitpost, answered in public.sqlserver
HTH, jens Suessmeyer.
--
http://www.sqlserver2005.de
--sqlsql

connect to named instance in a cluster

Windows 2003 N+1 cluster, SQL2005 enterprise + sp2
I have a N+1 cluster and installed default sql instance and one named
instance. SQL Browser service is running on the node which owns the named
instance; UDP port 1434 is opened on the firewall.
I had problem connecting to the named instance. Then I found the port number
in the sql error log which the named instance listens on. Opening this port
in firewall solved the connection problem.
My questions:
1. What's the best/secure way to connect to the named instance in a cluster?
Why does it not work with UDP opened and SQL Browser running before the
specific port is opened?
2. Will the port number change when the sql instance restarts? If yes, how
to assign a static port number?
Thanks.
Claudia
The short answer is that the behavior you observed is perfectly normal.
SQL will decide on a port when the service restarts unless it is a default
instance or you have locked SQL to a specific port number.
You can use the SQL Server Configuration Tool to "lock" the instance to a
specific port. This is done whenever a client needs a static port to
connect to.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Claudia" <Claudia@.discussions.microsoft.com> wrote in message
news:17766F0D-BF9B-4DA1-9D1A-126B57E422B4@.microsoft.com...
> Windows 2003 N+1 cluster, SQL2005 enterprise + sp2
> I have a N+1 cluster and installed default sql instance and one named
> instance. SQL Browser service is running on the node which owns the named
> instance; UDP port 1434 is opened on the firewall.
> I had problem connecting to the named instance. Then I found the port
> number
> in the sql error log which the named instance listens on. Opening this
> port
> in firewall solved the connection problem.
> My questions:
> 1. What's the best/secure way to connect to the named instance in a
> cluster?
> Why does it not work with UDP opened and SQL Browser running before the
> specific port is opened?
> 2. Will the port number change when the sql instance restarts? If yes, how
> to assign a static port number?
> Thanks.
> Claudia

Connect Sql server Mobile with VS2005

I have a default SQL server 2005 setup on my machine.

There is a large database to whom i can connect.

I made my own data by Sql server Mobile on my local machine and then try to connect it

to the the application in visual studio 2005.

But it each time it gives that the port cannot be open.

I am a native client for SQL server.

Do we have any idea how wil i connect to database local to machine with the

application in Visual studio 2005 with C# language.

thanks

Prashant Gupta

The actual message i am getting

Microsoft SQL Native Client Version 09.00.2047

Running connectivity tests...

Attempting connection
[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [53].
[Microsoft][SQL Native Client]Login timeout expired
[Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

TESTS FAILED!

Sorry, but your question is off topic here, since this is the forum with smart device development. Move to Sql Server 2005 forum.

Hint: it seems like the connection string is not correct.

Thanks!

|||Please post your connection string. Make sure that you enabled remote connections (see the screencast on my site for more information how to do this)

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||Do you need more help, or did you solve the problem ?
Jens K. Suessmeyer.

http://www.sqlserver2005.de

Connect Sql server Mobile with VS2005

I have a default SQL server 2005 setup on my machine.

There is a large database to whom i can connect.

I made my own data by Sql server Mobile on my local machine and then try to connect it

to the the application in visual studio 2005.

But it each time it gives that the port cannot be open.

I am a native client for SQL server.

Do we have any idea how wil i connect to database local to machine with the

application in Visual studio 2005 with C# language.

thanks

Prashant Gupta

The actual message i am getting

Microsoft SQL Native Client Version 09.00.2047

Running connectivity tests...

Attempting connection
[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [53].
[Microsoft][SQL Native Client]Login timeout expired
[Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

TESTS FAILED!

Sorry, but your question is off topic here, since this is the forum with smart device development. Move to Sql Server 2005 forum.

Hint: it seems like the connection string is not correct.

Thanks!

|||Please post your connection string. Make sure that you enabled remote connections (see the screencast on my site for more information how to do this)

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||Do you need more help, or did you solve the problem ?
Jens K. Suessmeyer.

http://www.sqlserver2005.de

Connect fails: Error 4064, Can not open user default DB

I just installed SQL Server 2005 CTP (9.00.1116) on Windows Server 2003 with SP1. Then I unzipped DotNetNuke portal site and tried to connect to it with various errors, generally relating to invalid login.

I never figured it out after many hours of exploring every SQL interface I could find, changing web.config's connection string, and editing the DotNetNuke ODBC Data Source. At one point I was able to intermittently sign in to the SQL Server Management Studio (but never to get DotNetNuke site to connect to the DB).

Late in this process I gave up, decided to reinstall DotNetNuke from scratch, and removed that directory with my default database. Maybe one isn't supposed to do this, but I did it and suspect that is the reason for the error message in the title of this post. I don't see a way to login in as another user either at this point.

If it is indeed possible for one to delete one's default database - and if so - is there any solution except a complete (multi-hour on my old system) reinstall of SQL Server?

If I try to connect using SQL user SA (user names are case insensative, right?!), I get error 18452: "The user is not associated with a trusted SQL Server Connection."

You can change default database for a user using ALTER LOGIN. You can check your current settings for all users using sys.server_principals.

As far as being unable to connect using ‘sa’ credentials, verify that you have mixed mode authentication enabled. If you do not that might explain why you are getting trusted connection error for ‘sa’.

This may also be affecting your inability to connect to the portal.

Overall, it is recommended that you upgrade to CTP 15 (build 1187), so reinstall might be the cleanest option. Make sure you select ‘mixed mode auth’ and set ‘sa’ password during setup.

Regards,

Boris.

|||Boris B is right , I had the same problem when i started using it and it turned out to be the default database i hat for the specific login .

Connect fails: Error 4064, Can not open user default DB

I just installed SQL Server 2005 CTP (9.00.1116) on Windows Server 2003 with SP1. Then I unzipped DotNetNuke portal site and tried to connect to it with various errors, generally relating to invalid login.

I never figured it out after many hours of exploring every SQL interface I could find, changing web.config's connection string, and editing the DotNetNuke ODBC Data Source. At one point I was able to intermittently sign in to the SQL Server Management Studio (but never to get DotNetNuke site to connect to the DB).

Late in this process I gave up, decided to reinstall DotNetNuke from scratch, and removed that directory with my default database. Maybe one isn't supposed to do this, but I did it and suspect that is the reason for the error message in the title of this post. I don't see a way to login in as another user either at this point.

If it is indeed possible for one to delete one's default database - and if so - is there any solution except a complete (multi-hour on my old system) reinstall of SQL Server?

If I try to connect using SQL user SA (user names are case insensative, right?!), I get error 18452: "The user is not associated with a trusted SQL Server Connection."

You can change default database for a user using ALTER LOGIN. You can check your current settings for all users using sys.server_principals.

As far as being unable to connect using ‘sa’ credentials, verify that you have mixed mode authentication enabled. If you do not that might explain why you are getting trusted connection error for ‘sa’.

This may also be affecting your inability to connect to the portal.

Overall, it is recommended that you upgrade to CTP 15 (build 1187), so reinstall might be the cleanest option. Make sure you select ‘mixed mode auth’ and set ‘sa’ password during setup.

Regards,

Boris.

|||Boris B is right , I had the same problem when i started using it and it turned out to be the default database i hat for the specific login .

Conflict Resolution: Is defining local subscription enough: How to get log of lost record.

Publisher always wins is the default, so you don't need
to do anything to achieve this.
To get notification of a conflict, you could create a
polling routine (there's no alert that I know of).
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
hi Paul,
Thanks for you reply, I have few more queries
1. Where is this conflict information specially the losing row information is stored, at the publisher side or at the subscriber side? if losing row information is maintained at the publisher side is there any way so that we can store this information at the publisher side.
2. As you talked about creating a polling routine to get notification of conflict, in my implementation I just want a log file which contain information about the losing row nothing else, will the polling routine you are referring to can do the same and alsoI have not much information about how to write polling routine can you throw some light on it?
regards.
Ruchir.

Quote:

Originally posted by Paul Ibison
Publisher always wins is the default, so you don't need
to do anything to achieve this.
To get notification of a conflict, you could create a
polling routine (there's no alert that I know of).
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

|||Have a look at the tables
conflict_<PublicationName>_<ArticleName>_usertable name
and
MSmerge_delete_conflicts
at the publisher.
The polling routine would be not much more than a job
that runs regularly and does a select from this table,
then sends the results in an email as an attachment. The
origin_datasource column could be used to determine the
correct recipient.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

configuring SQLDataSource with default database

Hello,

I have specified a default database in my web.config like this:

<dataConfigurationdefaultDatabase="scsLocal"/>

<connectionStrings>

<addname="scsLocal"connectionString="server=DRLSWARTEBRV;database=SCS;uid=******;password=******;"providerName="System.Data.SqlClient"/>

</connectionStrings>

Now I would like to configure a SQLDataSource control to use this default database, yet it prompts me for a connectionstring. I know I can program it in the code behind file (if I ommit connection string, it will use the default), but then I can make no use of the wizard for configuring the SQLDataSource which would safe me a lot of coding.

Is there a way to configure the SQLDataSource to use the default database that is specified in the web.config?

Thanks!

Veerle

Veerle:

<dataConfigurationdefaultDatabase="scsLocal"/>

I'm not sure about what you're trying to do with this but you can configure the SQLDataSource in your .aspx page like this:

<asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="<%$ ConnectionStrings:<the web.config parameter name>%>"
 SelectCommand="You select query here"
 <SelectParameters>
 <if any>
 </SelectParameters>
 </asp:SqlDataSource>

Hope this will help.

Configuring and using PAE on SQS Server 2000 Enterprise Edition

We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
machine with 16 GB of memory. I am trying to use more than the default 2GB of
memory for SQL Server.
I have added the /PAE switch to the boot.ini file on the server, configured
SQL Server by issuing a
sp_configure 'show advanced options', 1
RECONFIGURE
and a
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 14336
RECONFIGURE
GO
However, it looks like SQL Server is till using less than 2GB of memory when
running. I have run the sp_configure check on it's own and noticed that the
config_value for AWE enabled is 1, but that the run_value is still 0.
Could that be the problem? What do I have to do to fix this?
I know I did restart the server after adding the settings (the setting for
'show advanced options' and 'max server memory' both show the same value for
config and run_value. It is just the AWE enable setting that has a
discrepancy.
Should I set the 'max server memory' to less than 14 GB if the server has
16GB available? How much does the OS need?
Thanks
FredHow to configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
Managing AWE Memor
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
AMB
"fredscuba" wrote:
> We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> machine with 16 GB of memory. I am trying to use more than the default 2GB of
> memory for SQL Server.
> I have added the /PAE switch to the boot.ini file on the server, configured
> SQL Server by issuing a
> sp_configure 'show advanced options', 1
> RECONFIGURE
> and a
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 14336
> RECONFIGURE
> GO
> However, it looks like SQL Server is till using less than 2GB of memory when
> running. I have run the sp_configure check on it's own and noticed that the
> config_value for AWE enabled is 1, but that the run_value is still 0.
> Could that be the problem? What do I have to do to fix this?
> I know I did restart the server after adding the settings (the setting for
> 'show advanced options' and 'max server memory' both show the same value for
> config and run_value. It is just the AWE enable setting that has a
> discrepancy.
> Should I set the 'max server memory' to less than 14 GB if the server has
> 16GB available? How much does the OS need?
> Thanks
> Fred|||Alejandro,
I did go through the instructions that are shown on the pages you bookmarked
(see my original post).
My question is: why is SQL Server still using less than 2GB of memory even
after I have setup my boot.ini and enabled AWE and set the max server
memory?
Fred
"Alejandro Mesa" wrote:
> How to configure memory for more than 2 GB in SQL Server
> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
> Managing AWE Memory
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
>
> AMB
>
> "fredscuba" wrote:
> > We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> > machine with 16 GB of memory. I am trying to use more than the default 2GB of
> > memory for SQL Server.
> >
> > I have added the /PAE switch to the boot.ini file on the server, configured
> > SQL Server by issuing a
> >
> > sp_configure 'show advanced options', 1
> > RECONFIGURE
> >
> > and a
> >
> > sp_configure 'awe enabled', 1
> > RECONFIGURE
> > GO
> > sp_configure 'max server memory', 14336
> > RECONFIGURE
> > GO
> >
> > However, it looks like SQL Server is till using less than 2GB of memory when
> > running. I have run the sp_configure check on it's own and noticed that the
> > config_value for AWE enabled is 1, but that the run_value is still 0.
> >
> > Could that be the problem? What do I have to do to fix this?
> >
> > I know I did restart the server after adding the settings (the setting for
> > 'show advanced options' and 'max server memory' both show the same value for
> > config and run_value. It is just the AWE enable setting that has a
> > discrepancy.
> >
> > Should I set the 'max server memory' to less than 14 GB if the server has
> > 16GB available? How much does the OS need?
> >
> > Thanks
> >
> > Fred|||What Edition of Windows 2003 Server?
AMB
"fredscuba" wrote:
> Alejandro,
> I did go through the instructions that are shown on the pages you bookmarked
> (see my original post).
> My question is: why is SQL Server still using less than 2GB of memory even
> after I have setup my boot.ini and enabled AWE and set the max server
> memory?
> Fred
>
> "Alejandro Mesa" wrote:
> > How to configure memory for more than 2 GB in SQL Server
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
> >
> > Managing AWE Memory
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
> >
> >
> > AMB
> >
> >
> > "fredscuba" wrote:
> >
> > > We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> > > machine with 16 GB of memory. I am trying to use more than the default 2GB of
> > > memory for SQL Server.
> > >
> > > I have added the /PAE switch to the boot.ini file on the server, configured
> > > SQL Server by issuing a
> > >
> > > sp_configure 'show advanced options', 1
> > > RECONFIGURE
> > >
> > > and a
> > >
> > > sp_configure 'awe enabled', 1
> > > RECONFIGURE
> > > GO
> > > sp_configure 'max server memory', 14336
> > > RECONFIGURE
> > > GO
> > >
> > > However, it looks like SQL Server is till using less than 2GB of memory when
> > > running. I have run the sp_configure check on it's own and noticed that the
> > > config_value for AWE enabled is 1, but that the run_value is still 0.
> > >
> > > Could that be the problem? What do I have to do to fix this?
> > >
> > > I know I did restart the server after adding the settings (the setting for
> > > 'show advanced options' and 'max server memory' both show the same value for
> > > config and run_value. It is just the AWE enable setting that has a
> > > discrepancy.
> > >
> > > Should I set the 'max server memory' to less than 14 GB if the server has
> > > 16GB available? How much does the OS need?
> > >
> > > Thanks
> > >
> > > Fred|||Are you sure it is Enterprise Edition and not Std? What Edition is the OS?
What does @.@.VERSION or xp_MSVer show? After you get it going I would start
out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty and
there is a little room to spare for other apps.
--
Andrew J. Kelly SQL MVP
"fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
> Alejandro,
> I did go through the instructions that are shown on the pages you
> bookmarked
> (see my original post).
> My question is: why is SQL Server still using less than 2GB of memory even
> after I have setup my boot.ini and enabled AWE and set the max server
> memory?
> Fred
>
> "Alejandro Mesa" wrote:
>> How to configure memory for more than 2 GB in SQL Server
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
>> Managing AWE Memory
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
>>
>> AMB
>>
>> "fredscuba" wrote:
>> > We are running SQL Server 2000 Enterprise Edition on a Windows Server
>> > 2003
>> > machine with 16 GB of memory. I am trying to use more than the default
>> > 2GB of
>> > memory for SQL Server.
>> >
>> > I have added the /PAE switch to the boot.ini file on the server,
>> > configured
>> > SQL Server by issuing a
>> >
>> > sp_configure 'show advanced options', 1
>> > RECONFIGURE
>> >
>> > and a
>> >
>> > sp_configure 'awe enabled', 1
>> > RECONFIGURE
>> > GO
>> > sp_configure 'max server memory', 14336
>> > RECONFIGURE
>> > GO
>> >
>> > However, it looks like SQL Server is till using less than 2GB of memory
>> > when
>> > running. I have run the sp_configure check on it's own and noticed that
>> > the
>> > config_value for AWE enabled is 1, but that the run_value is still 0.
>> >
>> > Could that be the problem? What do I have to do to fix this?
>> >
>> > I know I did restart the server after adding the settings (the setting
>> > for
>> > 'show advanced options' and 'max server memory' both show the same
>> > value for
>> > config and run_value. It is just the AWE enable setting that has a
>> > discrepancy.
>> >
>> > Should I set the 'max server memory' to less than 14 GB if the server
>> > has
>> > 16GB available? How much does the OS need?
>> >
>> > Thanks
>> >
>> > Fred|||Andrew & Alejandro,
I am running Server 2003 Enterprise Edition and SQL Server 2000 Enterprise
Edition.
I think the problem is that the config_value for 'AWE enabled' is 1, but
that the run_value is still 0.
Why would that be? What do I have to do to fix this?
I am fairly sure that I restarted the server after changing the AWE setting,
but I can do it again after hours (it is a production server).
Is there any reason why the 'AWE enabled' setting would stay at a run_value
of 0, even after I try to set it with:
sp_configure 'awe enabled', 1
RECONFIGURE
Fred
"Andrew J. Kelly" wrote:
> Are you sure it is Enterprise Edition and not Std? What Edition is the OS?
> What does @.@.VERSION or xp_MSVer show? After you get it going I would start
> out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty and
> there is a little room to spare for other apps.
> --
> Andrew J. Kelly SQL MVP
>
> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
> > Alejandro,
> >
> > I did go through the instructions that are shown on the pages you
> > bookmarked
> > (see my original post).
> >
> > My question is: why is SQL Server still using less than 2GB of memory even
> > after I have setup my boot.ini and enabled AWE and set the max server
> > memory?
> >
> > Fred
> >
> >
> > "Alejandro Mesa" wrote:
> >
> >> How to configure memory for more than 2 GB in SQL Server
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
> >>
> >> Managing AWE Memory
> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
> >>
> >>
> >> AMB
> >>
> >>
> >> "fredscuba" wrote:
> >>
> >> > We are running SQL Server 2000 Enterprise Edition on a Windows Server
> >> > 2003
> >> > machine with 16 GB of memory. I am trying to use more than the default
> >> > 2GB of
> >> > memory for SQL Server.
> >> >
> >> > I have added the /PAE switch to the boot.ini file on the server,
> >> > configured
> >> > SQL Server by issuing a
> >> >
> >> > sp_configure 'show advanced options', 1
> >> > RECONFIGURE
> >> >
> >> > and a
> >> >
> >> > sp_configure 'awe enabled', 1
> >> > RECONFIGURE
> >> > GO
> >> > sp_configure 'max server memory', 14336
> >> > RECONFIGURE
> >> > GO
> >> >
> >> > However, it looks like SQL Server is till using less than 2GB of memory
> >> > when
> >> > running. I have run the sp_configure check on it's own and noticed that
> >> > the
> >> > config_value for AWE enabled is 1, but that the run_value is still 0.
> >> >
> >> > Could that be the problem? What do I have to do to fix this?
> >> >
> >> > I know I did restart the server after adding the settings (the setting
> >> > for
> >> > 'show advanced options' and 'max server memory' both show the same
> >> > value for
> >> > config and run_value. It is just the AWE enable setting that has a
> >> > discrepancy.
> >> >
> >> > Should I set the 'max server memory' to less than 14 GB if the server
> >> > has
> >> > 16GB available? How much does the OS need?
> >> >
> >> > Thanks
> >> >
> >> > Fred
>
>|||The most obvious reason would be that you didn't actually restart SQL
Server. I would try that and see if it fixes it.
--
Andrew J. Kelly SQL MVP
"fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
news:27D53CE0-A064-4B3A-83CA-25293115FA99@.microsoft.com...
> Andrew & Alejandro,
> I am running Server 2003 Enterprise Edition and SQL Server 2000 Enterprise
> Edition.
> I think the problem is that the config_value for 'AWE enabled' is 1, but
> that the run_value is still 0.
> Why would that be? What do I have to do to fix this?
> I am fairly sure that I restarted the server after changing the AWE
> setting,
> but I can do it again after hours (it is a production server).
> Is there any reason why the 'AWE enabled' setting would stay at a
> run_value
> of 0, even after I try to set it with:
> sp_configure 'awe enabled', 1
> RECONFIGURE
>
> Fred
>
> "Andrew J. Kelly" wrote:
>> Are you sure it is Enterprise Edition and not Std? What Edition is the
>> OS?
>> What does @.@.VERSION or xp_MSVer show? After you get it going I would
>> start
>> out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty
>> and
>> there is a little room to spare for other apps.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
>> news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
>> > Alejandro,
>> >
>> > I did go through the instructions that are shown on the pages you
>> > bookmarked
>> > (see my original post).
>> >
>> > My question is: why is SQL Server still using less than 2GB of memory
>> > even
>> > after I have setup my boot.ini and enabled AWE and set the max server
>> > memory?
>> >
>> > Fred
>> >
>> >
>> > "Alejandro Mesa" wrote:
>> >
>> >> How to configure memory for more than 2 GB in SQL Server
>> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
>> >>
>> >> Managing AWE Memory
>> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
>> >>
>> >>
>> >> AMB
>> >>
>> >>
>> >> "fredscuba" wrote:
>> >>
>> >> > We are running SQL Server 2000 Enterprise Edition on a Windows
>> >> > Server
>> >> > 2003
>> >> > machine with 16 GB of memory. I am trying to use more than the
>> >> > default
>> >> > 2GB of
>> >> > memory for SQL Server.
>> >> >
>> >> > I have added the /PAE switch to the boot.ini file on the server,
>> >> > configured
>> >> > SQL Server by issuing a
>> >> >
>> >> > sp_configure 'show advanced options', 1
>> >> > RECONFIGURE
>> >> >
>> >> > and a
>> >> >
>> >> > sp_configure 'awe enabled', 1
>> >> > RECONFIGURE
>> >> > GO
>> >> > sp_configure 'max server memory', 14336
>> >> > RECONFIGURE
>> >> > GO
>> >> >
>> >> > However, it looks like SQL Server is till using less than 2GB of
>> >> > memory
>> >> > when
>> >> > running. I have run the sp_configure check on it's own and noticed
>> >> > that
>> >> > the
>> >> > config_value for AWE enabled is 1, but that the run_value is still
>> >> > 0.
>> >> >
>> >> > Could that be the problem? What do I have to do to fix this?
>> >> >
>> >> > I know I did restart the server after adding the settings (the
>> >> > setting
>> >> > for
>> >> > 'show advanced options' and 'max server memory' both show the same
>> >> > value for
>> >> > config and run_value. It is just the AWE enable setting that has a
>> >> > discrepancy.
>> >> >
>> >> > Should I set the 'max server memory' to less than 14 GB if the
>> >> > server
>> >> > has
>> >> > 16GB available? How much does the OS need?
>> >> >
>> >> > Thanks
>> >> >
>> >> > Fred
>>|||Hi,
Apologies if this has already been checked, but have you looked in the SQL
Server log for an entry of 'Address Windowing Extensions enabled' to clarify
if AWE is enabled or not?
--
Regards
Robert
"fredscuba" wrote:
> Andrew & Alejandro,
> I am running Server 2003 Enterprise Edition and SQL Server 2000 Enterprise
> Edition.
> I think the problem is that the config_value for 'AWE enabled' is 1, but
> that the run_value is still 0.
> Why would that be? What do I have to do to fix this?
> I am fairly sure that I restarted the server after changing the AWE setting,
> but I can do it again after hours (it is a production server).
> Is there any reason why the 'AWE enabled' setting would stay at a run_value
> of 0, even after I try to set it with:
> sp_configure 'awe enabled', 1
> RECONFIGURE
>
> Fred
>
> "Andrew J. Kelly" wrote:
> > Are you sure it is Enterprise Edition and not Std? What Edition is the OS?
> > What does @.@.VERSION or xp_MSVer show? After you get it going I would start
> > out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty and
> > there is a little room to spare for other apps.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> > news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
> > > Alejandro,
> > >
> > > I did go through the instructions that are shown on the pages you
> > > bookmarked
> > > (see my original post).
> > >
> > > My question is: why is SQL Server still using less than 2GB of memory even
> > > after I have setup my boot.ini and enabled AWE and set the max server
> > > memory?
> > >
> > > Fred
> > >
> > >
> > > "Alejandro Mesa" wrote:
> > >
> > >> How to configure memory for more than 2 GB in SQL Server
> > >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
> > >>
> > >> Managing AWE Memory
> > >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
> > >>
> > >>
> > >> AMB
> > >>
> > >>
> > >> "fredscuba" wrote:
> > >>
> > >> > We are running SQL Server 2000 Enterprise Edition on a Windows Server
> > >> > 2003
> > >> > machine with 16 GB of memory. I am trying to use more than the default
> > >> > 2GB of
> > >> > memory for SQL Server.
> > >> >
> > >> > I have added the /PAE switch to the boot.ini file on the server,
> > >> > configured
> > >> > SQL Server by issuing a
> > >> >
> > >> > sp_configure 'show advanced options', 1
> > >> > RECONFIGURE
> > >> >
> > >> > and a
> > >> >
> > >> > sp_configure 'awe enabled', 1
> > >> > RECONFIGURE
> > >> > GO
> > >> > sp_configure 'max server memory', 14336
> > >> > RECONFIGURE
> > >> > GO
> > >> >
> > >> > However, it looks like SQL Server is till using less than 2GB of memory
> > >> > when
> > >> > running. I have run the sp_configure check on it's own and noticed that
> > >> > the
> > >> > config_value for AWE enabled is 1, but that the run_value is still 0.
> > >> >
> > >> > Could that be the problem? What do I have to do to fix this?
> > >> >
> > >> > I know I did restart the server after adding the settings (the setting
> > >> > for
> > >> > 'show advanced options' and 'max server memory' both show the same
> > >> > value for
> > >> > config and run_value. It is just the AWE enable setting that has a
> > >> > discrepancy.
> > >> >
> > >> > Should I set the 'max server memory' to less than 14 GB if the server
> > >> > has
> > >> > 16GB available? How much does the OS need?
> > >> >
> > >> > Thanks
> > >> >
> > >> > Fred
> >
> >
> >|||And check to make sure the account sql server is running under has Lock
Pages In Memory rights.
--
Andrew J. Kelly SQL MVP
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:u2cLo5lhFHA.576@.TK2MSFTNGP15.phx.gbl...
> The most obvious reason would be that you didn't actually restart SQL
> Server. I would try that and see if it fixes it.
> --
> Andrew J. Kelly SQL MVP
>
> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> news:27D53CE0-A064-4B3A-83CA-25293115FA99@.microsoft.com...
>> Andrew & Alejandro,
>> I am running Server 2003 Enterprise Edition and SQL Server 2000
>> Enterprise
>> Edition.
>> I think the problem is that the config_value for 'AWE enabled' is 1, but
>> that the run_value is still 0.
>> Why would that be? What do I have to do to fix this?
>> I am fairly sure that I restarted the server after changing the AWE
>> setting,
>> but I can do it again after hours (it is a production server).
>> Is there any reason why the 'AWE enabled' setting would stay at a
>> run_value
>> of 0, even after I try to set it with:
>> sp_configure 'awe enabled', 1
>> RECONFIGURE
>>
>> Fred
>>
>> "Andrew J. Kelly" wrote:
>> Are you sure it is Enterprise Edition and not Std? What Edition is the
>> OS?
>> What does @.@.VERSION or xp_MSVer show? After you get it going I would
>> start
>> out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty
>> and
>> there is a little room to spare for other apps.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
>> news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
>> > Alejandro,
>> >
>> > I did go through the instructions that are shown on the pages you
>> > bookmarked
>> > (see my original post).
>> >
>> > My question is: why is SQL Server still using less than 2GB of memory
>> > even
>> > after I have setup my boot.ini and enabled AWE and set the max server
>> > memory?
>> >
>> > Fred
>> >
>> >
>> > "Alejandro Mesa" wrote:
>> >
>> >> How to configure memory for more than 2 GB in SQL Server
>> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
>> >>
>> >> Managing AWE Memory
>> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
>> >>
>> >>
>> >> AMB
>> >>
>> >>
>> >> "fredscuba" wrote:
>> >>
>> >> > We are running SQL Server 2000 Enterprise Edition on a Windows
>> >> > Server
>> >> > 2003
>> >> > machine with 16 GB of memory. I am trying to use more than the
>> >> > default
>> >> > 2GB of
>> >> > memory for SQL Server.
>> >> >
>> >> > I have added the /PAE switch to the boot.ini file on the server,
>> >> > configured
>> >> > SQL Server by issuing a
>> >> >
>> >> > sp_configure 'show advanced options', 1
>> >> > RECONFIGURE
>> >> >
>> >> > and a
>> >> >
>> >> > sp_configure 'awe enabled', 1
>> >> > RECONFIGURE
>> >> > GO
>> >> > sp_configure 'max server memory', 14336
>> >> > RECONFIGURE
>> >> > GO
>> >> >
>> >> > However, it looks like SQL Server is till using less than 2GB of
>> >> > memory
>> >> > when
>> >> > running. I have run the sp_configure check on it's own and noticed
>> >> > that
>> >> > the
>> >> > config_value for AWE enabled is 1, but that the run_value is still
>> >> > 0.
>> >> >
>> >> > Could that be the problem? What do I have to do to fix this?
>> >> >
>> >> > I know I did restart the server after adding the settings (the
>> >> > setting
>> >> > for
>> >> > 'show advanced options' and 'max server memory' both show the same
>> >> > value for
>> >> > config and run_value. It is just the AWE enable setting that has a
>> >> > discrepancy.
>> >> >
>> >> > Should I set the 'max server memory' to less than 14 GB if the
>> >> > server
>> >> > has
>> >> > 16GB available? How much does the OS need?
>> >> >
>> >> > Thanks
>> >> >
>> >> > Fred
>>
>|||Hi
Before you set AWE you need to set "Lock Pages In Memory" first.
How to set the "Lock Pages In Memory", Please see URL
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_servp_2vqh.asp
By default SQL Seerver 2000 in Windows 2003 is disable.
Goog luck
Bogi Wu
"fredscuba" wrote:
> We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> machine with 16 GB of memory. I am trying to use more than the default 2GB of
> memory for SQL Server.
> I have added the /PAE switch to the boot.ini file on the server, configured
> SQL Server by issuing a
> sp_configure 'show advanced options', 1
> RECONFIGURE
> and a
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 14336
> RECONFIGURE
> GO
> However, it looks like SQL Server is till using less than 2GB of memory when
> running. I have run the sp_configure check on it's own and noticed that the
> config_value for AWE enabled is 1, but that the run_value is still 0.
> Could that be the problem? What do I have to do to fix this?
> I know I did restart the server after adding the settings (the setting for
> 'show advanced options' and 'max server memory' both show the same value for
> config and run_value. It is just the AWE enable setting that has a
> discrepancy.
> Should I set the 'max server memory' to less than 14 GB if the server has
> 16GB available? How much does the OS need?
> Thanks
> Fred|||OK, I did reboot the server and afterwards I could verify that the run_value
for 'AWE enabled' is now 1.
The 'min server memory' is set to 1024 (1 GB) and the 'max server memory'
is set to 10240 (10GB). The server has 16GB of memory, but I will be sharing
that with the OS and with a SAS application, so I thought that 10GB for SQL
Server is a good number to start with.
*HOWEVER* when I check the memory utilization on the server through the Task
Manager, it now shows that the process sqlservr.exe is only using 141,164 K
of memory - only about 138 MB!!
Why would this be? Could this be correct? The server is being used pretty
heavily right now - it is not a transaction heavy load, more a batch type
load with millions of records being updated in a batch.
My impression was that if AWE is enabled and PAE is used, that the memory
allocation is not dynamic anymore, but static, according to what you specify
in the max server memory setting.
Why would it then show such a low memory utilization by SQL Server? (It used
to hover around 1.7 GB before I enabled PAE and AWE).
Fred
"Andrew J. Kelly" wrote:
> And check to make sure the account sql server is running under has Lock
> Pages In Memory rights.
> --
> Andrew J. Kelly SQL MVP
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:u2cLo5lhFHA.576@.TK2MSFTNGP15.phx.gbl...
> > The most obvious reason would be that you didn't actually restart SQL
> > Server. I would try that and see if it fixes it.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> > news:27D53CE0-A064-4B3A-83CA-25293115FA99@.microsoft.com...
> >> Andrew & Alejandro,
> >>
> >> I am running Server 2003 Enterprise Edition and SQL Server 2000
> >> Enterprise
> >> Edition.
> >>
> >> I think the problem is that the config_value for 'AWE enabled' is 1, but
> >> that the run_value is still 0.
> >>
> >> Why would that be? What do I have to do to fix this?
> >>
> >> I am fairly sure that I restarted the server after changing the AWE
> >> setting,
> >> but I can do it again after hours (it is a production server).
> >>
> >> Is there any reason why the 'AWE enabled' setting would stay at a
> >> run_value
> >> of 0, even after I try to set it with:
> >>
> >> sp_configure 'awe enabled', 1
> >> RECONFIGURE
> >>
> >>
> >> Fred
> >>
> >>
> >> "Andrew J. Kelly" wrote:
> >>
> >> Are you sure it is Enterprise Edition and not Std? What Edition is the
> >> OS?
> >> What does @.@.VERSION or xp_MSVer show? After you get it going I would
> >> start
> >> out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty
> >> and
> >> there is a little room to spare for other apps.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> >> news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
> >> > Alejandro,
> >> >
> >> > I did go through the instructions that are shown on the pages you
> >> > bookmarked
> >> > (see my original post).
> >> >
> >> > My question is: why is SQL Server still using less than 2GB of memory
> >> > even
> >> > after I have setup my boot.ini and enabled AWE and set the max server
> >> > memory?
> >> >
> >> > Fred
> >> >
> >> >
> >> > "Alejandro Mesa" wrote:
> >> >
> >> >> How to configure memory for more than 2 GB in SQL Server
> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
> >> >>
> >> >> Managing AWE Memory
> >> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
> >> >>
> >> >>
> >> >> AMB
> >> >>
> >> >>
> >> >> "fredscuba" wrote:
> >> >>
> >> >> > We are running SQL Server 2000 Enterprise Edition on a Windows
> >> >> > Server
> >> >> > 2003
> >> >> > machine with 16 GB of memory. I am trying to use more than the
> >> >> > default
> >> >> > 2GB of
> >> >> > memory for SQL Server.
> >> >> >
> >> >> > I have added the /PAE switch to the boot.ini file on the server,
> >> >> > configured
> >> >> > SQL Server by issuing a
> >> >> >
> >> >> > sp_configure 'show advanced options', 1
> >> >> > RECONFIGURE
> >> >> >
> >> >> > and a
> >> >> >
> >> >> > sp_configure 'awe enabled', 1
> >> >> > RECONFIGURE
> >> >> > GO
> >> >> > sp_configure 'max server memory', 14336
> >> >> > RECONFIGURE
> >> >> > GO
> >> >> >
> >> >> > However, it looks like SQL Server is till using less than 2GB of
> >> >> > memory
> >> >> > when
> >> >> > running. I have run the sp_configure check on it's own and noticed
> >> >> > that
> >> >> > the
> >> >> > config_value for AWE enabled is 1, but that the run_value is still
> >> >> > 0.
> >> >> >
> >> >> > Could that be the problem? What do I have to do to fix this?
> >> >> >
> >> >> > I know I did restart the server after adding the settings (the
> >> >> > setting
> >> >> > for
> >> >> > 'show advanced options' and 'max server memory' both show the same
> >> >> > value for
> >> >> > config and run_value. It is just the AWE enable setting that has a
> >> >> > discrepancy.
> >> >> >
> >> >> > Should I set the 'max server memory' to less than 14 GB if the
> >> >> > server
> >> >> > has
> >> >> > 16GB available? How much does the OS need?
> >> >> >
> >> >> > Thanks
> >> >> >
> >> >> > Fred
> >>
> >>
> >>
> >
> >
>
>|||Hi,
I followed the link you provided, but there is a note saying that "This
functionality is available only if you are running the Microsoft® Windows®
2000 operating system".
Can I or should I do it if I am running on Windows Server 2003?
Fred
"BogiWu" wrote:
> Hi
> Before you set AWE you need to set "Lock Pages In Memory" first.
> How to set the "Lock Pages In Memory", Please see URL
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_servp_2vqh.asp
> By default SQL Seerver 2000 in Windows 2003 is disable.
> Goog luck
> Bogi Wu
> "fredscuba" wrote:
> > We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> > machine with 16 GB of memory. I am trying to use more than the default 2GB of
> > memory for SQL Server.
> >
> > I have added the /PAE switch to the boot.ini file on the server, configured
> > SQL Server by issuing a
> >
> > sp_configure 'show advanced options', 1
> > RECONFIGURE
> >
> > and a
> >
> > sp_configure 'awe enabled', 1
> > RECONFIGURE
> > GO
> > sp_configure 'max server memory', 14336
> > RECONFIGURE
> > GO
> >
> > However, it looks like SQL Server is till using less than 2GB of memory when
> > running. I have run the sp_configure check on it's own and noticed that the
> > config_value for AWE enabled is 1, but that the run_value is still 0.
> >
> > Could that be the problem? What do I have to do to fix this?
> >
> > I know I did restart the server after adding the settings (the setting for
> > 'show advanced options' and 'max server memory' both show the same value for
> > config and run_value. It is just the AWE enable setting that has a
> > discrepancy.
> >
> > Should I set the 'max server memory' to less than 14 GB if the server has
> > 16GB available? How much does the OS need?
> >
> > Thanks
> >
> > Fred|||Never mind - the account running SQL Server already has the ability to lock
pages in memory.
My problem now is that SQL Server does not seem to be using all of the
memory I set aside for it under the max server memory setting. (see my other
post from today)
Fred
"fredscuba" wrote:
> Hi,
> I followed the link you provided, but there is a note saying that "This
> functionality is available only if you are running the Microsoft® Windows®
> 2000 operating system".
> Can I or should I do it if I am running on Windows Server 2003?
>
> Fred
> "BogiWu" wrote:
> > Hi
> > Before you set AWE you need to set "Lock Pages In Memory" first.
> > How to set the "Lock Pages In Memory", Please see URL
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_servp_2vqh.asp
> > By default SQL Seerver 2000 in Windows 2003 is disable.
> >
> > Goog luck
> >
> > Bogi Wu
> > "fredscuba" wrote:
> >
> > > We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> > > machine with 16 GB of memory. I am trying to use more than the default 2GB of
> > > memory for SQL Server.
> > >
> > > I have added the /PAE switch to the boot.ini file on the server, configured
> > > SQL Server by issuing a
> > >
> > > sp_configure 'show advanced options', 1
> > > RECONFIGURE
> > >
> > > and a
> > >
> > > sp_configure 'awe enabled', 1
> > > RECONFIGURE
> > > GO
> > > sp_configure 'max server memory', 14336
> > > RECONFIGURE
> > > GO
> > >
> > > However, it looks like SQL Server is till using less than 2GB of memory when
> > > running. I have run the sp_configure check on it's own and noticed that the
> > > config_value for AWE enabled is 1, but that the run_value is still 0.
> > >
> > > Could that be the problem? What do I have to do to fix this?
> > >
> > > I know I did restart the server after adding the settings (the setting for
> > > 'show advanced options' and 'max server memory' both show the same value for
> > > config and run_value. It is just the AWE enable setting that has a
> > > discrepancy.
> > >
> > > Should I set the 'max server memory' to less than 14 GB if the server has
> > > 16GB available? How much does the OS need?
> > >
> > > Thanks
> > >
> > > Fred|||Task Manager isn't PAE aware. Use Perf Mon.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
news:3AB99BA7-408F-4B05-B44B-DA2D78FE0053@.microsoft.com...
> OK, I did reboot the server and afterwards I could verify that the run_value
> for 'AWE enabled' is now 1.
> The 'min server memory' is set to 1024 (1 GB) and the 'max server memory'
> is set to 10240 (10GB). The server has 16GB of memory, but I will be sharing
> that with the OS and with a SAS application, so I thought that 10GB for SQL
> Server is a good number to start with.
> *HOWEVER* when I check the memory utilization on the server through the Task
> Manager, it now shows that the process sqlservr.exe is only using 141,164 K
> of memory - only about 138 MB!!
> Why would this be? Could this be correct? The server is being used pretty
> heavily right now - it is not a transaction heavy load, more a batch type
> load with millions of records being updated in a batch.
> My impression was that if AWE is enabled and PAE is used, that the memory
> allocation is not dynamic anymore, but static, according to what you specify
> in the max server memory setting.
> Why would it then show such a low memory utilization by SQL Server? (It used
> to hover around 1.7 GB before I enabled PAE and AWE).
>
> Fred
> "Andrew J. Kelly" wrote:
>> And check to make sure the account sql server is running under has Lock
>> Pages In Memory rights.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> news:u2cLo5lhFHA.576@.TK2MSFTNGP15.phx.gbl...
>> > The most obvious reason would be that you didn't actually restart SQL
>> > Server. I would try that and see if it fixes it.
>> >
>> > --
>> > Andrew J. Kelly SQL MVP
>> >
>> >
>> > "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
>> > news:27D53CE0-A064-4B3A-83CA-25293115FA99@.microsoft.com...
>> >> Andrew & Alejandro,
>> >>
>> >> I am running Server 2003 Enterprise Edition and SQL Server 2000
>> >> Enterprise
>> >> Edition.
>> >>
>> >> I think the problem is that the config_value for 'AWE enabled' is 1, but
>> >> that the run_value is still 0.
>> >>
>> >> Why would that be? What do I have to do to fix this?
>> >>
>> >> I am fairly sure that I restarted the server after changing the AWE
>> >> setting,
>> >> but I can do it again after hours (it is a production server).
>> >>
>> >> Is there any reason why the 'AWE enabled' setting would stay at a
>> >> run_value
>> >> of 0, even after I try to set it with:
>> >>
>> >> sp_configure 'awe enabled', 1
>> >> RECONFIGURE
>> >>
>> >>
>> >> Fred
>> >>
>> >>
>> >> "Andrew J. Kelly" wrote:
>> >>
>> >> Are you sure it is Enterprise Edition and not Std? What Edition is the
>> >> OS?
>> >> What does @.@.VERSION or xp_MSVer show? After you get it going I would
>> >> start
>> >> out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty
>> >> and
>> >> there is a little room to spare for other apps.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
>> >> news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
>> >> > Alejandro,
>> >> >
>> >> > I did go through the instructions that are shown on the pages you
>> >> > bookmarked
>> >> > (see my original post).
>> >> >
>> >> > My question is: why is SQL Server still using less than 2GB of memory
>> >> > even
>> >> > after I have setup my boot.ini and enabled AWE and set the max server
>> >> > memory?
>> >> >
>> >> > Fred
>> >> >
>> >> >
>> >> > "Alejandro Mesa" wrote:
>> >> >
>> >> >> How to configure memory for more than 2 GB in SQL Server
>> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
>> >> >>
>> >> >> Managing AWE Memory
>> >> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
>> >> >>
>> >> >>
>> >> >> AMB
>> >> >>
>> >> >>
>> >> >> "fredscuba" wrote:
>> >> >>
>> >> >> > We are running SQL Server 2000 Enterprise Edition on a Windows
>> >> >> > Server
>> >> >> > 2003
>> >> >> > machine with 16 GB of memory. I am trying to use more than the
>> >> >> > default
>> >> >> > 2GB of
>> >> >> > memory for SQL Server.
>> >> >> >
>> >> >> > I have added the /PAE switch to the boot.ini file on the server,
>> >> >> > configured
>> >> >> > SQL Server by issuing a
>> >> >> >
>> >> >> > sp_configure 'show advanced options', 1
>> >> >> > RECONFIGURE
>> >> >> >
>> >> >> > and a
>> >> >> >
>> >> >> > sp_configure 'awe enabled', 1
>> >> >> > RECONFIGURE
>> >> >> > GO
>> >> >> > sp_configure 'max server memory', 14336
>> >> >> > RECONFIGURE
>> >> >> > GO
>> >> >> >
>> >> >> > However, it looks like SQL Server is till using less than 2GB of
>> >> >> > memory
>> >> >> > when
>> >> >> > running. I have run the sp_configure check on it's own and noticed
>> >> >> > that
>> >> >> > the
>> >> >> > config_value for AWE enabled is 1, but that the run_value is still
>> >> >> > 0.
>> >> >> >
>> >> >> > Could that be the problem? What do I have to do to fix this?
>> >> >> >
>> >> >> > I know I did restart the server after adding the settings (the
>> >> >> > setting
>> >> >> > for
>> >> >> > 'show advanced options' and 'max server memory' both show the same
>> >> >> > value for
>> >> >> > config and run_value. It is just the AWE enable setting that has a
>> >> >> > discrepancy.
>> >> >> >
>> >> >> > Should I set the 'max server memory' to less than 14 GB if the
>> >> >> > server
>> >> >> > has
>> >> >> > 16GB available? How much does the OS need?
>> >> >> >
>> >> >> > Thanks
>> >> >> >
>> >> >> > Fred
>> >>
>> >>
>> >>
>> >
>> >
>>|||Thanks!
Perf Mon shows a static number for the memory assigned to SQL Server and it
matches what I set the max server memory setting to.
Fred
"Tibor Karaszi" wrote:
> Task Manager isn't PAE aware. Use Perf Mon.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> news:3AB99BA7-408F-4B05-B44B-DA2D78FE0053@.microsoft.com...
> > OK, I did reboot the server and afterwards I could verify that the run_value
> > for 'AWE enabled' is now 1.
> >
> > The 'min server memory' is set to 1024 (1 GB) and the 'max server memory'
> > is set to 10240 (10GB). The server has 16GB of memory, but I will be sharing
> > that with the OS and with a SAS application, so I thought that 10GB for SQL
> > Server is a good number to start with.
> >
> > *HOWEVER* when I check the memory utilization on the server through the Task
> > Manager, it now shows that the process sqlservr.exe is only using 141,164 K
> > of memory - only about 138 MB!!
> >
> > Why would this be? Could this be correct? The server is being used pretty
> > heavily right now - it is not a transaction heavy load, more a batch type
> > load with millions of records being updated in a batch.
> >
> > My impression was that if AWE is enabled and PAE is used, that the memory
> > allocation is not dynamic anymore, but static, according to what you specify
> > in the max server memory setting.
> >
> > Why would it then show such a low memory utilization by SQL Server? (It used
> > to hover around 1.7 GB before I enabled PAE and AWE).
> >
> >
> > Fred
> >
> > "Andrew J. Kelly" wrote:
> >
> >> And check to make sure the account sql server is running under has Lock
> >> Pages In Memory rights.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> >> news:u2cLo5lhFHA.576@.TK2MSFTNGP15.phx.gbl...
> >> > The most obvious reason would be that you didn't actually restart SQL
> >> > Server. I would try that and see if it fixes it.
> >> >
> >> > --
> >> > Andrew J. Kelly SQL MVP
> >> >
> >> >
> >> > "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> >> > news:27D53CE0-A064-4B3A-83CA-25293115FA99@.microsoft.com...
> >> >> Andrew & Alejandro,
> >> >>
> >> >> I am running Server 2003 Enterprise Edition and SQL Server 2000
> >> >> Enterprise
> >> >> Edition.
> >> >>
> >> >> I think the problem is that the config_value for 'AWE enabled' is 1, but
> >> >> that the run_value is still 0.
> >> >>
> >> >> Why would that be? What do I have to do to fix this?
> >> >>
> >> >> I am fairly sure that I restarted the server after changing the AWE
> >> >> setting,
> >> >> but I can do it again after hours (it is a production server).
> >> >>
> >> >> Is there any reason why the 'AWE enabled' setting would stay at a
> >> >> run_value
> >> >> of 0, even after I try to set it with:
> >> >>
> >> >> sp_configure 'awe enabled', 1
> >> >> RECONFIGURE
> >> >>
> >> >>
> >> >> Fred
> >> >>
> >> >>
> >> >> "Andrew J. Kelly" wrote:
> >> >>
> >> >> Are you sure it is Enterprise Edition and not Std? What Edition is the
> >> >> OS?
> >> >> What does @.@.VERSION or xp_MSVer show? After you get it going I would
> >> >> start
> >> >> out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty
> >> >> and
> >> >> there is a little room to spare for other apps.
> >> >>
> >> >> --
> >> >> Andrew J. Kelly SQL MVP
> >> >>
> >> >>
> >> >> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> >> >> news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
> >> >> > Alejandro,
> >> >> >
> >> >> > I did go through the instructions that are shown on the pages you
> >> >> > bookmarked
> >> >> > (see my original post).
> >> >> >
> >> >> > My question is: why is SQL Server still using less than 2GB of memory
> >> >> > even
> >> >> > after I have setup my boot.ini and enabled AWE and set the max server
> >> >> > memory?
> >> >> >
> >> >> > Fred
> >> >> >
> >> >> >
> >> >> > "Alejandro Mesa" wrote:
> >> >> >
> >> >> >> How to configure memory for more than 2 GB in SQL Server
> >> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
> >> >> >>
> >> >> >> Managing AWE Memory
> >> >> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
> >> >> >>
> >> >> >>
> >> >> >> AMB
> >> >> >>
> >> >> >>
> >> >> >> "fredscuba" wrote:
> >> >> >>
> >> >> >> > We are running SQL Server 2000 Enterprise Edition on a Windows
> >> >> >> > Server
> >> >> >> > 2003
> >> >> >> > machine with 16 GB of memory. I am trying to use more than the
> >> >> >> > default
> >> >> >> > 2GB of
> >> >> >> > memory for SQL Server.
> >> >> >> >
> >> >> >> > I have added the /PAE switch to the boot.ini file on the server,
> >> >> >> > configured
> >> >> >> > SQL Server by issuing a
> >> >> >> >
> >> >> >> > sp_configure 'show advanced options', 1
> >> >> >> > RECONFIGURE
> >> >> >> >
> >> >> >> > and a
> >> >> >> >
> >> >> >> > sp_configure 'awe enabled', 1
> >> >> >> > RECONFIGURE
> >> >> >> > GO
> >> >> >> > sp_configure 'max server memory', 14336
> >> >> >> > RECONFIGURE
> >> >> >> > GO
> >> >> >> >
> >> >> >> > However, it looks like SQL Server is till using less than 2GB of
> >> >> >> > memory
> >> >> >> > when
> >> >> >> > running. I have run the sp_configure check on it's own and noticed
> >> >> >> > that
> >> >> >> > the
> >> >> >> > config_value for AWE enabled is 1, but that the run_value is still
> >> >> >> > 0.
> >> >> >> >
> >> >> >> > Could that be the problem? What do I have to do to fix this?
> >> >> >> >
> >> >> >> > I know I did restart the server after adding the settings (the
> >> >> >> > setting
> >> >> >> > for
> >> >> >> > 'show advanced options' and 'max server memory' both show the same
> >> >> >> > value for
> >> >> >> > config and run_value. It is just the AWE enable setting that has a
> >> >> >> > discrepancy.
> >> >> >> >
> >> >> >> > Should I set the 'max server memory' to less than 14 GB if the
> >> >> >> > server
> >> >> >> > has
> >> >> >> > 16GB available? How much does the OS need?
> >> >> >> >
> >> >> >> > Thanks
> >> >> >> >
> >> >> >> > Fred
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >>
>

Configuring and using PAE on SQS Server 2000 Enterprise Edition

We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
machine with 16 GB of memory. I am trying to use more than the default 2GB of
memory for SQL Server.
I have added the /PAE switch to the boot.ini file on the server, configured
SQL Server by issuing a
sp_configure 'show advanced options', 1
RECONFIGURE
and a
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 14336
RECONFIGURE
GO
However, it looks like SQL Server is till using less than 2GB of memory when
running. I have run the sp_configure check on it's own and noticed that the
config_value for AWE enabled is 1, but that the run_value is still 0.
Could that be the problem? What do I have to do to fix this?
I know I did restart the server after adding the settings (the setting for
'show advanced options' and 'max server memory' both show the same value for
config and run_value. It is just the AWE enable setting that has a
discrepancy.
Should I set the 'max server memory' to less than 14 GB if the server has
16GB available? How much does the OS need?
Thanks
Fred
How to configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/default...274750&sd=tech
Managing AWE Memory
http://msdn.microsoft.com/library/de...erver_1fnd.asp
AMB
"fredscuba" wrote:

> We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> machine with 16 GB of memory. I am trying to use more than the default 2GB of
> memory for SQL Server.
> I have added the /PAE switch to the boot.ini file on the server, configured
> SQL Server by issuing a
> sp_configure 'show advanced options', 1
> RECONFIGURE
> and a
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 14336
> RECONFIGURE
> GO
> However, it looks like SQL Server is till using less than 2GB of memory when
> running. I have run the sp_configure check on it's own and noticed that the
> config_value for AWE enabled is 1, but that the run_value is still 0.
> Could that be the problem? What do I have to do to fix this?
> I know I did restart the server after adding the settings (the setting for
> 'show advanced options' and 'max server memory' both show the same value for
> config and run_value. It is just the AWE enable setting that has a
> discrepancy.
> Should I set the 'max server memory' to less than 14 GB if the server has
> 16GB available? How much does the OS need?
> Thanks
> Fred
|||Hi
Before you set AWE you need to set "Lock Pages In Memory" first.
How to set the "Lock Pages In Memory", Please see URL
http://msdn.microsoft.com/library/de...servp_2vqh.asp
By default SQL Seerver 2000 in Windows 2003 is disable.
Goog luck
Bogi Wu
"fredscuba" wrote:

> We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> machine with 16 GB of memory. I am trying to use more than the default 2GB of
> memory for SQL Server.
> I have added the /PAE switch to the boot.ini file on the server, configured
> SQL Server by issuing a
> sp_configure 'show advanced options', 1
> RECONFIGURE
> and a
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 14336
> RECONFIGURE
> GO
> However, it looks like SQL Server is till using less than 2GB of memory when
> running. I have run the sp_configure check on it's own and noticed that the
> config_value for AWE enabled is 1, but that the run_value is still 0.
> Could that be the problem? What do I have to do to fix this?
> I know I did restart the server after adding the settings (the setting for
> 'show advanced options' and 'max server memory' both show the same value for
> config and run_value. It is just the AWE enable setting that has a
> discrepancy.
> Should I set the 'max server memory' to less than 14 GB if the server has
> 16GB available? How much does the OS need?
> Thanks
> Fred

Configuring and using PAE on SQS Server 2000 Enterprise Edition

We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
machine with 16 GB of memory. I am trying to use more than the default 2GB o
f
memory for SQL Server.
I have added the /PAE switch to the boot.ini file on the server, configured
SQL Server by issuing a
sp_configure 'show advanced options', 1
RECONFIGURE
and a
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 14336
RECONFIGURE
GO
However, it looks like SQL Server is till using less than 2GB of memory when
running. I have run the sp_configure check on it's own and noticed that the
config_value for AWE enabled is 1, but that the run_value is still 0.
Could that be the problem? What do I have to do to fix this?
I know I did restart the server after adding the settings (the setting for
'show advanced options' and 'max server memory' both show the same value for
config and run_value. It is just the AWE enable setting that has a
discrepancy.
Should I set the 'max server memory' to less than 14 GB if the server has
16GB available? How much does the OS need?
Thanks
FredHow to configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/defaul...;274750&sd=tech
Managing AWE Memory
http://msdn.microsoft.com/library/d...>
ver_1fnd.asp
AMB
"fredscuba" wrote:

> We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> machine with 16 GB of memory. I am trying to use more than the default 2GB
of
> memory for SQL Server.
> I have added the /PAE switch to the boot.ini file on the server, configure
d
> SQL Server by issuing a
> sp_configure 'show advanced options', 1
> RECONFIGURE
> and a
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 14336
> RECONFIGURE
> GO
> However, it looks like SQL Server is till using less than 2GB of memory wh
en
> running. I have run the sp_configure check on it's own and noticed that th
e
> config_value for AWE enabled is 1, but that the run_value is still 0.
> Could that be the problem? What do I have to do to fix this?
> I know I did restart the server after adding the settings (the setting for
> 'show advanced options' and 'max server memory' both show the same value f
or
> config and run_value. It is just the AWE enable setting that has a
> discrepancy.
> Should I set the 'max server memory' to less than 14 GB if the server has
> 16GB available? How much does the OS need?
> Thanks
> Fred|||Hi
Before you set AWE you need to set "Lock Pages In Memory" first.
How to set the "Lock Pages In Memory", Please see URL
http://msdn.microsoft.com/library/d...r />
_2vqh.asp
By default SQL Seerver 2000 in Windows 2003 is disable.
Goog luck
Bogi Wu
"fredscuba" wrote:

> We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> machine with 16 GB of memory. I am trying to use more than the default 2GB
of
> memory for SQL Server.
> I have added the /PAE switch to the boot.ini file on the server, configure
d
> SQL Server by issuing a
> sp_configure 'show advanced options', 1
> RECONFIGURE
> and a
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 14336
> RECONFIGURE
> GO
> However, it looks like SQL Server is till using less than 2GB of memory wh
en
> running. I have run the sp_configure check on it's own and noticed that th
e
> config_value for AWE enabled is 1, but that the run_value is still 0.
> Could that be the problem? What do I have to do to fix this?
> I know I did restart the server after adding the settings (the setting for
> 'show advanced options' and 'max server memory' both show the same value f
or
> config and run_value. It is just the AWE enable setting that has a
> discrepancy.
> Should I set the 'max server memory' to less than 14 GB if the server has
> 16GB available? How much does the OS need?
> Thanks
> Fred