Showing posts with label memory. Show all posts
Showing posts with label memory. Show all posts

Friday, March 9, 2012

Help-Can I use 4 GB memory by SQL Server2000?

There is a Server with 4G Memory. I installed a SQL Server 2000 standard
version on it.
I heard that SQLServer2000 could use only up to 2GB memory. Is it true?
How can I use those 4GB memory? I can not upgrade to SQL Server 2005 or
other version because i don't want to take this risk.
Thank you very much.
True. Standard edition is limited to 2GB
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Damon" <Damon@.china.com> wrote in message
news:3YChh.69507$YV4.69275@.edtnps89...
> There is a Server with 4G Memory. I installed a SQL Server 2000 standard
> version on it.
> I heard that SQLServer2000 could use only up to 2GB memory. Is it true?
> How can I use those 4GB memory? I can not upgrade to SQL Server 2005 or
> other version because i don't want to take this risk.
> Thank you very much.
>
|||Thank you Kevin.
Is there any solution to use 4 GB memory by sql2000?
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:uL6CwcuIHHA.4760@.TK2MSFTNGP03.phx.gbl...
> True. Standard edition is limited to 2GB
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Damon" <Damon@.china.com> wrote in message
> news:3YChh.69507$YV4.69275@.edtnps89...
>
|||Upgrade to Enterprise Edition.
Configuration -Maximum Capacity Specifications
2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Damon" <Damon@.china.com> wrote in message
news:cuDhh.69523$YV4.18832@.edtnps89...
> Thank you Kevin.
> Is there any solution to use 4 GB memory by sql2000?
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:uL6CwcuIHHA.4760@.TK2MSFTNGP03.phx.gbl...
>
|||Damon (Damon@.china.com) writes:
> Thank you Kevin.
> Is there any solution to use 4 GB memory by sql2000?
Upgrade to Enterprise Edition of SQL 2000.
Which is quite more expensive than moving to SQL 2005 Standard, I believe.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|||"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns989DEE520DF4DYazorman@.127.0.0.1...
> Damon (Damon@.china.com) writes:
> Upgrade to Enterprise Edition of SQL 2000.
> Which is quite more expensive than moving to SQL 2005 Standard, I believe.
Would a "Named Instance" on SQL 2000 Standard be able to use most of the
remaining half of the 4GB? When I expirimented with named instances back in
2001 - and decided not to use them in a production environment - I only had
2GB in the server.
Even if possible I'm not sure this would be a good solution, just wondering
what the behavior is.

> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|||The OS will require some memory I leave 512 MB as a minimum. The remaining
memory could be divided between the various instances of SQL Server,
equally, or one instance getting 2GB and the other only 1.5GB, etc.
You would need to use the Server setting for MAX Server Memory on each
instance.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Russ Rose" <russrose@.hotmail.com> wrote in message
news:5_-dnWp8N8-s1BrYnZ2dnUVZ_u63nZ2d@.comcast.com...
> "Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
> news:Xns989DEE520DF4DYazorman@.127.0.0.1...
> Would a "Named Instance" on SQL 2000 Standard be able to use most of the
> remaining half of the 4GB? When I expirimented with named instances back
> in 2001 - and decided not to use them in a production environment - I only
> had 2GB in the server.
> Even if possible I'm not sure this would be a good solution, just
> wondering what the behavior is.
>
>
|||"Russ Rose" <russrose@.hotmail.com> wrote in message
news:5_-dnWp8N8-s1BrYnZ2dnUVZ_u63nZ2d@.comcast.com...
> "Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
> news:Xns989DEE520DF4DYazorman@.127.0.0.1...
> Would a "Named Instance" on SQL 2000 Standard be able to use most of the
> remaining half of the 4GB? When I expirimented with named instances back
> in 2001 - and decided not to use them in a production environment - I only
> had 2GB in the server.
Note for say a website, as I recall, you need a CPU license for each
physical CPU in the machine for each instance (in Standard).
However, this probably won't necessarily help. It depends on the OS.
If you're running Windows 2000 Standard, you're limited to 4 GB of physical
RAM anyway.
Now, 2 gig of physical RAM can be given to a process (3 gig if compiled with
the right options, but that raises other issues here.)
So, if you have 5 gig of physical RAM and an OS that can address all of
that, in theory this could support 2 processes each using 2 gig of physical
RAM with 1 gig reserved for the OS.
If you have less memory, obviously this won't work as well.
Quite honestly, I think your best bet if you really need the memory (and
while I'm always a fan of more memory, sometimes it's just not worth it) is
to move to SQL 2005.

> Even if possible I'm not sure this would be a good solution, just
> wondering what the behavior is.
>
>
|||Thank you every body!
Now, I am going to move to SQL 2005.
Merry Christmas.
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:MdRhh.917$yx6.284@.newsread2.news.pas.earthlin k.net...
> "Russ Rose" <russrose@.hotmail.com> wrote in message
> news:5_-dnWp8N8-s1BrYnZ2dnUVZ_u63nZ2d@.comcast.com...
>
> Note for say a website, as I recall, you need a CPU license for each
> physical CPU in the machine for each instance (in Standard).
> However, this probably won't necessarily help. It depends on the OS.
> If you're running Windows 2000 Standard, you're limited to 4 GB of
> physical RAM anyway.
> Now, 2 gig of physical RAM can be given to a process (3 gig if compiled
> with the right options, but that raises other issues here.)
> So, if you have 5 gig of physical RAM and an OS that can address all of
> that, in theory this could support 2 processes each using 2 gig of
> physical RAM with 1 gig reserved for the OS.
> If you have less memory, obviously this won't work as well.
> Quite honestly, I think your best bet if you really need the memory (and
> while I'm always a fan of more memory, sometimes it's just not worth it)
> is to move to SQL 2005.
>
>

Help-Can I use 4 GB memory by SQL Server2000?

There is a Server with 4G Memory. I installed a SQL Server 2000 standard
version on it.
I heard that SQLServer2000 could use only up to 2GB memory. Is it true?
How can I use those 4GB memory? I can not upgrade to SQL Server 2005 or
other version because i don't want to take this risk.
Thank you very much.True. Standard edition is limited to 2GB
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Damon" <Damon@.china.com> wrote in message
news:3YChh.69507$YV4.69275@.edtnps89...
> There is a Server with 4G Memory. I installed a SQL Server 2000 standard
> version on it.
> I heard that SQLServer2000 could use only up to 2GB memory. Is it true?
> How can I use those 4GB memory? I can not upgrade to SQL Server 2005 or
> other version because i don't want to take this risk.
> Thank you very much.
>|||Thank you Kevin.
Is there any solution to use 4 GB memory by sql2000?
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:uL6CwcuIHHA.4760@.TK2MSFTNGP03.phx.gbl...
> True. Standard edition is limited to 2GB
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Damon" <Damon@.china.com> wrote in message
> news:3YChh.69507$YV4.69275@.edtnps89...
>|||Upgrade to Enterprise Edition.
Configuration -Maximum Capacity Specifications
2000
http://msdn.microsoft.com/library/d...br />
8dbn.asp
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Damon" <Damon@.china.com> wrote in message
news:cuDhh.69523$YV4.18832@.edtnps89...
> Thank you Kevin.
> Is there any solution to use 4 GB memory by sql2000?
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:uL6CwcuIHHA.4760@.TK2MSFTNGP03.phx.gbl...
>|||Damon (Damon@.china.com) writes:
> Thank you Kevin.
> Is there any solution to use 4 GB memory by sql2000?
Upgrade to Enterprise Edition of SQL 2000.
Which is quite more expensive than moving to SQL 2005 Standard, I believe.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns989DEE520DF4DYazorman@.127.0.0.1...
> Damon (Damon@.china.com) writes:
> Upgrade to Enterprise Edition of SQL 2000.
> Which is quite more expensive than moving to SQL 2005 Standard, I believe.
Would a "Named Instance" on SQL 2000 Standard be able to use most of the
remaining half of the 4GB? When I expirimented with named instances back in
2001 - and decided not to use them in a production environment - I only had
2GB in the server.
Even if possible I'm not sure this would be a good solution, just wondering
what the behavior is.

> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||The OS will require some memory I leave 512 MB as a minimum. The remaining
memory could be divided between the various instances of SQL Server,
equally, or one instance getting 2GB and the other only 1.5GB, etc.
You would need to use the Server setting for MAX Server Memory on each
instance.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Russ Rose" <russrose@.hotmail.com> wrote in message
news:5_-dnWp8N8-s1BrYnZ2dnUVZ_u63nZ2d@.comcast.com...
> "Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
> news:Xns989DEE520DF4DYazorman@.127.0.0.1...
> Would a "Named Instance" on SQL 2000 Standard be able to use most of the
> remaining half of the 4GB? When I expirimented with named instances back
> in 2001 - and decided not to use them in a production environment - I only
> had 2GB in the server.
> Even if possible I'm not sure this would be a good solution, just
> wondering what the behavior is.
>
>|||"Russ Rose" <russrose@.hotmail.com> wrote in message
news:5_-dnWp8N8-s1BrYnZ2dnUVZ_u63nZ2d@.comcast.com...
> "Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
> news:Xns989DEE520DF4DYazorman@.127.0.0.1...
> Would a "Named Instance" on SQL 2000 Standard be able to use most of the
> remaining half of the 4GB? When I expirimented with named instances back
> in 2001 - and decided not to use them in a production environment - I only
> had 2GB in the server.
Note for say a website, as I recall, you need a CPU license for each
physical CPU in the machine for each instance (in Standard).
However, this probably won't necessarily help. It depends on the OS.
If you're running Windows 2000 Standard, you're limited to 4 GB of physical
RAM anyway.
Now, 2 gig of physical RAM can be given to a process (3 gig if compiled with
the right options, but that raises other issues here.)
So, if you have 5 gig of physical RAM and an OS that can address all of
that, in theory this could support 2 processes each using 2 gig of physical
RAM with 1 gig reserved for the OS.
If you have less memory, obviously this won't work as well.
Quite honestly, I think your best bet if you really need the memory (and
while I'm always a fan of more memory, sometimes it's just not worth it) is
to move to SQL 2005.

> Even if possible I'm not sure this would be a good solution, just
> wondering what the behavior is.
>
>|||Lines: 71
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
NNTP-Posting-Host: 68.145.111.181
X-Trace: edtnps90 1166550467 68.145.111.181 (Tue, 19 Dec 2006 10:47:47 MST)
NNTP-Posting-Date: Tue, 19 Dec 2006 10:47:47 MST
Xref: leafnode.mcse.ms microsoft.public.sqlserver.server:22144
Thank you every body!
Now, I am going to move to SQL 2005.
Merry Christmas.
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:MdRhh.917$yx6.284@.newsread2.news.pas.earthlink.net...
> "Russ Rose" <russrose@.hotmail.com> wrote in message
> news:5_-dnWp8N8-s1BrYnZ2dnUVZ_u63nZ2d@.comcast.com...
>
> Note for say a website, as I recall, you need a CPU license for each
> physical CPU in the machine for each instance (in Standard).
> However, this probably won't necessarily help. It depends on the OS.
> If you're running Windows 2000 Standard, you're limited to 4 GB of
> physical RAM anyway.
> Now, 2 gig of physical RAM can be given to a process (3 gig if compiled
> with the right options, but that raises other issues here.)
> So, if you have 5 gig of physical RAM and an OS that can address all of
> that, in theory this could support 2 processes each using 2 gig of
> physical RAM with 1 gig reserved for the OS.
> If you have less memory, obviously this won't work as well.
> Quite honestly, I think your best bet if you really need the memory (and
> while I'm always a fan of more memory, sometimes it's just not worth it)
> is to move to SQL 2005.
>
>

Help-Can I use 4 GB memory by SQL Server2000?

There is a Server with 4G Memory. I installed a SQL Server 2000 standard
version on it.
I heard that SQLServer2000 could use only up to 2GB memory. Is it true?
How can I use those 4GB memory? I can not upgrade to SQL Server 2005 or
other version because i don't want to take this risk.

Thank you very much.True. Standard edition is limited to 2GB

--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Damon" <Damon@.china.comwrote in message
news:3YChh.69507$YV4.69275@.edtnps89...

Quote:

Originally Posted by

There is a Server with 4G Memory. I installed a SQL Server 2000 standard
version on it.
I heard that SQLServer2000 could use only up to 2GB memory. Is it true?
How can I use those 4GB memory? I can not upgrade to SQL Server 2005 or
other version because i don't want to take this risk.
>
Thank you very much.
>

|||Thank you Kevin.
Is there any solution to use 4 GB memory by sql2000?

"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.comwrote in message
news:uL6CwcuIHHA.4760@.TK2MSFTNGP03.phx.gbl...

Quote:

Originally Posted by

True. Standard edition is limited to 2GB
>
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
>
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
>
>
"Damon" <Damon@.china.comwrote in message
news:3YChh.69507$YV4.69275@.edtnps89...

Quote:

Originally Posted by

>There is a Server with 4G Memory. I installed a SQL Server 2000 standard
>version on it.
>I heard that SQLServer2000 could use only up to 2GB memory. Is it true?
>How can I use those 4GB memory? I can not upgrade to SQL Server 2005 or
>other version because i don't want to take this risk.
>>
>Thank you very much.
>>


>
>

|||Upgrade to Enterprise Edition.

Configuration -Maximum Capacity Specifications
2000
http://msdn.microsoft.com/library/d..._ar_ts_8dbn.asp
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf

"Damon" <Damon@.china.comwrote in message
news:cuDhh.69523$YV4.18832@.edtnps89...

Quote:

Originally Posted by

Thank you Kevin.
Is there any solution to use 4 GB memory by sql2000?
>
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.comwrote in message
news:uL6CwcuIHHA.4760@.TK2MSFTNGP03.phx.gbl...

Quote:

Originally Posted by

>True. Standard edition is limited to 2GB
>>
>--
>Kevin Hill
>3NF Consulting
>http://www.3nf-inc.com/NewsGroups.htm
>>
>Real-world stuff I run across with SQL Server:
>http://kevin3nf.blogspot.com
>>
>>
>"Damon" <Damon@.china.comwrote in message
>news:3YChh.69507$YV4.69275@.edtnps89...

Quote:

Originally Posted by

