显示标签为“memory”的博文。显示所有博文
显示标签为“memory”的博文。显示所有博文

2012年3月11日星期日

Fixed memory size on MSDE

I would like to limit memory (RAM) usage for MSDE.
Since there is no Enterprise manager - is there another way how to do it?
(-> SQL command?!)
Thank You
PetrHi Petr
Please read about sp_configure in the Books Online.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Petr Stejskal" <petr.stejskal@.txn.cz> wrote in message
news:uoi1VuKnDHA.1884@.TK2MSFTNGP09.phx.gbl...
> I would like to limit memory (RAM) usage for MSDE.
> Since there is no Enterprise manager - is there another way how to do it?
> (-> SQL command?!)
> Thank You
> Petr
>

Fixed Memory = 3Gb sqlserver.exe uses 1.7Gb

Hello
We are trying to enhance the performance of our server. We recently noticed
that despite having 4Gb of RAM in the server, sqlserver.exe was only using
1.7Gb. There are 4 databases on the server, one of which is at 9Gb and in
constant use (by around 50 people).
We had thought that perhaps there was a problem with the dynamic memory
allocation so switched to fixed at 3Gb. Having restarted, the sqlserver.exe
process is still only using 1.7Gb of RAM (and still running at 100% CPU).
Surely when allocating memory in this way it should show sqlserver.exe with
the total amount of RAM. (Looking in task monitor to get the usage figure.)
Any ideas?
Thanks
DavidDavid Morgan wrote:
> Hello
> We are trying to enhance the performance of our server. We recently notic
ed
> that despite having 4Gb of RAM in the server, sqlserver.exe was only using
> 1.7Gb. There are 4 databases on the server, one of which is at 9Gb and in
> constant use (by around 50 people).
> We had thought that perhaps there was a problem with the dynamic memory
> allocation so switched to fixed at 3Gb. Having restarted, the sqlserver.e
xe
> process is still only using 1.7Gb of RAM (and still running at 100% CPU).
> Surely when allocating memory in this way it should show sqlserver.exe wit
h
> the total amount of RAM. (Looking in task monitor to get the usage figure
.)
> Any ideas?
> Thanks
> David
>
Which version of SQL? 2000 Standard will only use 2GB of RAM...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||1.7 GB indicates SQL Server uses 2GB (considering the memtoleave area - Goog
le for more info). What
version and edition of SQL Server and the OS?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Morgan" <microsoft_newsgroups.nospam@.davidmorgan.me.uk> wrote in mess
age
news:eacc4dLvGHA.1224@.TK2MSFTNGP03.phx.gbl...
> Hello
> We are trying to enhance the performance of our server. We recently notic
ed that despite having
> 4Gb of RAM in the server, sqlserver.exe was only using 1.7Gb. There are 4
databases on the
> server, one of which is at 9Gb and in constant use (by around 50 people).
> We had thought that perhaps there was a problem with the dynamic memory al
location so switched to
> fixed at 3Gb. Having restarted, the sqlserver.exe process is still only u
sing 1.7Gb of RAM (and
> still running at 100% CPU). Surely when allocating memory in this way it
should show
> sqlserver.exe with the total amount of RAM. (Looking in task monitor to g
et the usage figure.)
> Any ideas?
> Thanks
> David
>|||Thank you to both above. You are quite correct.
SQL Server 8.00.760 - SP3 (Standard Edition)
Bummer. Guess the 2005 upgrade is coming sooner than I thought.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23XKgriLvGHA.2232@.TK2MSFTNGP05.phx.gbl...
> 1.7 GB indicates SQL Server uses 2GB (considering the memtoleave area -
> Google for more info). What version and edition of SQL Server and the OS?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "David Morgan" <microsoft_newsgroups.nospam@.davidmorgan.me.uk> wrote in
> message news:eacc4dLvGHA.1224@.TK2MSFTNGP03.phx.gbl...
>

Fixed Memory = 3Gb sqlserver.exe uses 1.7Gb

