merge input output selection dialog is hanging

Hello

I'm trying to use the Merge component. When i attach a datasource to the the component, the Select Input/Output dialog box should popup.. It does, but VS.NET is hanging and i can only shutdown the procesess...

Any idea how i should solve this? how can i re-register this component?

ps. sql 2005 sp1 is installed.

Thanks
Marco

I am experiencing the same problem.

I have SQL Server 2005 SP1 and Visual Studio 2005 SP1.

I thought I had worked around this in the past by adding the components to the designer in a different order, but that does not seem to make a difference any longer.

|||

If this is something that happened very randomly and could be worked around by just closing/killing the project and open it again, then it's a known issue, the fix will be in SP2. However if you bumped into a constant repro of this, then likely it is something new, in that case please file a bug at our beta place with a brief description of that you got, we will get back to you soon.

Thanks

wenyang

|||

Beta Place closed some time ago.

You can of course raise a PSS support case for full paid support, or just log the bug/request online at MS Connect, effectively the replacement for Beta Place - http://connect.microsoft.com

merge input output selection dialog is hanging

Hello

I'm trying to use the Merge component. When i attach a datasource to the the component, the Select Input/Output dialog box should popup.. It does, but VS.NET is hanging and i can only shutdown the procesess...

Any idea how i should solve this? how can i re-register this component?

ps. sql 2005 sp1 is installed.

Thanks
Marco

I am experiencing the same problem.

I have SQL Server 2005 SP1 and Visual Studio 2005 SP1.

I thought I had worked around this in the past by adding the components to the designer in a different order, but that does not seem to make a difference any longer.

|||

If this is something that happened very randomly and could be worked around by just closing/killing the project and open it again, then it's a known issue, the fix will be in SP2. However if you bumped into a constant repro of this, then likely it is something new, in that case please file a bug at our beta place with a brief description of that you got, we will get back to you soon.

Thanks

wenyang

|||

Beta Place closed some time ago.

You can of course raise a PSS support case for full paid support, or just log the bug/request online at MS Connect, effectively the replacement for Beta Place - http://connect.microsoft.com

Memory Usage, SBS 2000 & SQL 2000