>>There is a Server with 4G Memory. I installed a SQL Server 2000 standard
>>version on it.
>>I heard that SQLServer2000 could use only up to 2GB memory. Is it true?
>>How can I use those 4GB memory? I can not upgrade to SQL Server 2005 or
>>other version because i don't want to take this risk.
>>>
>>Thank you very much.
>>>


>>
>>


>
>

|||Damon (Damon@.china.com) writes:

Quote:

Originally Posted by

Thank you Kevin.
Is there any solution to use 4 GB memory by sql2000?


Upgrade to Enterprise Edition of SQL 2000.

Which is quite more expensive than moving to SQL 2005 Standard, I believe.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||"Erland Sommarskog" <esquel@.sommarskog.sewrote in message
news:Xns989DEE520DF4DYazorman@.127.0.0.1...

Quote:

Originally Posted by

Damon (Damon@.china.com) writes:

Quote:

Originally Posted by

>Thank you Kevin.
>Is there any solution to use 4 GB memory by sql2000?


>
Upgrade to Enterprise Edition of SQL 2000.
>
Which is quite more expensive than moving to SQL 2005 Standard, I believe.


Would a "Named Instance" on SQL 2000 Standard be able to use most of the
remaining half of the 4GB? When I expirimented with named instances back in
2001 - and decided not to use them in a production environment - I only had
2GB in the server.

Even if possible I'm not sure this would be a good solution, just wondering
what the behavior is.

Quote:

Originally Posted by

>
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

|||The OS will require some memory I leave 512 MB as a minimum. The remaining
memory could be divided between the various instances of SQL Server,
equally, or one instance getting 2GB and the other only 1.5GB, etc.

You would need to use the Server setting for MAX Server Memory on each
instance.

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf

"Russ Rose" <russrose@.hotmail.comwrote in message
news:5_-dnWp8N8-s1BrYnZ2dnUVZ_u63nZ2d@.comcast.com...

Quote:

Originally Posted by

>
"Erland Sommarskog" <esquel@.sommarskog.sewrote in message
news:Xns989DEE520DF4DYazorman@.127.0.0.1...

Quote:

Originally Posted by

>Damon (Damon@.china.com) writes:

Quote:

Originally Posted by

>>Thank you Kevin.
>>Is there any solution to use 4 GB memory by sql2000?


>>
>Upgrade to Enterprise Edition of SQL 2000.
>>
>Which is quite more expensive than moving to SQL 2005 Standard, I
>believe.


>
Would a "Named Instance" on SQL 2000 Standard be able to use most of the
remaining half of the 4GB? When I expirimented with named instances back
in 2001 - and decided not to use them in a production environment - I only
had 2GB in the server.
>
Even if possible I'm not sure this would be a good solution, just
wondering what the behavior is.
>

Quote:

Originally Posted by

>>
>--
>Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>>
>Books Online for SQL Server 2005 at
>http://www.microsoft.com/technet/pr...oads/books.mspx
>Books Online for SQL Server 2000 at
>http://www.microsoft.com/sql/prodin...ions/books.mspx


>
>

|||"Russ Rose" <russrose@.hotmail.comwrote in message
news:5_-dnWp8N8-s1BrYnZ2dnUVZ_u63nZ2d@.comcast.com...

Quote:

Originally Posted by

>
"Erland Sommarskog" <esquel@.sommarskog.sewrote in message
news:Xns989DEE520DF4DYazorman@.127.0.0.1...

Quote:

Originally Posted by

>Damon (Damon@.china.com) writes:

Quote:

Originally Posted by

>>Thank you Kevin.
>>Is there any solution to use 4 GB memory by sql2000?


>>
>Upgrade to Enterprise Edition of SQL 2000.
>>
>Which is quite more expensive than moving to SQL 2005 Standard, I
>believe.


>
Would a "Named Instance" on SQL 2000 Standard be able to use most of the
remaining half of the 4GB? When I expirimented with named instances back
in 2001 - and decided not to use them in a production environment - I only
had 2GB in the server.


Note for say a website, as I recall, you need a CPU license for each
physical CPU in the machine for each instance (in Standard).

However, this probably won't necessarily help. It depends on the OS.

If you're running Windows 2000 Standard, you're limited to 4 GB of physical
RAM anyway.

Now, 2 gig of physical RAM can be given to a process (3 gig if compiled with
the right options, but that raises other issues here.)

So, if you have 5 gig of physical RAM and an OS that can address all of
that, in theory this could support 2 processes each using 2 gig of physical
RAM with 1 gig reserved for the OS.

If you have less memory, obviously this won't work as well.

Quite honestly, I think your best bet if you really need the memory (and
while I'm always a fan of more memory, sometimes it's just not worth it) is
to move to SQL 2005.

Quote:

Originally Posted by

>
Even if possible I'm not sure this would be a good solution, just
wondering what the behavior is.
>

Quote:

Originally Posted by

>>
>--
>Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>>
>Books Online for SQL Server 2005 at
>http://www.microsoft.com/technet/pr...oads/books.mspx
>Books Online for SQL Server 2000 at
>http://www.microsoft.com/sql/prodin...ions/books.mspx


>
>

|||Thank you every body!
Now, I am going to move to SQL 2005.

Merry Christmas.

"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.comwrote in message
news:MdRhh.917$yx6.284@.newsread2.news.pas.earthlin k.net...

Quote:

Originally Posted by

>
"Russ Rose" <russrose@.hotmail.comwrote in message
news:5_-dnWp8N8-s1BrYnZ2dnUVZ_u63nZ2d@.comcast.com...

Quote:

Originally Posted by

>>
>"Erland Sommarskog" <esquel@.sommarskog.sewrote in message
>news:Xns989DEE520DF4DYazorman@.127.0.0.1...

Quote:

Originally Posted by

>>Damon (Damon@.china.com) writes:
>>>Thank you Kevin.
>>>Is there any solution to use 4 GB memory by sql2000?
>>>
>>Upgrade to Enterprise Edition of SQL 2000.
>>>
>>Which is quite more expensive than moving to SQL 2005 Standard, I
>>believe.


>>
>Would a "Named Instance" on SQL 2000 Standard be able to use most of the
>remaining half of the 4GB? When I expirimented with named instances back
>in 2001 - and decided not to use them in a production environment - I
>only had 2GB in the server.


>
>
Note for say a website, as I recall, you need a CPU license for each
physical CPU in the machine for each instance (in Standard).
>
However, this probably won't necessarily help. It depends on the OS.
>
If you're running Windows 2000 Standard, you're limited to 4 GB of
physical RAM anyway.
>
Now, 2 gig of physical RAM can be given to a process (3 gig if compiled
with the right options, but that raises other issues here.)
>
So, if you have 5 gig of physical RAM and an OS that can address all of
that, in theory this could support 2 processes each using 2 gig of
physical RAM with 1 gig reserved for the OS.
>
If you have less memory, obviously this won't work as well.
>
Quite honestly, I think your best bet if you really need the memory (and
while I'm always a fan of more memory, sometimes it's just not worth it)
is to move to SQL 2005.
>
>

Quote:

Originally Posted by

>>
>Even if possible I'm not sure this would be a good solution, just
>wondering what the behavior is.
>>

Quote:

Originally Posted by