Hello
We are trying to enhance the performance of our server. We recently noticed
that despite having 4Gb of RAM in the server, sqlserver.exe was only using
1.7Gb. There are 4 databases on the server, one of which is at 9Gb and in
constant use (by around 50 people).
We had thought that perhaps there was a problem with the dynamic memory
allocation so switched to fixed at 3Gb. Having restarted, the sqlserver.exe
process is still only using 1.7Gb of RAM (and still running at 100% CPU).
Surely when allocating memory in this way it should show sqlserver.exe with
the total amount of RAM. (Looking in task monitor to get the usage figure.)
Any ideas?
Thanks
DavidDavid Morgan wrote:
> Hello
> We are trying to enhance the performance of our server. We recently noticed
> that despite having 4Gb of RAM in the server, sqlserver.exe was only using
> 1.7Gb. There are 4 databases on the server, one of which is at 9Gb and in
> constant use (by around 50 people).
> We had thought that perhaps there was a problem with the dynamic memory
> allocation so switched to fixed at 3Gb. Having restarted, the sqlserver.exe
> process is still only using 1.7Gb of RAM (and still running at 100% CPU).
> Surely when allocating memory in this way it should show sqlserver.exe with
> the total amount of RAM. (Looking in task monitor to get the usage figure.)
> Any ideas?
> Thanks
> David
>
Which version of SQL? 2000 Standard will only use 2GB of RAM...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||1.7 GB indicates SQL Server uses 2GB (considering the memtoleave area - Google for more info). What
version and edition of SQL Server and the OS?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Morgan" <microsoft_newsgroups.nospam@.davidmorgan.me.uk> wrote in message
news:eacc4dLvGHA.1224@.TK2MSFTNGP03.phx.gbl...
> Hello
> We are trying to enhance the performance of our server. We recently noticed that despite having
> 4Gb of RAM in the server, sqlserver.exe was only using 1.7Gb. There are 4 databases on the
> server, one of which is at 9Gb and in constant use (by around 50 people).
> We had thought that perhaps there was a problem with the dynamic memory allocation so switched to
> fixed at 3Gb. Having restarted, the sqlserver.exe process is still only using 1.7Gb of RAM (and
> still running at 100% CPU). Surely when allocating memory in this way it should show
> sqlserver.exe with the total amount of RAM. (Looking in task monitor to get the usage figure.)
> Any ideas?
> Thanks
> David
>|||Thank you to both above. You are quite correct.
SQL Server 8.00.760 - SP3 (Standard Edition)
Bummer. Guess the 2005 upgrade is coming sooner than I thought.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23XKgriLvGHA.2232@.TK2MSFTNGP05.phx.gbl...
> 1.7 GB indicates SQL Server uses 2GB (considering the memtoleave area -
> Google for more info). What version and edition of SQL Server and the OS?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "David Morgan" <microsoft_newsgroups.nospam@.davidmorgan.me.uk> wrote in
> message news:eacc4dLvGHA.1224@.TK2MSFTNGP03.phx.gbl...
>> Hello
>> We are trying to enhance the performance of our server. We recently
>> noticed that despite having 4Gb of RAM in the server, sqlserver.exe was
>> only using 1.7Gb. There are 4 databases on the server, one of which is
>> at 9Gb and in constant use (by around 50 people).
>> We had thought that perhaps there was a problem with the dynamic memory
>> allocation so switched to fixed at 3Gb. Having restarted, the
>> sqlserver.exe process is still only using 1.7Gb of RAM (and still running
>> at 100% CPU). Surely when allocating memory in this way it should show
>> sqlserver.exe with the total amount of RAM. (Looking in task monitor to
>> get the usage figure.)
>> Any ideas?
>> Thanks
>> David
>

FIX: Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).


ADDITIONAL INFORMATION:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

FIX: AWE and SQL Server 2000 SP4 (899761)