Hello,
I am noticing that memory on our SQL 2000 (on an SBS 2000 box, a dual
processor box with 2GB of RAM) continues to grow over a few day period. I
have double-checked to make sure that SP3a is installed and am trying to
double-check to make sure that MDAC 2.71 is installed (correctly). First,
what's the best way to assure that each of these are installed without
errors or issues? Second, if those are then, what else could be causing the
memory to continue to grow over time?
I know that I can limit the SQL configuration to 1GB (for example) but
that's not really the key problem here. As I write this the memory has
grown from 287MB to 314MB and by the weekend will likely be over 1GB thus
forcing the box to be using 2.2 - 2.8 GB of RAM when it only has 2GB's.
Adding RAM is obviously an option but that looks like it's only going to be
a band-aid to the problem because it will just continue to eat the
additional memory unless I lock the SQL RAM usage however I feel the key
issue to determine why the RAM is continuing to grow day-by-day.
Thanks in advance!
ChrisI expect that the behavior you are seeing is normal. There is no cause for
alarm.
SQL Server 2000 Standard Edition is able to use up to 2GB of RAM. It will
not use more than that. SQL Server stores data and query plans in RAM. As
you use SQL Server it caches data and query plans to memory.
If SQL Server is the only thing running on the box you might want to leave
it as is. If you have other server apps running and consuming resources you
might want to limit memory usage to something that allows your other apps to
have enough memory. The other option, of course is to leave SQL Server
as-is and add additional memory for the other apps that you may have on this
server.
By the way, how big are your databases? If all of your user databases are
"small" (they all add up to 1GB or LESS) you should not see SQL Server
consume much over 1GB.
Bottom line: don't worry unless your server is RAM hungry. If it is RAM
hungry add some or limit SQL Server to "enough" memory.
--
Keith
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:OOfxH9alEHA.3968@.TK2MSFTNGP11.phx.gbl...
> Hello,
>
> I am noticing that memory on our SQL 2000 (on an SBS 2000 box, a dual
> processor box with 2GB of RAM) continues to grow over a few day period. I
> have double-checked to make sure that SP3a is installed and am trying to
> double-check to make sure that MDAC 2.71 is installed (correctly). First,
> what's the best way to assure that each of these are installed without
> errors or issues? Second, if those are then, what else could be causing
the
> memory to continue to grow over time?
>
> I know that I can limit the SQL configuration to 1GB (for example) but
> that's not really the key problem here. As I write this the memory has
> grown from 287MB to 314MB and by the weekend will likely be over 1GB thus
> forcing the box to be using 2.2 - 2.8 GB of RAM when it only has 2GB's.
> Adding RAM is obviously an option but that looks like it's only going to
be
> a band-aid to the problem because it will just continue to eat the
> additional memory unless I lock the SQL RAM usage however I feel the key
> issue to determine why the RAM is continuing to grow day-by-day.
>
> Thanks in advance!
>
> Chris
>|||Thank you...
The database(s) right now are just about a 1/2GB and I've noticed the SQL
box hitting about 1GB of RAM. I guess I will limit it for the moment so
that other apps don't eatup too much or go past the physical limit.
Chris
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:e1VmGYblEHA.2968@.TK2MSFTNGP14.phx.gbl...
>I expect that the behavior you are seeing is normal. There is no cause for
> alarm.
> SQL Server 2000 Standard Edition is able to use up to 2GB of RAM. It will
> not use more than that. SQL Server stores data and query plans in RAM.
> As
> you use SQL Server it caches data and query plans to memory.
> If SQL Server is the only thing running on the box you might want to leave
> it as is. If you have other server apps running and consuming resources
> you
> might want to limit memory usage to something that allows your other apps
> to
> have enough memory. The other option, of course is to leave SQL Server
> as-is and add additional memory for the other apps that you may have on
> this
> server.
> By the way, how big are your databases? If all of your user databases are
> "small" (they all add up to 1GB or LESS) you should not see SQL Server
> consume much over 1GB.
> Bottom line: don't worry unless your server is RAM hungry. If it is RAM
> hungry add some or limit SQL Server to "enough" memory.
> --
> Keith
>
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:OOfxH9alEHA.3968@.TK2MSFTNGP11.phx.gbl...
>> Hello,
>>
>> I am noticing that memory on our SQL 2000 (on an SBS 2000 box, a dual
>> processor box with 2GB of RAM) continues to grow over a few day period.
>> I
>> have double-checked to make sure that SP3a is installed and am trying to
>> double-check to make sure that MDAC 2.71 is installed (correctly).
>> First,
>> what's the best way to assure that each of these are installed without
>> errors or issues? Second, if those are then, what else could be causing
> the
>> memory to continue to grow over time?
>>
>> I know that I can limit the SQL configuration to 1GB (for example) but
>> that's not really the key problem here. As I write this the memory has
>> grown from 287MB to 314MB and by the weekend will likely be over 1GB thus
>> forcing the box to be using 2.2 - 2.8 GB of RAM when it only has 2GB's.
>> Adding RAM is obviously an option but that looks like it's only going to
> be
>> a band-aid to the problem because it will just continue to eat the
>> additional memory unless I lock the SQL RAM usage however I feel the key
>> issue to determine why the RAM is continuing to grow day-by-day.
>>
>> Thanks in advance!
>>
>> Chris
>>
>

Memory Usage, SBS 2000 & SQL 2000