>>>
>>--
>>Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>>>
>>Books Online for SQL Server 2005 at
>>http://www.microsoft.com/technet/pr...oads/books.mspx
>>Books Online for SQL Server 2000 at
>>http://www.microsoft.com/sql/prodin...ions/books.mspx


>>
>>


>
>

Help-Can I use 4 GB memory by SQL Server2000?

There is a Server with 4G Memory. I installed a SQL Server 2000 standard
version on it.
I heard that SQLServer2000 could use only up to 2GB memory. Is it true?
How can I use those 4GB memory? I can not upgrade to SQL Server 2005 or
other version because i don't want to take this risk.
Thank you very much.True. Standard edition is limited to 2GB
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Damon" <Damon@.china.com> wrote in message
news:3YChh.69507$YV4.69275@.edtnps89...
> There is a Server with 4G Memory. I installed a SQL Server 2000 standard
> version on it.
> I heard that SQLServer2000 could use only up to 2GB memory. Is it true?
> How can I use those 4GB memory? I can not upgrade to SQL Server 2005 or
> other version because i don't want to take this risk.
> Thank you very much.
>|||Thank you Kevin.
Is there any solution to use 4 GB memory by sql2000?
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:uL6CwcuIHHA.4760@.TK2MSFTNGP03.phx.gbl...
> True. Standard edition is limited to 2GB
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Damon" <Damon@.china.com> wrote in message
> news:3YChh.69507$YV4.69275@.edtnps89...
>> There is a Server with 4G Memory. I installed a SQL Server 2000 standard
>> version on it.
>> I heard that SQLServer2000 could use only up to 2GB memory. Is it true?
>> How can I use those 4GB memory? I can not upgrade to SQL Server 2005 or
>> other version because i don't want to take this risk.
>> Thank you very much.
>|||Upgrade to Enterprise Edition.
Configuration -Maximum Capacity Specifications
2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Damon" <Damon@.china.com> wrote in message
news:cuDhh.69523$YV4.18832@.edtnps89...
> Thank you Kevin.
> Is there any solution to use 4 GB memory by sql2000?
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:uL6CwcuIHHA.4760@.TK2MSFTNGP03.phx.gbl...
>> True. Standard edition is limited to 2GB
>> --
>> Kevin Hill
>> 3NF Consulting
>> http://www.3nf-inc.com/NewsGroups.htm
>> Real-world stuff I run across with SQL Server:
>> http://kevin3nf.blogspot.com
>>
>> "Damon" <Damon@.china.com> wrote in message
>> news:3YChh.69507$YV4.69275@.edtnps89...
>> There is a Server with 4G Memory. I installed a SQL Server 2000 standard
>> version on it.
>> I heard that SQLServer2000 could use only up to 2GB memory. Is it true?
>> How can I use those 4GB memory? I can not upgrade to SQL Server 2005 or
>> other version because i don't want to take this risk.
>> Thank you very much.
>>
>|||Damon (Damon@.china.com) writes:
> Thank you Kevin.
> Is there any solution to use 4 GB memory by sql2000?
Upgrade to Enterprise Edition of SQL 2000.
Which is quite more expensive than moving to SQL 2005 Standard, I believe.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns989DEE520DF4DYazorman@.127.0.0.1...
> Damon (Damon@.china.com) writes:
>> Thank you Kevin.
>> Is there any solution to use 4 GB memory by sql2000?
> Upgrade to Enterprise Edition of SQL 2000.
> Which is quite more expensive than moving to SQL 2005 Standard, I believe.
Would a "Named Instance" on SQL 2000 Standard be able to use most of the
remaining half of the 4GB? When I expirimented with named instances back in
2001 - and decided not to use them in a production environment - I only had
2GB in the server.
Even if possible I'm not sure this would be a good solution, just wondering
what the behavior is.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||The OS will require some memory I leave 512 MB as a minimum. The remaining
memory could be divided between the various instances of SQL Server,
equally, or one instance getting 2GB and the other only 1.5GB, etc.
You would need to use the Server setting for MAX Server Memory on each
instance.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Russ Rose" <russrose@.hotmail.com> wrote in message
news:5_-dnWp8N8-s1BrYnZ2dnUVZ_u63nZ2d@.comcast.com...
> "Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
> news:Xns989DEE520DF4DYazorman@.127.0.0.1...
>> Damon (Damon@.china.com) writes:
>> Thank you Kevin.
>> Is there any solution to use 4 GB memory by sql2000?
>> Upgrade to Enterprise Edition of SQL 2000.
>> Which is quite more expensive than moving to SQL 2005 Standard, I
>> believe.
> Would a "Named Instance" on SQL 2000 Standard be able to use most of the
> remaining half of the 4GB? When I expirimented with named instances back
> in 2001 - and decided not to use them in a production environment - I only
> had 2GB in the server.
> Even if possible I'm not sure this would be a good solution, just
> wondering what the behavior is.
>> --
>> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>> Books Online for SQL Server 2005 at
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
>> Books Online for SQL Server 2000 at
>> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>|||"Russ Rose" <russrose@.hotmail.com> wrote in message
news:5_-dnWp8N8-s1BrYnZ2dnUVZ_u63nZ2d@.comcast.com...
> "Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
> news:Xns989DEE520DF4DYazorman@.127.0.0.1...
>> Damon (Damon@.china.com) writes:
>> Thank you Kevin.
>> Is there any solution to use 4 GB memory by sql2000?
>> Upgrade to Enterprise Edition of SQL 2000.
>> Which is quite more expensive than moving to SQL 2005 Standard, I
>> believe.
> Would a "Named Instance" on SQL 2000 Standard be able to use most of the
> remaining half of the 4GB? When I expirimented with named instances back
> in 2001 - and decided not to use them in a production environment - I only
> had 2GB in the server.
Note for say a website, as I recall, you need a CPU license for each
physical CPU in the machine for each instance (in Standard).
However, this probably won't necessarily help. It depends on the OS.
If you're running Windows 2000 Standard, you're limited to 4 GB of physical
RAM anyway.
Now, 2 gig of physical RAM can be given to a process (3 gig if compiled with
the right options, but that raises other issues here.)
So, if you have 5 gig of physical RAM and an OS that can address all of
that, in theory this could support 2 processes each using 2 gig of physical
RAM with 1 gig reserved for the OS.
If you have less memory, obviously this won't work as well.
Quite honestly, I think your best bet if you really need the memory (and
while I'm always a fan of more memory, sometimes it's just not worth it) is
to move to SQL 2005.
> Even if possible I'm not sure this would be a good solution, just
> wondering what the behavior is.
>> --
>> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>> Books Online for SQL Server 2005 at
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
>> Books Online for SQL Server 2000 at
>> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>|||Thank you every body!
Now, I am going to move to SQL 2005.
Merry Christmas.
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:MdRhh.917$yx6.284@.newsread2.news.pas.earthlink.net...
> "Russ Rose" <russrose@.hotmail.com> wrote in message
> news:5_-dnWp8N8-s1BrYnZ2dnUVZ_u63nZ2d@.comcast.com...
>> "Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
>> news:Xns989DEE520DF4DYazorman@.127.0.0.1...
>> Damon (Damon@.china.com) writes:
>> Thank you Kevin.
>> Is there any solution to use 4 GB memory by sql2000?
>> Upgrade to Enterprise Edition of SQL 2000.
>> Which is quite more expensive than moving to SQL 2005 Standard, I
>> believe.
>> Would a "Named Instance" on SQL 2000 Standard be able to use most of the
>> remaining half of the 4GB? When I expirimented with named instances back
>> in 2001 - and decided not to use them in a production environment - I
>> only had 2GB in the server.
>
> Note for say a website, as I recall, you need a CPU license for each
> physical CPU in the machine for each instance (in Standard).
> However, this probably won't necessarily help. It depends on the OS.
> If you're running Windows 2000 Standard, you're limited to 4 GB of
> physical RAM anyway.
> Now, 2 gig of physical RAM can be given to a process (3 gig if compiled
> with the right options, but that raises other issues here.)
> So, if you have 5 gig of physical RAM and an OS that can address all of
> that, in theory this could support 2 processes each using 2 gig of
> physical RAM with 1 gig reserved for the OS.
> If you have less memory, obviously this won't work as well.
> Quite honestly, I think your best bet if you really need the memory (and
> while I'm always a fan of more memory, sometimes it's just not worth it)
> is to move to SQL 2005.
>
>> Even if possible I'm not sure this would be a good solution, just
>> wondering what the behavior is.
>>
>> --
>> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>> Books Online for SQL Server 2005 at
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
>> Books Online for SQL Server 2000 at
>> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>>
>