FIX: Not all memory is available when AWE is enabled on a computer that is
running a 32-bit version of SQL Server 2000 SP4 (899761)
http://www.microsoft.com/downloads/details.aspx?familyid=7c407047-3f1f-48b8-9e4c-dc32875e1961&displaylang=en
This issue only impacts customers with more than 2GB of memory (available
only with the Enterprise, Developer and Evaluation editions) where AWE has
been enabled and more than half of the total system memory is being
allocated to a single SQL Server instance.
Customers with this configuration should apply this hotfix after upgrading
to SQL Server 2000 Service Pack 4.
KB 899761 http://support.microsoft.com/default.aspx?scid=KB;en-us;899761
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.orgThanks Jasper.
Is there any central resouce for sql server hot fixes?
Paul
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:%23VwCMVMdFHA.412@.tk2msftngp13.phx.gbl...
> FIX: Not all memory is available when AWE is enabled on a computer that is
> running a 32-bit version of SQL Server 2000 SP4 (899761)
> http://www.microsoft.com/downloads/details.aspx?familyid=7c407047-3f1f-48b8-9e4c-dc32875e1961&displaylang=en
> This issue only impacts customers with more than 2GB of memory (available
> only with the Enterprise, Developer and Evaluation editions) where AWE has
> been enabled and more than half of the total system memory is being
> allocated to a single SQL Server instance.
> Customers with this configuration should apply this hotfix after upgrading
> to SQL Server 2000 Service Pack 4.
> KB 899761 http://support.microsoft.com/default.aspx?scid=KB;en-us;899761
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>|||Hi
For a list, you can find it here.
http://www.aspfaq.com/show.asp?id=2160
For some reason, it has not been updated to the latest fixes yet.
Cheers
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Paul Cahill" <nospam@.hotmail.com> wrote in message
news:Oyu$31QdFHA.1684@.TK2MSFTNGP09.phx.gbl...
> Thanks Jasper.
> Is there any central resouce for sql server hot fixes?
> Paul
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
> news:%23VwCMVMdFHA.412@.tk2msftngp13.phx.gbl...
>> FIX: Not all memory is available when AWE is enabled on a computer that
>> is running a 32-bit version of SQL Server 2000 SP4 (899761)
>> http://www.microsoft.com/downloads/details.aspx?familyid=7c407047-3f1f-48b8-9e4c-dc32875e1961&displaylang=en
>> This issue only impacts customers with more than 2GB of memory (available
>> only with the Enterprise, Developer and Evaluation editions) where AWE
>> has been enabled and more than half of the total system memory is being
>> allocated to a single SQL Server instance.
>> Customers with this configuration should apply this hotfix after
>> upgrading to SQL Server 2000 Service Pack 4.
>> KB 899761 http://support.microsoft.com/default.aspx?scid=KB;en-us;899761
>> --
>> HTH
>> Jasper Smith (SQL Server MVP)
>> http://www.sqldbatips.com
>> I support PASS - the definitive, global
>> community for SQL Server professionals -
>> http://www.sqlpass.org
>>
>|||Thanks Mike.
Paul
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euYYVbRdFHA.1384@.TK2MSFTNGP09.phx.gbl...
> Hi
> For a list, you can find it here.
> http://www.aspfaq.com/show.asp?id=2160
> For some reason, it has not been updated to the latest fixes yet.
> Cheers
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Paul Cahill" <nospam@.hotmail.com> wrote in message
> news:Oyu$31QdFHA.1684@.TK2MSFTNGP09.phx.gbl...
>> Thanks Jasper.
>> Is there any central resouce for sql server hot fixes?
>> Paul
>> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
>> news:%23VwCMVMdFHA.412@.tk2msftngp13.phx.gbl...
>> FIX: Not all memory is available when AWE is enabled on a computer that
>> is running a 32-bit version of SQL Server 2000 SP4 (899761)
>> http://www.microsoft.com/downloads/details.aspx?familyid=7c407047-3f1f-48b8-9e4c-dc32875e1961&displaylang=en
>> This issue only impacts customers with more than 2GB of memory
>> (available only with the Enterprise, Developer and Evaluation editions)
>> where AWE has been enabled and more than half of the total system memory
>> is being allocated to a single SQL Server instance.
>> Customers with this configuration should apply this hotfix after
>> upgrading to SQL Server 2000 Service Pack 4.
>> KB 899761 http://support.microsoft.com/default.aspx?scid=KB;en-us;899761
>> --
>> HTH
>> Jasper Smith (SQL Server MVP)
>> http://www.sqldbatips.com
>> I support PASS - the definitive, global
>> community for SQL Server professionals -
>> http://www.sqlpass.org
>>
>>
>|||Mike Epprecht (SQL MVP) wrote:
> For a list, you can find it here:
> http://www.aspfaq.com/show.asp=AD?id=3D2160
> For some reason, it has not been updated to the latest fixes yet.
An updated list, containing only the build numbers for SQL Server 2000,
can be found at:
http://www.aspfaq.com/sql2000builds.asp
Razvan