Hello,
I am noticing that memory on our SQL 2000 (on an SBS 2000 box, a dual
processor box with 2GB of RAM) continues to grow over a few day period. I
have double-checked to make sure that SP3a is installed and am trying to
double-check to make sure that MDAC 2.71 is installed (correctly). First,
what's the best way to assure that each of these are installed without
errors or issues? Second, if those are then, what else could be causing the
memory to continue to grow over time?
I know that I can limit the SQL configuration to 1GB (for example) but
that's not really the key problem here. As I write this the memory has
grown from 287MB to 314MB and by the weekend will likely be over 1GB thus
forcing the box to be using 2.2 - 2.8 GB of RAM when it only has 2GB's.
Adding RAM is obviously an option but that looks like it's only going to be
a band-aid to the problem because it will just continue to eat the
additional memory unless I lock the SQL RAM usage however I feel the key
issue to determine why the RAM is continuing to grow day-by-day.
Thanks in advance!
Chris
I expect that the behavior you are seeing is normal. There is no cause for
alarm.
SQL Server 2000 Standard Edition is able to use up to 2GB of RAM. It will
not use more than that. SQL Server stores data and query plans in RAM. As
you use SQL Server it caches data and query plans to memory.
If SQL Server is the only thing running on the box you might want to leave
it as is. If you have other server apps running and consuming resources you
might want to limit memory usage to something that allows your other apps to
have enough memory. The other option, of course is to leave SQL Server
as-is and add additional memory for the other apps that you may have on this
server.
By the way, how big are your databases? If all of your user databases are
"small" (they all add up to 1GB or LESS) you should not see SQL Server
consume much over 1GB.
Bottom line: don't worry unless your server is RAM hungry. If it is RAM
hungry add some or limit SQL Server to "enough" memory.
Keith
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:OOfxH9alEHA.3968@.TK2MSFTNGP11.phx.gbl...
> Hello,
>
> I am noticing that memory on our SQL 2000 (on an SBS 2000 box, a dual
> processor box with 2GB of RAM) continues to grow over a few day period. I
> have double-checked to make sure that SP3a is installed and am trying to
> double-check to make sure that MDAC 2.71 is installed (correctly). First,
> what's the best way to assure that each of these are installed without
> errors or issues? Second, if those are then, what else could be causing
the
> memory to continue to grow over time?
>
> I know that I can limit the SQL configuration to 1GB (for example) but
> that's not really the key problem here. As I write this the memory has
> grown from 287MB to 314MB and by the weekend will likely be over 1GB thus
> forcing the box to be using 2.2 - 2.8 GB of RAM when it only has 2GB's.
> Adding RAM is obviously an option but that looks like it's only going to
be
> a band-aid to the problem because it will just continue to eat the
> additional memory unless I lock the SQL RAM usage however I feel the key
> issue to determine why the RAM is continuing to grow day-by-day.
>
> Thanks in advance!
>
> Chris
>
|||Thank you...
The database(s) right now are just about a 1/2GB and I've noticed the SQL
box hitting about 1GB of RAM. I guess I will limit it for the moment so
that other apps don't eatup too much or go past the physical limit.
Chris
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:e1VmGYblEHA.2968@.TK2MSFTNGP14.phx.gbl...
>I expect that the behavior you are seeing is normal. There is no cause for
> alarm.
> SQL Server 2000 Standard Edition is able to use up to 2GB of RAM. It will
> not use more than that. SQL Server stores data and query plans in RAM.
> As
> you use SQL Server it caches data and query plans to memory.
> If SQL Server is the only thing running on the box you might want to leave
> it as is. If you have other server apps running and consuming resources
> you
> might want to limit memory usage to something that allows your other apps
> to
> have enough memory. The other option, of course is to leave SQL Server
> as-is and add additional memory for the other apps that you may have on
> this
> server.
> By the way, how big are your databases? If all of your user databases are
> "small" (they all add up to 1GB or LESS) you should not see SQL Server
> consume much over 1GB.
> Bottom line: don't worry unless your server is RAM hungry. If it is RAM
> hungry add some or limit SQL Server to "enough" memory.
> --
> Keith
>
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:OOfxH9alEHA.3968@.TK2MSFTNGP11.phx.gbl...
> the
> be
>

Memory usage +4gig of ram

Question:
Is it true that sql 2k will not recognize more than 4 gigz of ram? If this
is true and I have 6 gigz of ram in the box. Will sql only seethe first 4
gigz of ram and then the other two left will be used by whatever else may be
running on the box?
Thanks in Advance,
Robert Tafaro
rtafaro@.hibernia.comHi,
Chk this link...
http://www.sqlservercentral.com/faq/viewfaqanswer.asp?faqid=202
Cheers,
Shiva.
Chennai.
"Robert Tafaro" <rtafaro@.nospam.hibernia.com> wrote in message
news:3f0ac9c8$1@.dnews1.hiberniabank.com...
> Question:
> Is it true that sql 2k will not recognize more than 4 gigz of ram? If
this
> is true and I have 6 gigz of ram in the box. Will sql only seethe first 4
> gigz of ram and then the other two left will be used by whatever else may
be
> running on the box?
> Thanks in Advance,
> Robert Tafaro
> rtafaro@.hibernia.com
>