Help--A error about memory!

I use linkedserver to get data from Oracle, but sometimes I get the error below:

Server: Msg 7399, Level 16, State 1, Procedure GetDataFromERP, Line 21
OLE DB provider 'OraOLEDB.Oracle' reported an error.
2006-02-09
[OLE/DB provider returned message: ]
[OLE/DB provider returned message: ROW-00001: Cannot allocate memory]
OLE DB error trace [OLE/DB Provider 'OraOLEDB.Oracle' ICommandText::Execute returned 0x80004005: ].

I think maybe it is because the data is very large.
How do I solve this problem?What is the statement you are executing against the linked server?|||The statement is "select ..... from openquery(......)"
The provider of linkedserver is "Oracle provider for OLE DB"|||That doesn't help much. That is what you are executing locally.

What is the statement you are executing against the linked server?|||This is the main statment of my store procedure:


INSERT INTO
[ARA].[dbo].[AgingData]
([RO], [NS], [CustomerID], [CustomerCode], [CustomerName],
[TransactionalCurrency], [ROCurrency], [CurrentByTrx], [Over1_15ByTrx],
[Over16_30ByTrx], [Over31_60ByTrx], [Over61_90ByTrx], [Over90ByTrx],
[CurrentByRO], [Over1_15ByRO], [Over16_30ByRO], [Over31_60ByRO],
[Over61_90ByRO], [Over90ByRO], [CurrentByUSD], [Over1_15ByUSD],
[Over16_30ByUSD], [Over31_60ByUSD], [Over61_90ByUSD], [Over90ByUSD],
[TotalAmountByTraCur], [TotalAmountByROCur], [TotalAmountByUSD],
[ProductLine], [AgedDate], [ProcessDate], [Tenor_Flag])
SELECT [RO_NAME], [NS_NAME], [CUST_ID], [CUST_NO], [CUST_NAME], [TRX_CURR], [RO_CURR],
[TRX_AMOUNT_BUCKET_1], [TRX_AMOUNT_BUCKET_2], [TRX_AMOUNT_BUCKET_3],
[TRX_AMOUNT_BUCKET_4], [TRX_AMOUNT_BUCKET_5], [TRX_AMOUNT_BUCKET_6],
[RO_CURR_AMOUNT_BUCKET_1], [RO_CURR_AMOUNT_BUCKET_2], [RO_CURR_AMOUNT_BUCKET_3],
[RO_CURR_AMOUNT_BUCKET_4], [RO_CURR_AMOUNT_BUCKET_5], [RO_CURR_AMOUNT_BUCKET_6],
[USD_CURR_AMOUNT_BUCKET_1], [USD_CURR_AMOUNT_BUCKET_2], [USD_CURR_AMOUNT_BUCKET_3],
[USD_CURR_AMOUNT_BUCKET_4], [USD_CURR_AMOUNT_BUCKET_5], [USD_CURR_AMOUNT_BUCKET_6],
[TOTAL_TRX_AMOUNT], [TOTAL_AMOUNT_WITH_RO_CURR], [TOTAL_AMOUNT_WITH_USD_CURR],
[PRODLINE], [AGED_DATE], [PROCESS_DATE], 1
FROM OPENQUERY(ORACLE_BQE,
'SELECT RO_NAME, NS_NAME, CUST_ID, CUST_NO, CUST_NAME, TRX_CURR, RO_CURR,
TRX_AMOUNT_BUCKET_1, TRX_AMOUNT_BUCKET_2, TRX_AMOUNT_BUCKET_3,
TRX_AMOUNT_BUCKET_4, TRX_AMOUNT_BUCKET_5, TRX_AMOUNT_BUCKET_6,
RO_CURR_AMOUNT_BUCKET_1, RO_CURR_AMOUNT_BUCKET_2, RO_CURR_AMOUNT_BUCKET_3,
RO_CURR_AMOUNT_BUCKET_4, RO_CURR_AMOUNT_BUCKET_5, RO_CURR_AMOUNT_BUCKET_6,
USD_CURR_AMOUNT_BUCKET_1, USD_CURR_AMOUNT_BUCKET_2, USD_CURR_AMOUNT_BUCKET_3,
USD_CURR_AMOUNT_BUCKET_4, USD_CURR_AMOUNT_BUCKET_5, USD_CURR_AMOUNT_BUCKET_6,
TOTAL_TRX_AMOUNT, TOTAL_AMOUNT_WITH_RO_CURR, TOTAL_AMOUNT_WITH_USD_CURR,
PRODLINE, TO_CHAR(AGED_DATE) AS AGED_DATE, TO_CHAR(PROCESS_DATE) AS PROCESS_DATE
FROM APPS.XXAR_ARA_AGE_DETAIL')
WHERE CONVERT(NVARCHAR(10), AGED_DATE) = @.BEGINDATE

I just get data from Oracle and insert them to the local table, it is not complicated. But there are another three similar statement in this store procedure.|||Any way you can filter the data on the Oracle side? Try executing your statement as dynamic SQL, which will allow you to pass the @.BEGINDATE value within your OPENQUERY statement, and should reduce the volume of data returned.|||I have solved this problem by filtering data on the Oracle side!
Thank you very much!

Monday, February 27, 2012

HELP: SQL Server Wont Release Memory

Hi,

I am having an issue with SQL server that slows everything to a crawl,
and makes almost any query impossible to complete.

Here are the symptoms:
I stop SQL, I start SQL. The task manager shows SQL starting up and
quickly allocates 50 MB of memory. I then open SQL Manager and I can
open up the instance of SQL Server and I expand to see all of the
databases, memory rises to about 70MB allocated. I then expand a
database and view a list of tables. The memory allocation quickly
rockets to 860+ MB and any attempt to query they database results in
huge hang times.

I have MacAfee anti-virus in place and it is constantly scanning for
viruses, so I don't think it is a virus. The log files do not appear
to be large. I have done everything I know to do to resolve this. Any
help would be much appreciated.

Does anyone have any ideas?

Thank you for taking the time to read this.

Tod"Tod1d" <tod124@.icqmail.com> wrote in message
news:d3ce916b.0309160556.72dbc548@.posting.google.c om...
> Hi,
> I am having an issue with SQL server that slows everything to a crawl,
> and makes almost any query impossible to complete.
> Here are the symptoms:
> I stop SQL, I start SQL. The task manager shows SQL starting up and
> quickly allocates 50 MB of memory. I then open SQL Manager and I can
> open up the instance of SQL Server and I expand to see all of the
> databases, memory rises to about 70MB allocated. I then expand a
> database and view a list of tables. The memory allocation quickly
> rockets to 860+ MB and any attempt to query they database results in
> huge hang times.
> I have MacAfee anti-virus in place and it is constantly scanning for
> viruses, so I don't think it is a virus. The log files do not appear
> to be large. I have done everything I know to do to resolve this. Any
> help would be much appreciated.
> Does anyone have any ideas?
> Thank you for taking the time to read this.
> Tod

Have you tried excluding your MSSQL data folders (all the .mdf/.ndf/.ldf
files) from the virus scan? If the antivirus software is scanning a database
file when MSSQL starts up, then there could easily be a problem of some
kind.

http://support.microsoft.com/defaul...kb;en-us;309422

Simon|||[posted and mailed, please reply in news]

Tod1d (tod124@.icqmail.com) writes:
> I am having an issue with SQL server that slows everything to a crawl,
> and makes almost any query impossible to complete.
> Here are the symptoms:
> I stop SQL, I start SQL. The task manager shows SQL starting up and
> quickly allocates 50 MB of memory. I then open SQL Manager and I can
> open up the instance of SQL Server and I expand to see all of the
> databases, memory rises to about 70MB allocated. I then expand a
> database and view a list of tables. The memory allocation quickly
> rockets to 860+ MB and any attempt to query they database results in
> huge hang times.

McAfee could indeed be a culprit, as Simon suggested. You should
also check if you have your databases set to autoclose, and you should
also check that you don't have ODBC tracing on. (Check this from the
ODBC applet in the Control Panel.)

As for the memory, this behaviour is by design. SQL Server grasps as
much memory it can, because it thinks that memory is good for cache.
If there are other applications on the same machine, SQL Server will
yeild if they need memory, but it may not yield fast enough. You can
control how much memory SQL Server may use from the Memory tab in
Enterprise Manager.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

HELP: SQL Server 2000 will not start after full system restore

Hi,
I just did a full system backup, memory and hard disk reconfiguration,
and a full system restore of my SQL Server 2000 machine.
SQL Server refuses to start as a service giving the error message:
"could not start the MSSQLSERVER service on the local computer"
"Error 3: the system cannot find the path specified"
It however starts from the command prompt by simply executing:
"C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe"
Any assistance welcome!Hi
Check what flags you have specified when you start it as a service.
John
"kim@.kasnet.com" wrote:

> Hi,
> I just did a full system backup, memory and hard disk reconfiguration,
> and a full system restore of my SQL Server 2000 machine.
> SQL Server refuses to start as a service giving the error message:
> "could not start the MSSQLSERVER service on the local computer"
> "Error 3: the system cannot find the path specified"
> It however starts from the command prompt by simply executing:
> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe"
> Any assistance welcome!
>|||Hi John,
There are no flags specified as startup parameters... is there
anything else I should check?
Kim
On Tue, 25 Apr 2006 09:48:01 -0700, John Bell
<jbellnewsposts@.hotmail.com> wrote:
[vbcol=seagreen]
>Hi
>Check what flags you have specified when you start it as a service.
>John
>"kim@.kasnet.com" wrote:
>|||Hi
Check the registry
key& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\MSSQLServer\Parame
ters]
You will find entries like:
"SQLArg0"="-dC:\\Program Files\\Microsoft SQL Server\\MSSQL\\data\\master.md
f"
"SQLArg1"="-eC:\\Program Files\\Microsoft SQL Server\\MSSQL\\log\\ERRORLOG"
"SQLArg2"="-lC:\\Program Files\\Microsoft SQL
Server\\MSSQL\\data\\mastlog.ldf"
Check that these files/directories exists. Other possible parameters are
detailed in Books Online topic "sqlservr Application"
John
"velliott@.hdhopwood.com" wrote:

> Hi John,
> There are no flags specified as startup parameters... is there
> anything else I should check?
> Kim
> On Tue, 25 Apr 2006 09:48:01 -0700, John Bell
> <jbellnewsposts@.hotmail.com> wrote:
>
>|||I checked the registry entries and the only difference is that there
are single backslashes in the directory path. All other path entries
in the registry are represented the same way.
If this is the problem, my logic tells me that the SQL Server should
not start from the command prompt anyway!
Is there a way to get the service startup process to indicate which
specific path it cannot find?
Kim
On Thu, 27 Apr 2006 00:04:01 -0700, John Bell
<jbellnewsposts@.hotmail.com> wrote:
[vbcol=seagreen]
>Hi
>Check the registry
>key& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\MSSQLServer\Param
eters]
>You will find entries like:
>"SQLArg0"="-dC:\\Program Files\\Microsoft SQL Server\\MSSQL\\data\\master.m
df"
>"SQLArg1"="-eC:\\Program Files\\Microsoft SQL Server\\MSSQL\\log\\ERRORLOG"
>"SQLArg2"="-lC:\\Program Files\\Microsoft SQL
>Server\\MSSQL\\data\\mastlog.ldf"
>Check that these files/directories exists. Other possible parameters are
>detailed in Books Online topic "sqlservr Application"
>John
>
>"velliott@.hdhopwood.com" wrote:
>|||Hi
The double backslashes are from an export of the registry check other
registry values such as
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\Setup]
John
"velliott@.hdhopwood.com" wrote:

> I checked the registry entries and the only difference is that there
> are single backslashes in the directory path. All other path entries
> in the registry are represented the same way.
> If this is the problem, my logic tells me that the SQL Server should
> not start from the command prompt anyway!
> Is there a way to get the service startup process to indicate which
> specific path it cannot find?
> Kim
> On Thu, 27 Apr 2006 00:04:01 -0700, John Bell
> <jbellnewsposts@.hotmail.com> wrote:
>
>|||John,
The registry keys in error were:
& #91;HKEY_LOCAL_MACHINE\SYSTEM\CurrentCon
trolSet\Services\MSSQLServer\ImageP
ath]
and
& #91;HKEY_LOCAL_MACHINE\SYSTEM\CurrentCon
trolSet\Services\MSSQLServer\Perfor
mance\Library]
Both contained the DOS version of the path (eg.
C:\Program~1\Micro~2\...) to the relevant binaries.
I expanded the paths and the service started without error!
Many thanks for your patience and invaluable assistance!!!
Kim
On Thu, 27 Apr 2006 09:50:02 -0700, John Bell
<jbellnewsposts@.hotmail.com> wrote:
[vbcol=seagreen]
>Hi
>The double backslashes are from an export of the registry check other
>registry values such as
>& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\Setup]
>John
>"velliott@.hdhopwood.com" wrote:
>