memory usage

Hello,
I have a sql 2000 box that has roughly 15 datbases. How do i determine how
much memory/cpu a particular db is using?
thanks!
Calvin
DBs don't use CPU, client connections do. You can correlate CPU use for
current connections by doing a little extrapolation from the
master.dbo.sysprocesses table. That table lists all current connections
and each row specifies which DB is currently being used (dbid) by the
connection and how much CPU time that connection has consumed. (Take
this with a grain of salt though because a SPID can change DB simply by
running a USE statement, so there's no guarantee the SPID has been using
the same DB its whole life.) This is a cumulative value so if a client
has been connected to the server by the same SPID for a long time, the
cumulative CPU will be high compared to a relatively new SPID. Just
bear that in mind when extrapolating - you might do well to divide the
CPU figure by the number of hours, "datediff(hh, login_time,
getdate())", (or minutes or days or...) the SPID has been alive for to
get an hourly average CPU - slightly more helpful.
As for memory, it's very hard to tell what percentage of memory is
attributable to each DB. SQL Server simply caches data pages
(regardless of which DB they belong to) when they're accessed. The
execution plans stored in the procedure cache can involve objects in
many databases so you can't really attribute them to any particular DB.
You can see a little bit of information about the buffer cache by running:
DBCC MEMUSAGE
This will show you a little info about the top 20 objects in terms of
cache use. It lists the dbid (what you're interested in), the objectid
& indexid from that DB (this will be the id of the associated
table/index) and the number of buffers (8K pages?) being used by that
object in the buffer cache. NB/ Microsoft recommend not using DBCC
MEMUSAGE and using the related perfmon counters instead (see
http://msdn.microsoft.com/library/de...kcomp_992x.asp)
but I find DBCC MEMUSAGE still slightly helpful, although I suppose you
could get the perfmon data you're after (that replaces DBCC MEMUSAGE)
from querying the master.dbo.sysperfinfo table and correlating that data.
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Calvin Do wrote:

>Hello,
>
>I have a sql 2000 box that has roughly 15 datbases. How do i determine how
>much memory/cpu a particular db is using?
>
>thanks!
>Calvin
>
>
|||thank you for the email Mike, i will review...
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message news:%23bzeX6gHFHA.720@.TK2MSFTNGP10.phx.gbl...
DBs don't use CPU, client connections do. You can correlate CPU use for current connections by doing a little extrapolation from the master.dbo.sysprocesses table. That table lists all current connections and each row specifies which DB is currently being used (dbid) by the connection and how much CPU time that connection has consumed. (Take this with a grain of salt though because a SPID can change DB simply by running a USE statement, so there's no guarantee the SPID has been using the same DB its whole life.) This is a cumulative value so if a client has been connected to the server by the same SPID for a long time, the cumulative CPU will be high compared to a relatively new SPID. Just bear that in mind when extrapolating - you might do well to divide the CPU figure by the number of hours, "datediff(hh, login_time, getdate())", (or minutes or days or...) the SPID has been alive for to get an hourly average CPU - slightly more helpful.
As for memory, it's very hard to tell what percentage of memory is attributable to each DB. SQL Server simply caches data pages (regardless of which DB they belong to) when they're accessed. The execution plans stored in the procedure cache can involve objects in many databases so you can't really attribute them to any particular DB. You can see a little bit of information about the buffer cache by running:
DBCC MEMUSAGE
This will show you a little info about the top 20 objects in terms of cache use. It lists the dbid (what you're interested in), the objectid & indexid from that DB (this will be the id of the associated table/index) and the number of buffers (8K pages?) being used by that object in the buffer cache. NB/ Microsoft recommend not using DBCC MEMUSAGE and using the related perfmon counters instead (see http://msdn.microsoft.com/library/de...kcomp_992x.asp) but I find DBCC MEMUSAGE still slightly helpful, although I suppose you could get the perfmon data you're after (that replaces DBCC MEMUSAGE) from querying the master.dbo.sysperfinfo table and correlating that data.
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W http://www.mallesons.com
Calvin Do wrote:
Hello,
I have a sql 2000 box that has roughly 15 datbases. How do i determine how
much memory/cpu a particular db is using?
thanks!
Calvin

Memory Settings

Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with 8GB
RAM on the box. 3 questions for the experts:
(1) Firstly, my understanding is that only 4GB can be used by windows - is
this correct?
(2) do we still have to change boot.ini file or is this not needed with
windows 2003?
(3) do we need to make changes to sp_configure - the max server memory will
need changing but how about the AWE setting?
Thanks.Jack
- Enabling Memory Support for Over 4GB of Physical Memory
http://msdn2.microsoft.com/en-us/library/ms179301.aspx
"Jack" <jack@.Nospam.com> wrote in message
news:%2367lbLjDHHA.3492@.TK2MSFTNGP02.phx.gbl...
> Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with
> 8GB RAM on the box. 3 questions for the experts:
> (1) Firstly, my understanding is that only 4GB can be used by windows - is
> this correct?
> (2) do we still have to change boot.ini file or is this not needed with
> windows 2003?
> (3) do we need to make changes to sp_configure - the max server memory
> will need changing but how about the AWE setting?
> Thanks.
>|||Also
http://blogs.msdn.com/slavao/
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:upLFsNjDHHA.4404@.TK2MSFTNGP06.phx.gbl...
> Jack
> - Enabling Memory Support for Over 4GB of Physical Memory
> http://msdn2.microsoft.com/en-us/library/ms179301.aspx
>
>
> "Jack" <jack@.Nospam.com> wrote in message
> news:%2367lbLjDHHA.3492@.TK2MSFTNGP02.phx.gbl...
>> Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with
>> 8GB RAM on the box. 3 questions for the experts:
>> (1) Firstly, my understanding is that only 4GB can be used by windows -
>> is this correct?
>> (2) do we still have to change boot.ini file or is this not needed with
>> windows 2003?
>> (3) do we need to make changes to sp_configure - the max server memory
>> will need changing but how about the AWE setting?
>> Thanks.
>|||Hi Jack,
I just started playing with AWE my self and this is what I found so far.
SQL Server 2005 can make use of the extra memory with modifying the boot.ini.
Make sure that the account that the sql service is running as is part of the
lock pages in memory group policy, AWE is enabled in SQL server, and
configure max memory in SQL server to be at most 7GB, leaving 1 GB for the
OS. If you go to 16 GB of RAM then leave 2 GB free for the OS. The max that
the OS can use depends on the version of the OS that you are running I think.
--
MG
"Jack" wrote:
> Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with 8GB
> RAM on the box. 3 questions for the experts:
> (1) Firstly, my understanding is that only 4GB can be used by windows - is
> this correct?
> (2) do we still have to change boot.ini file or is this not needed with
> windows 2003?
> (3) do we need to make changes to sp_configure - the max server memory will
> need changing but how about the AWE setting?
> Thanks.
>
>

Memory Settings

Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with 8GB
RAM on the box. 3 questions for the experts:
(1) Firstly, my understanding is that only 4GB can be used by windows - is
this correct?
(2) do we still have to change boot.ini file or is this not needed with
windows 2003?
(3) do we need to make changes to sp_configure - the max server memory will
need changing but how about the AWE setting?
Thanks.
Jack
- Enabling Memory Support for Over 4GB of Physical Memory
http://msdn2.microsoft.com/en-us/library/ms179301.aspx
"Jack" <jack@.Nospam.com> wrote in message
news:%2367lbLjDHHA.3492@.TK2MSFTNGP02.phx.gbl...
> Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with
> 8GB RAM on the box. 3 questions for the experts:
> (1) Firstly, my understanding is that only 4GB can be used by windows - is
> this correct?
> (2) do we still have to change boot.ini file or is this not needed with
> windows 2003?
> (3) do we need to make changes to sp_configure - the max server memory
> will need changing but how about the AWE setting?
> Thanks.
>
|||Also
http://blogs.msdn.com/slavao/
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:upLFsNjDHHA.4404@.TK2MSFTNGP06.phx.gbl...
> Jack
> - Enabling Memory Support for Over 4GB of Physical Memory
> http://msdn2.microsoft.com/en-us/library/ms179301.aspx
>
>
> "Jack" <jack@.Nospam.com> wrote in message
> news:%2367lbLjDHHA.3492@.TK2MSFTNGP02.phx.gbl...
>
|||Hi Jack,
I just started playing with AWE my self and this is what I found so far.
SQL Server 2005 can make use of the extra memory with modifying the boot.ini.
Make sure that the account that the sql service is running as is part of the
lock pages in memory group policy, AWE is enabled in SQL server, and
configure max memory in SQL server to be at most 7GB, leaving 1 GB for the
OS. If you go to 16 GB of RAM then leave 2 GB free for the OS. The max that
the OS can use depends on the version of the OS that you are running I think.
MG
"Jack" wrote:

> Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with 8GB
> RAM on the box. 3 questions for the experts:
> (1) Firstly, my understanding is that only 4GB can be used by windows - is
> this correct?
> (2) do we still have to change boot.ini file or is this not needed with
> windows 2003?
> (3) do we need to make changes to sp_configure - the max server memory will
> need changing but how about the AWE setting?
> Thanks.
>
>

Memory Settings

Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with 8GB
RAM on the box. 3 questions for the experts:
(1) Firstly, my understanding is that only 4GB can be used by windows - is
this correct?
(2) do we still have to change boot.ini file or is this not needed with
windows 2003?
(3) do we need to make changes to sp_configure - the max server memory will
need changing but how about the AWE setting?
Thanks.Jack
- Enabling Memory Support for Over 4GB of Physical Memory
http://msdn2.microsoft.com/en-us/library/ms179301.aspx
"Jack" <jack@.Nospam.com> wrote in message
news:%2367lbLjDHHA.3492@.TK2MSFTNGP02.phx.gbl...
> Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with
> 8GB RAM on the box. 3 questions for the experts:
> (1) Firstly, my understanding is that only 4GB can be used by windows - is
> this correct?
> (2) do we still have to change boot.ini file or is this not needed with
> windows 2003?
> (3) do we need to make changes to sp_configure - the max server memory
> will need changing but how about the AWE setting?
> Thanks.
>|||Also
http://blogs.msdn.com/slavao/
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:upLFsNjDHHA.4404@.TK2MSFTNGP06.phx.gbl...
> Jack
> - Enabling Memory Support for Over 4GB of Physical Memory
> http://msdn2.microsoft.com/en-us/library/ms179301.aspx
>
>
> "Jack" <jack@.Nospam.com> wrote in message
> news:%2367lbLjDHHA.3492@.TK2MSFTNGP02.phx.gbl...
>|||Hi Jack,
I just started playing with AWE my self and this is what I found so far.
SQL Server 2005 can make use of the extra memory with modifying the boot.ini
.
Make sure that the account that the sql service is running as is part of the
lock pages in memory group policy, AWE is enabled in SQL server, and
configure max memory in SQL server to be at most 7GB, leaving 1 GB for the
OS. If you go to 16 GB of RAM then leave 2 GB free for the OS. The max tha
t
the OS can use depends on the version of the OS that you are running I think
.
--
MG
"Jack" wrote:

> Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with 8G
B
> RAM on the box. 3 questions for the experts:
> (1) Firstly, my understanding is that only 4GB can be used by windows - is
> this correct?
> (2) do we still have to change boot.ini file or is this not needed with
> windows 2003?
> (3) do we need to make changes to sp_configure - the max server memory wil
l
> need changing but how about the AWE setting?
> Thanks.
>
>

Memory pb

Hie,
When i restrict the memory of the db in property dialog box, the process sqlserv.exe increase his memry above this limit why ?Have you enabled AWE? That pretty much circumvents the normal Windows process management, mostly because that is exactly what it is supposed to do!

Even if you haven't enabled AWE, the server responds to its environment. If large blocks of RAM are not being used, then the OS can elect to dynamically ease the restrictions on an application that is memory starved (which happens fast with a busy SQL Server).

-PatP