HELP: SQL Server 2000 will not start after full system restore

Hi,
I just did a full system backup, memory and hard disk reconfiguration,
and a full system restore of my SQL Server 2000 machine.
SQL Server refuses to start as a service giving the error message:
"could not start the MSSQLSERVER service on the local computer"
"Error 3: the system cannot find the path specified"
It however starts from the command prompt by simply executing:
"C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe"
Any assistance welcome!Hi
Check what flags you have specified when you start it as a service.
John
"kim@.kasnet.com" wrote:
> Hi,
> I just did a full system backup, memory and hard disk reconfiguration,
> and a full system restore of my SQL Server 2000 machine.
> SQL Server refuses to start as a service giving the error message:
> "could not start the MSSQLSERVER service on the local computer"
> "Error 3: the system cannot find the path specified"
> It however starts from the command prompt by simply executing:
> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe"
> Any assistance welcome!
>|||Hi John,
There are no flags specified as startup parameters... is there
anything else I should check?
Kim
On Tue, 25 Apr 2006 09:48:01 -0700, John Bell
<jbellnewsposts@.hotmail.com> wrote:
>Hi
>Check what flags you have specified when you start it as a service.
>John
>"kim@.kasnet.com" wrote:
>> Hi,
>> I just did a full system backup, memory and hard disk reconfiguration,
>> and a full system restore of my SQL Server 2000 machine.
>> SQL Server refuses to start as a service giving the error message:
>> "could not start the MSSQLSERVER service on the local computer"
>> "Error 3: the system cannot find the path specified"
>> It however starts from the command prompt by simply executing:
>> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe"
>> Any assistance welcome!|||Hi
Check the registry
key[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters]
You will find entries like:
"SQLArg0"="-dC:\\Program Files\\Microsoft SQL Server\\MSSQL\\data\\master.mdf"
"SQLArg1"="-eC:\\Program Files\\Microsoft SQL Server\\MSSQL\\log\\ERRORLOG"
"SQLArg2"="-lC:\\Program Files\\Microsoft SQL
Server\\MSSQL\\data\\mastlog.ldf"
Check that these files/directories exists. Other possible parameters are
detailed in Books Online topic "sqlservr Application"
John
"velliott@.hdhopwood.com" wrote:
> Hi John,
> There are no flags specified as startup parameters... is there
> anything else I should check?
> Kim
> On Tue, 25 Apr 2006 09:48:01 -0700, John Bell
> <jbellnewsposts@.hotmail.com> wrote:
> >Hi
> >
> >Check what flags you have specified when you start it as a service.
> >
> >John
> >
> >"kim@.kasnet.com" wrote:
> >
> >> Hi,
> >>
> >> I just did a full system backup, memory and hard disk reconfiguration,
> >> and a full system restore of my SQL Server 2000 machine.
> >>
> >> SQL Server refuses to start as a service giving the error message:
> >>
> >> "could not start the MSSQLSERVER service on the local computer"
> >> "Error 3: the system cannot find the path specified"
> >>
> >> It however starts from the command prompt by simply executing:
> >> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe"
> >>
> >> Any assistance welcome!
> >>
>|||I checked the registry entries and the only difference is that there
are single backslashes in the directory path. All other path entries
in the registry are represented the same way.
If this is the problem, my logic tells me that the SQL Server should
not start from the command prompt anyway!
Is there a way to get the service startup process to indicate which
specific path it cannot find?
Kim
On Thu, 27 Apr 2006 00:04:01 -0700, John Bell
<jbellnewsposts@.hotmail.com> wrote:
>Hi
>Check the registry
>key[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters]
>You will find entries like:
>"SQLArg0"="-dC:\\Program Files\\Microsoft SQL Server\\MSSQL\\data\\master.mdf"
>"SQLArg1"="-eC:\\Program Files\\Microsoft SQL Server\\MSSQL\\log\\ERRORLOG"
>"SQLArg2"="-lC:\\Program Files\\Microsoft SQL
>Server\\MSSQL\\data\\mastlog.ldf"
>Check that these files/directories exists. Other possible parameters are
>detailed in Books Online topic "sqlservr Application"
>John
>
>"velliott@.hdhopwood.com" wrote:
>> Hi John,
>> There are no flags specified as startup parameters... is there
>> anything else I should check?
>> Kim
>> On Tue, 25 Apr 2006 09:48:01 -0700, John Bell
>> <jbellnewsposts@.hotmail.com> wrote:
>> >Hi
>> >
>> >Check what flags you have specified when you start it as a service.
>> >
>> >John
>> >
>> >"kim@.kasnet.com" wrote:
>> >
>> >> Hi,
>> >>
>> >> I just did a full system backup, memory and hard disk reconfiguration,
>> >> and a full system restore of my SQL Server 2000 machine.
>> >>
>> >> SQL Server refuses to start as a service giving the error message:
>> >>
>> >> "could not start the MSSQLSERVER service on the local computer"
>> >> "Error 3: the system cannot find the path specified"
>> >>
>> >> It however starts from the command prompt by simply executing:
>> >> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe"
>> >>
>> >> Any assistance welcome!
>> >>
>>|||Hi
The double backslashes are from an export of the registry check other
registry values such as
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup]
John
"velliott@.hdhopwood.com" wrote:
> I checked the registry entries and the only difference is that there
> are single backslashes in the directory path. All other path entries
> in the registry are represented the same way.
> If this is the problem, my logic tells me that the SQL Server should
> not start from the command prompt anyway!
> Is there a way to get the service startup process to indicate which
> specific path it cannot find?
> Kim
> On Thu, 27 Apr 2006 00:04:01 -0700, John Bell
> <jbellnewsposts@.hotmail.com> wrote:
> >Hi
> >
> >Check the registry
> >key[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters]
> >
> >You will find entries like:
> >"SQLArg0"="-dC:\\Program Files\\Microsoft SQL Server\\MSSQL\\data\\master.mdf"
> >"SQLArg1"="-eC:\\Program Files\\Microsoft SQL Server\\MSSQL\\log\\ERRORLOG"
> >"SQLArg2"="-lC:\\Program Files\\Microsoft SQL
> >Server\\MSSQL\\data\\mastlog.ldf"
> >
> >Check that these files/directories exists. Other possible parameters are
> >detailed in Books Online topic "sqlservr Application"
> >
> >John
> >
> >
> >"velliott@.hdhopwood.com" wrote:
> >
> >> Hi John,
> >>
> >> There are no flags specified as startup parameters... is there
> >> anything else I should check?
> >>
> >> Kim
> >>
> >> On Tue, 25 Apr 2006 09:48:01 -0700, John Bell
> >> <jbellnewsposts@.hotmail.com> wrote:
> >>
> >> >Hi
> >> >
> >> >Check what flags you have specified when you start it as a service.
> >> >
> >> >John
> >> >
> >> >"kim@.kasnet.com" wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> I just did a full system backup, memory and hard disk reconfiguration,
> >> >> and a full system restore of my SQL Server 2000 machine.
> >> >>
> >> >> SQL Server refuses to start as a service giving the error message:
> >> >>
> >> >> "could not start the MSSQLSERVER service on the local computer"
> >> >> "Error 3: the system cannot find the path specified"
> >> >>
> >> >> It however starts from the command prompt by simply executing:
> >> >> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe"
> >> >>
> >> >> Any assistance welcome!
> >> >>
> >>
> >>
>|||John,
The registry keys in error were:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServer\ImagePath]
and
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServer\Performance\Library]
Both contained the DOS version of the path (eg.
C:\Program~1\Micro~2\...) to the relevant binaries.
I expanded the paths and the service started without error!
Many thanks for your patience and invaluable assistance!!!
Kim
On Thu, 27 Apr 2006 09:50:02 -0700, John Bell
<jbellnewsposts@.hotmail.com> wrote:
>Hi
>The double backslashes are from an export of the registry check other
>registry values such as
>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup]
>John
>"velliott@.hdhopwood.com" wrote:
>> I checked the registry entries and the only difference is that there
>> are single backslashes in the directory path. All other path entries
>> in the registry are represented the same way.
>> If this is the problem, my logic tells me that the SQL Server should
>> not start from the command prompt anyway!
>> Is there a way to get the service startup process to indicate which
>> specific path it cannot find?
>> Kim
>> On Thu, 27 Apr 2006 00:04:01 -0700, John Bell
>> <jbellnewsposts@.hotmail.com> wrote:
>> >Hi
>> >
>> >Check the registry
>> >key[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters]
>> >
>> >You will find entries like:
>> >"SQLArg0"="-dC:\\Program Files\\Microsoft SQL Server\\MSSQL\\data\\master.mdf"
>> >"SQLArg1"="-eC:\\Program Files\\Microsoft SQL Server\\MSSQL\\log\\ERRORLOG"
>> >"SQLArg2"="-lC:\\Program Files\\Microsoft SQL
>> >Server\\MSSQL\\data\\mastlog.ldf"
>> >
>> >Check that these files/directories exists. Other possible parameters are
>> >detailed in Books Online topic "sqlservr Application"
>> >
>> >John
>> >
>> >
>> >"velliott@.hdhopwood.com" wrote:
>> >
>> >> Hi John,
>> >>
>> >> There are no flags specified as startup parameters... is there
>> >> anything else I should check?
>> >>
>> >> Kim
>> >>
>> >> On Tue, 25 Apr 2006 09:48:01 -0700, John Bell
>> >> <jbellnewsposts@.hotmail.com> wrote:
>> >>
>> >> >Hi
>> >> >
>> >> >Check what flags you have specified when you start it as a service.
>> >> >
>> >> >John
>> >> >
>> >> >"kim@.kasnet.com" wrote:
>> >> >
>> >> >> Hi,
>> >> >>
>> >> >> I just did a full system backup, memory and hard disk reconfiguration,
>> >> >> and a full system restore of my SQL Server 2000 machine.
>> >> >>
>> >> >> SQL Server refuses to start as a service giving the error message:
>> >> >>
>> >> >> "could not start the MSSQLSERVER service on the local computer"
>> >> >> "Error 3: the system cannot find the path specified"
>> >> >>
>> >> >> It however starts from the command prompt by simply executing:
>> >> >> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe"
>> >> >>
>> >> >> Any assistance welcome!
>> >> >>
>> >>
>> >>
>>|||<kim@.kasnet.com> wrote in message
news:l0fs421805aj0doegq6e26ft224ll3mj99@.4ax.com...
> Hi,
> I just did a full system backup, memory and hard disk reconfiguration,
> and a full system restore of my SQL Server 2000 machine.
> SQL Server refuses to start as a service giving the error message:
> "could not start the MSSQLSERVER service on the local computer"
> "Error 3: the system cannot find the path specified"
> It however starts from the command prompt by simply executing:
> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe"
> Any assistance welcome!
How did you do your system restore?
We had a situation once where files were robocopied from old hardware to
new. The problem with that was that some files took longer to copy than
others, and this messed up the 8.3 names of those blasted c:\Program
Files\Microsoft ... directories. For example, the SQL Server directory was
MICROS~4 on the old box, but MICROS~2 on the new box. We didn't notice this
until we started getting weird errors like you describe. When we checked
the registry, we found that many keys referenced those directories by 8.3
name. Fixing it was a headache.|||Hi Karen
The OP has found that the registry enties
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServer\ImagePath]
and
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServer\Performance\Library]
had 8.3 files names in them, change them to the correct values solved her
problem.
John
"Karen Collins" wrote:
> <kim@.kasnet.com> wrote in message
> news:l0fs421805aj0doegq6e26ft224ll3mj99@.4ax.com...
> > Hi,
> >
> > I just did a full system backup, memory and hard disk reconfiguration,
> > and a full system restore of my SQL Server 2000 machine.
> >
> > SQL Server refuses to start as a service giving the error message:
> >
> > "could not start the MSSQLSERVER service on the local computer"
> > "Error 3: the system cannot find the path specified"
> >
> > It however starts from the command prompt by simply executing:
> > "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe"
> >
> > Any assistance welcome!
> How did you do your system restore?
> We had a situation once where files were robocopied from old hardware to
> new. The problem with that was that some files took longer to copy than
> others, and this messed up the 8.3 names of those blasted c:\Program
> Files\Microsoft ... directories. For example, the SQL Server directory was
> MICROS~4 on the old box, but MICROS~2 on the new box. We didn't notice this
> until we started getting weird errors like you describe. When we checked
> the registry, we found that many keys referenced those directories by 8.3
> name. Fixing it was a headache.
>
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:86E6F2AF-BD89-46C2-88BB-1329784382E3@.microsoft.com...
> Hi Karen
> The OP has found that the registry enties
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServer\ImagePath]
> and
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServer\Performance\Library]
> had 8.3 files names in them, change them to the correct values solved her
> problem.
Thanks for the update. Glad to hear she was able to fix the problem.

Sunday, February 19, 2012

Help: Can I load all table content to the memory during SQL server Startup?

Dear Sir,
I use SQL 2000 server. I want to load all the table content to the
memory the SQL server startup.
How can I do that?
My computer has 2 G RAM. The total space of the databse is 1G.
I have set the mininum memory is 1G (in dynamic configue SQL memory) in SQL
server and check the "Reserved physical memory for SQL server". But no all
data load into the memory during SQL server startup.
I just know that if I write a SQL statement to request records, these
records will be load into memory.
SO, I think it is not a good method to select all tables once after the SQL
server just startup.
Thank you for your help!
--
Regards,
Anthony LamAssuming you really want to do this, create a stored procedure which reads the rows and mark it as a
startup proc (sp_procoption).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"AA" <anthony@.jadeflex.com> wrote in message news:%23ARNLe$gDHA.3272@.tk2msftngp13.phx.gbl...
> Dear Sir,
> I use SQL 2000 server. I want to load all the table content to the
> memory the SQL server startup.
> How can I do that?
> My computer has 2 G RAM. The total space of the databse is 1G.
> I have set the mininum memory is 1G (in dynamic configue SQL memory) in SQL
> server and check the "Reserved physical memory for SQL server". But no all
> data load into the memory during SQL server startup.
> I just know that if I write a SQL statement to request records, these
> records will be load into memory.
> SO, I think it is not a good method to select all tables once after the SQL
> server just startup.
> Thank you for your help!
> --
> Regards,
> Anthony Lam
>