Kind of an obscure question, but here goes.
SQL2000 SP4
I have a E: drive on my SQL server that is ~400gb. On it you'll find
a ~100gb live DB file and last night's 100gb .bak file (maintenance
plan is set for one day retention). The vendor is telling me that I
am going to run out of space doing the SQL backups because 100gb is
used by the live DB, 100gb is used by last nights .bak file, 100gb
will be used to write today's .bak file, and the last 100gb will be
used in the deletion process of removing the old .bak file.
I can't say I know how SQL handles the removal of the old .bak file
but is this a true statement that SQL will need equal free space to
delete the old .bak file?SQL deletes old backups AFTER creating new ones, so you will need space for
at least two backups.
Look at it this way, what happens if your database blows up during a backup.
If you have an older backup, you are fine. If you are overwriting your only
backup, it is time to polish up the resume.
Personally, I would go out and buy a couple of USB drives and back up to
there. Last week my mother purchased a 500GB model for $99. If that is not
an option, you could look into one of the commercially available backup
compression tools. The three major ones are SQLSafe (www.idera.com),
LiteSpeed for SQL (www.quest.com), and SQL Backup (www.red-gate.com).
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:04b97215-0ec7-4545-a43b-f072fb3c47a2@.e6g2000prf.googlegroups.com...
> Kind of an obscure question, but here goes.
> SQL2000 SP4
> I have a E: drive on my SQL server that is ~400gb. On it you'll find
> a ~100gb live DB file and last night's 100gb .bak file (maintenance
> plan is set for one day retention). The vendor is telling me that I
> am going to run out of space doing the SQL backups because 100gb is
> used by the live DB, 100gb is used by last nights .bak file, 100gb
> will be used to write today's .bak file, and the last 100gb will be
> used in the deletion process of removing the old .bak file.
> I can't say I know how SQL handles the removal of the old .bak file
> but is this a true statement that SQL will need equal free space to
> delete the old .bak file?|||Right, I aggree. In your scenario I need 300gb, not 400gb as the
vendor claims.
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
--
300gb Total to perform the whole operation
Vendor is saying:
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
100gb - extra needed to delete last nights backup after a successful
backup
--
400gb Total to perform the whole operation
I just don't understand why that extra 100gb is needed.
On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> SQL deletes old backups AFTER creating new ones, so you will need space for
> at least two backups.
> Look at it this way, what happens if your database blows up during a backup.
> If you have an older backup, you are fine. If you are overwriting your only
> backup, it is time to polish up the resume.|||Also, a backup on the same disk as the primary is pretty useless when you
think about it.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>> SQL deletes old backups AFTER creating new ones, so you will need space
>> for
>> at least two backups.
>> Look at it this way, what happens if your database blows up during a
>> backup.
>> If you have an older backup, you are fine. If you are overwriting your
>> only
>> backup, it is time to polish up the resume.|||Only if it's not getting written to tape ;)
On Nov 28, 11:28 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Also, a backup on the same disk as the primary is pretty useless when you
> think about it.|||I've never seen Windows needing temp storage in order to delete a file. Perhaps your vendor somehow
confuses the windows Recycle Bin functionality somehow...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>> SQL deletes old backups AFTER creating new ones, so you will need space for
>> at least two backups.
>> Look at it this way, what happens if your database blows up during a backup.
>> If you have an older backup, you are fine. If you are overwriting your only
>> backup, it is time to polish up the resume.sql
Showing posts with label sp4. Show all posts
Showing posts with label sp4. Show all posts
Thursday, March 29, 2012
Thursday, March 22, 2012
Enterprise Manager/Query Analyser hangs
Hi, hope somebody can help - we have found a strange problem at one of our
clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
when they click the + on Databases on Enterprise manager, it hangs and also
hangs the server (applications accessing the DB timeout). We found that user
sa did not have access to any DBs! -- which we restored with sp_changedbowner
- but still hangs! Query analyser also hangs when opening object browser. All
other actions also very slow. Have also checked and switched off autoclose on
all DBs.
Could not yet determine how and exactly when this happened.
Any advice appreciated.
Alice van Rensburg
>. We found that user
> sa did not have access to any DBs! --
sa is a sysadmin and has acceess by default to all databases
Is it poosible another actvities on the server?
"Alice" <Alice@.discussions.microsoft.com> wrote in message
news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
> Hi, hope somebody can help - we have found a strange problem at one of our
> clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
> when they click the + on Databases on Enterprise manager, it hangs and
> also
> hangs the server (applications accessing the DB timeout). We found that
> user
> sa did not have access to any DBs! -- which we restored with
> sp_changedbowner
> - but still hangs! Query analyser also hangs when opening object browser.
> All
> other actions also very slow. Have also checked and switched off autoclose
> on
> all DBs.
> Could not yet determine how and exactly when this happened.
> Any advice appreciated.
> Alice van Rensburg
>
|||Thanx for your reply - the interesting thing is that user sa did have access
to all DBs when we last checked (in December) - something must have happened
to change that, but we do not know what. Have checked - nothing else running
on the SQL server. We are seriously considering uninstall and reinstall.
"Uri Dimant" wrote:
> sa is a sysadmin and has acceess by default to all databases
> Is it poosible another actvities on the server?
>
> "Alice" <Alice@.discussions.microsoft.com> wrote in message
> news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
>
>
|||Managed to resolve this issue - seems like one of the dbs still had a
non-existing Windows NT user as dbowner. We detached all DBs, and reattached
them one by one, each time checking the owner and checking if DataBases
folder opens.
Regards
A
"Alice" wrote:
[vbcol=seagreen]
> Thanx for your reply - the interesting thing is that user sa did have access
> to all DBs when we last checked (in December) - something must have happened
> to change that, but we do not know what. Have checked - nothing else running
> on the SQL server. We are seriously considering uninstall and reinstall.
> "Uri Dimant" wrote:
clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
when they click the + on Databases on Enterprise manager, it hangs and also
hangs the server (applications accessing the DB timeout). We found that user
sa did not have access to any DBs! -- which we restored with sp_changedbowner
- but still hangs! Query analyser also hangs when opening object browser. All
other actions also very slow. Have also checked and switched off autoclose on
all DBs.
Could not yet determine how and exactly when this happened.
Any advice appreciated.
Alice van Rensburg
>. We found that user
> sa did not have access to any DBs! --
sa is a sysadmin and has acceess by default to all databases
Is it poosible another actvities on the server?
"Alice" <Alice@.discussions.microsoft.com> wrote in message
news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
> Hi, hope somebody can help - we have found a strange problem at one of our
> clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
> when they click the + on Databases on Enterprise manager, it hangs and
> also
> hangs the server (applications accessing the DB timeout). We found that
> user
> sa did not have access to any DBs! -- which we restored with
> sp_changedbowner
> - but still hangs! Query analyser also hangs when opening object browser.
> All
> other actions also very slow. Have also checked and switched off autoclose
> on
> all DBs.
> Could not yet determine how and exactly when this happened.
> Any advice appreciated.
> Alice van Rensburg
>
|||Thanx for your reply - the interesting thing is that user sa did have access
to all DBs when we last checked (in December) - something must have happened
to change that, but we do not know what. Have checked - nothing else running
on the SQL server. We are seriously considering uninstall and reinstall.
"Uri Dimant" wrote:
> sa is a sysadmin and has acceess by default to all databases
> Is it poosible another actvities on the server?
>
> "Alice" <Alice@.discussions.microsoft.com> wrote in message
> news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
>
>
|||Managed to resolve this issue - seems like one of the dbs still had a
non-existing Windows NT user as dbowner. We detached all DBs, and reattached
them one by one, each time checking the owner and checking if DataBases
folder opens.
Regards
A
"Alice" wrote:
[vbcol=seagreen]
> Thanx for your reply - the interesting thing is that user sa did have access
> to all DBs when we last checked (in December) - something must have happened
> to change that, but we do not know what. Have checked - nothing else running
> on the SQL server. We are seriously considering uninstall and reinstall.
> "Uri Dimant" wrote:
Enterprise Manager/Query Analyser hangs
Hi, hope somebody can help - we have found a strange problem at one of our
clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
when they click the + on Databases on Enterprise manager, it hangs and also
hangs the server (applications accessing the DB timeout). We found that user
sa did not have access to any DBs! -- which we restored with sp_changedbowner
- but still hangs! Query analyser also hangs when opening object browser. All
other actions also very slow. Have also checked and switched off autoclose on
all DBs.
Could not yet determine how and exactly when this happened.
Any advice appreciated.
Alice van Rensburg>. We found that user
> sa did not have access to any DBs! --
sa is a sysadmin and has acceess by default to all databases
Is it poosible another actvities on the server?
"Alice" <Alice@.discussions.microsoft.com> wrote in message
news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
> Hi, hope somebody can help - we have found a strange problem at one of our
> clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
> when they click the + on Databases on Enterprise manager, it hangs and
> also
> hangs the server (applications accessing the DB timeout). We found that
> user
> sa did not have access to any DBs! -- which we restored with
> sp_changedbowner
> - but still hangs! Query analyser also hangs when opening object browser.
> All
> other actions also very slow. Have also checked and switched off autoclose
> on
> all DBs.
> Could not yet determine how and exactly when this happened.
> Any advice appreciated.
> Alice van Rensburg
>|||Thanx for your reply - the interesting thing is that user sa did have access
to all DBs when we last checked (in December) - something must have happened
to change that, but we do not know what. Have checked - nothing else running
on the SQL server. We are seriously considering uninstall and reinstall.
"Uri Dimant" wrote:
> >. We found that user
> > sa did not have access to any DBs! --
> sa is a sysadmin and has acceess by default to all databases
> Is it poosible another actvities on the server?
>
> "Alice" <Alice@.discussions.microsoft.com> wrote in message
> news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
> > Hi, hope somebody can help - we have found a strange problem at one of our
> > clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
> > when they click the + on Databases on Enterprise manager, it hangs and
> > also
> > hangs the server (applications accessing the DB timeout). We found that
> > user
> > sa did not have access to any DBs! -- which we restored with
> > sp_changedbowner
> > - but still hangs! Query analyser also hangs when opening object browser.
> > All
> > other actions also very slow. Have also checked and switched off autoclose
> > on
> > all DBs.
> > Could not yet determine how and exactly when this happened.
> > Any advice appreciated.
> > Alice van Rensburg
> >
>
>|||Managed to resolve this issue - seems like one of the dbs still had a
non-existing Windows NT user as dbowner. We detached all DBs, and reattached
them one by one, each time checking the owner and checking if DataBases
folder opens.
Regards
A
"Alice" wrote:
> Thanx for your reply - the interesting thing is that user sa did have access
> to all DBs when we last checked (in December) - something must have happened
> to change that, but we do not know what. Have checked - nothing else running
> on the SQL server. We are seriously considering uninstall and reinstall.
> "Uri Dimant" wrote:
> > >. We found that user
> > > sa did not have access to any DBs! --
> >
> > sa is a sysadmin and has acceess by default to all databases
> >
> > Is it poosible another actvities on the server?
> >
> >
> >
> > "Alice" <Alice@.discussions.microsoft.com> wrote in message
> > news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
> > > Hi, hope somebody can help - we have found a strange problem at one of our
> > > clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
> > > when they click the + on Databases on Enterprise manager, it hangs and
> > > also
> > > hangs the server (applications accessing the DB timeout). We found that
> > > user
> > > sa did not have access to any DBs! -- which we restored with
> > > sp_changedbowner
> > > - but still hangs! Query analyser also hangs when opening object browser.
> > > All
> > > other actions also very slow. Have also checked and switched off autoclose
> > > on
> > > all DBs.
> > > Could not yet determine how and exactly when this happened.
> > > Any advice appreciated.
> > > Alice van Rensburg
> > >
> >
> >
> >
clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
when they click the + on Databases on Enterprise manager, it hangs and also
hangs the server (applications accessing the DB timeout). We found that user
sa did not have access to any DBs! -- which we restored with sp_changedbowner
- but still hangs! Query analyser also hangs when opening object browser. All
other actions also very slow. Have also checked and switched off autoclose on
all DBs.
Could not yet determine how and exactly when this happened.
Any advice appreciated.
Alice van Rensburg>. We found that user
> sa did not have access to any DBs! --
sa is a sysadmin and has acceess by default to all databases
Is it poosible another actvities on the server?
"Alice" <Alice@.discussions.microsoft.com> wrote in message
news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
> Hi, hope somebody can help - we have found a strange problem at one of our
> clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
> when they click the + on Databases on Enterprise manager, it hangs and
> also
> hangs the server (applications accessing the DB timeout). We found that
> user
> sa did not have access to any DBs! -- which we restored with
> sp_changedbowner
> - but still hangs! Query analyser also hangs when opening object browser.
> All
> other actions also very slow. Have also checked and switched off autoclose
> on
> all DBs.
> Could not yet determine how and exactly when this happened.
> Any advice appreciated.
> Alice van Rensburg
>|||Thanx for your reply - the interesting thing is that user sa did have access
to all DBs when we last checked (in December) - something must have happened
to change that, but we do not know what. Have checked - nothing else running
on the SQL server. We are seriously considering uninstall and reinstall.
"Uri Dimant" wrote:
> >. We found that user
> > sa did not have access to any DBs! --
> sa is a sysadmin and has acceess by default to all databases
> Is it poosible another actvities on the server?
>
> "Alice" <Alice@.discussions.microsoft.com> wrote in message
> news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
> > Hi, hope somebody can help - we have found a strange problem at one of our
> > clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
> > when they click the + on Databases on Enterprise manager, it hangs and
> > also
> > hangs the server (applications accessing the DB timeout). We found that
> > user
> > sa did not have access to any DBs! -- which we restored with
> > sp_changedbowner
> > - but still hangs! Query analyser also hangs when opening object browser.
> > All
> > other actions also very slow. Have also checked and switched off autoclose
> > on
> > all DBs.
> > Could not yet determine how and exactly when this happened.
> > Any advice appreciated.
> > Alice van Rensburg
> >
>
>|||Managed to resolve this issue - seems like one of the dbs still had a
non-existing Windows NT user as dbowner. We detached all DBs, and reattached
them one by one, each time checking the owner and checking if DataBases
folder opens.
Regards
A
"Alice" wrote:
> Thanx for your reply - the interesting thing is that user sa did have access
> to all DBs when we last checked (in December) - something must have happened
> to change that, but we do not know what. Have checked - nothing else running
> on the SQL server. We are seriously considering uninstall and reinstall.
> "Uri Dimant" wrote:
> > >. We found that user
> > > sa did not have access to any DBs! --
> >
> > sa is a sysadmin and has acceess by default to all databases
> >
> > Is it poosible another actvities on the server?
> >
> >
> >
> > "Alice" <Alice@.discussions.microsoft.com> wrote in message
> > news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
> > > Hi, hope somebody can help - we have found a strange problem at one of our
> > > clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
> > > when they click the + on Databases on Enterprise manager, it hangs and
> > > also
> > > hangs the server (applications accessing the DB timeout). We found that
> > > user
> > > sa did not have access to any DBs! -- which we restored with
> > > sp_changedbowner
> > > - but still hangs! Query analyser also hangs when opening object browser.
> > > All
> > > other actions also very slow. Have also checked and switched off autoclose
> > > on
> > > all DBs.
> > > Could not yet determine how and exactly when this happened.
> > > Any advice appreciated.
> > > Alice van Rensburg
> > >
> >
> >
> >
Wednesday, March 21, 2012
Enterprise Manager Stops Responding
I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?
"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
> on the server via RDP, the server stops responding. At this time, when IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?
|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?
|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database
Cheers,
harry
|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>
>
|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...[vbcol=seagreen]
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?
"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
> on the server via RDP, the server stops responding. At this time, when IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?
|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?
|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database
Cheers,
harry
|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>
>
|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...[vbcol=seagreen]
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
Enterprise Manager Stops Responding
I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
> on the server via RDP, the server stops responding. At this time, when IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
--
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database
:)
Cheers,
harry|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> > I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> > Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> > Manager
> > on the server via RDP, the server stops responding. At this time, when
> > IRDP
> > another session I dont get the windows login screen...all I get is grey
> > screen and mouse pointer....it is as if the server is hung. Most of the
> > times, I have no other option than hard rebooting the server.
> >
> > What is wrong here?
>
>|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
--
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> When you reboot the server, do you see anything in the event log or SQL
>> Server error logs?
>> --
>> Aaron Bertrand
>> SQL Server MVP
>>
>>
>> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
>> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>> > I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187)
>> > on
>> > Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
>> > Manager
>> > on the server via RDP, the server stops responding. At this time, when
>> > IRDP
>> > another session I dont get the windows login screen...all I get is grey
>> > screen and mouse pointer....it is as if the server is hung. Most of
>> > the
>> > times, I have no other option than hard rebooting the server.
>> >
>> > What is wrong here?
>>sql
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
> on the server via RDP, the server stops responding. At this time, when IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
--
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database
:)
Cheers,
harry|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> > I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> > Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> > Manager
> > on the server via RDP, the server stops responding. At this time, when
> > IRDP
> > another session I dont get the windows login screen...all I get is grey
> > screen and mouse pointer....it is as if the server is hung. Most of the
> > times, I have no other option than hard rebooting the server.
> >
> > What is wrong here?
>
>|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
--
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> When you reboot the server, do you see anything in the event log or SQL
>> Server error logs?
>> --
>> Aaron Bertrand
>> SQL Server MVP
>>
>>
>> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
>> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>> > I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187)
>> > on
>> > Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
>> > Manager
>> > on the server via RDP, the server stops responding. At this time, when
>> > IRDP
>> > another session I dont get the windows login screen...all I get is grey
>> > screen and mouse pointer....it is as if the server is hung. Most of
>> > the
>> > times, I have no other option than hard rebooting the server.
>> >
>> > What is wrong here?
>>sql
Enterprise Manager Stops Responding
I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) o
n
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manage
r
> on the server via RDP, the server stops responding. At this time, when IRD
P
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database
Cheers,
harry|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>
>|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...[vbcol=seagreen]
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
>
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) o
n
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manage
r
> on the server via RDP, the server stops responding. At this time, when IRD
P
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database
Cheers,
harry|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>
>|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...[vbcol=seagreen]
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
>
Monday, March 19, 2012
Enterprise Manager reporting wrong OS memory (SQL 2000 SP4+)
I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The SQL Server instance is at SP4 with the
additional hot fix for the AWE memory problem.
We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still showing only 4 GB of RAM. Task Manager on
the server itself shows all 8 GB.
The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on. The startup log says AWE is enabled.
Still, EM shows only 4 GB of RAM. I have another instance on a non-clustered machine and it shows all 8 GB correctly.
Any ideas what the problem could be?
Thanks,
EdEd
Did you set up MAX Memory?
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed|||Hi Uri,
Yes, max memory is set. Here is ooutput of sp_configure for memory options:
name minimum maximum config_value run_value
awe enabled 0 1 1 1
max server memory (MB) 4 2147483647 6144 6144
min server memory (MB) 0 2147483647 0 0
"Uri Dimant" wrote:
> Ed
> Did you set up MAX Memory?
>|||Where exactly are you seeing this 4GB? What does sp_configure show for the
MAX Memory?
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed|||In Enterprise Manager, right-click on the instance.
On the General tab, the OS Memory: line shows 3839(MB)
The Memory tab shows range of 0 to 3839 MB.
in sp_configure, max server memory (MB) is 6144
"Andrew J. Kelly" wrote:
> Where exactly are you seeing this 4GB? What does sp_configure show for the
> MAX Memory?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>|||It sounds like either the hotfix did not succeed or you applied the wrong
one. If you run xp_msver do you see the proper version for that hotfix? Is
this Enterprise Edition of SQL Server? This was on a cluster. Did the
hotfix get applied to both nodes?
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
> In Enterprise Manager, right-click on the instance.
> On the General tab, the OS Memory: line shows 3839(MB)
> The Memory tab shows range of 0 to 3839 MB.
> in sp_configure, max server memory (MB) is 6144
> "Andrew J. Kelly" wrote:
>> Where exactly are you seeing this 4GB? What does sp_configure show for
>> the
>> MAX Memory?
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors|||Hi Andrew,
Results from xp_msver:
Index Name Internal_Value Character_Value
1 ProductName Microsoft SQL Server
2 ProductVersion 524288 8.00.2187
3 Language 1033 English (United States)
4 Platform NT INTEL X86
5 Comments NT INTEL X86
6 CompanyName Microsoft Corporation
7 FileDescription SQL Server Windows NT
8 FileVersion 2000.080.2187.00
9 InternalName SQLSERVR
10 LegalCopyright © 1988-2004 Microsoft Corp. All rights reserved.
11 LegalTrademarks Microsoft® is a registered trademark of Microsoft
Corporation. Windows(TM) is a trademark of Microsoft Corporation
12 OriginalFilename SQLSERVR.EXE
13 PrivateBuild
14 SpecialBuild 143327232
15 WindowsVersion 248381957 5.2 (3790)
16 ProcessorCount 4 4
17 ProcessorActiveMask 15 0000000f
18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM
19 PhysicalMemory 3839 3839 (4025999360)
20 Product ID
The hotfix was applied. So far as I know, it was successful (no errors).
It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
this version for clustering).
This is what is driving me nuts. Everything looks right, but SQL Server is
not seeing all the memory.
"Andrew J. Kelly" wrote:
> It sounds like either the hotfix did not succeed or you applied the wrong
> one. If you run xp_msver do you see the proper version for that hotfix? Is
> this Enterprise Edition of SQL Server? This was on a cluster. Did the
> hotfix get applied to both nodes?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
> > In Enterprise Manager, right-click on the instance.
> > On the General tab, the OS Memory: line shows 3839(MB)
> > The Memory tab shows range of 0 to 3839 MB.
> > in sp_configure, max server memory (MB) is 6144
> >
> > "Andrew J. Kelly" wrote:
> >
> >> Where exactly are you seeing this 4GB? What does sp_configure show for
> >> the
> >> MAX Memory?
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >> Solid Quality Mentors
> >>
>|||OK well you actually have the Cumulative Update not just the hotfix but it
still should contain it as far as I know. What do the perfmon counters for
SQL Memory Target and Total memory show? If they show the 6GB then it
sounds like a bug in the gui. You may need to contact PSS if perfmon or
DBCC MEMORYSTATUS are not showing the right amount.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:9D711AC5-1218-42B4-825F-6F8BF60B35CE@.microsoft.com...
> Hi Andrew,
> Results from xp_msver:
> Index Name Internal_Value Character_Value
> 1 ProductName Microsoft SQL Server
> 2 ProductVersion 524288 8.00.2187
> 3 Language 1033 English (United States)
> 4 Platform NT INTEL X86
> 5 Comments NT INTEL X86
> 6 CompanyName Microsoft Corporation
> 7 FileDescription SQL Server Windows NT
> 8 FileVersion 2000.080.2187.00
> 9 InternalName SQLSERVR
> 10 LegalCopyright © 1988-2004 Microsoft Corp. All rights reserved.
> 11 LegalTrademarks Microsoft® is a registered trademark of Microsoft
> Corporation. Windows(TM) is a trademark of Microsoft Corporation
> 12 OriginalFilename SQLSERVR.EXE
> 13 PrivateBuild
> 14 SpecialBuild 143327232
> 15 WindowsVersion 248381957 5.2 (3790)
> 16 ProcessorCount 4 4
> 17 ProcessorActiveMask 15 0000000f
> 18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM
> 19 PhysicalMemory 3839 3839 (4025999360)
> 20 Product ID
> The hotfix was applied. So far as I know, it was successful (no errors).
> It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
> this version for clustering).
> This is what is driving me nuts. Everything looks right, but SQL Server
> is
> not seeing all the memory.
> "Andrew J. Kelly" wrote:
>> It sounds like either the hotfix did not succeed or you applied the wrong
>> one. If you run xp_msver do you see the proper version for that hotfix?
>> Is
>> this Enterprise Edition of SQL Server? This was on a cluster. Did the
>> hotfix get applied to both nodes?
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "Ed" <Ed@.discussions.microsoft.com> wrote in message
>> news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
>> > In Enterprise Manager, right-click on the instance.
>> > On the General tab, the OS Memory: line shows 3839(MB)
>> > The Memory tab shows range of 0 to 3839 MB.
>> > in sp_configure, max server memory (MB) is 6144
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> Where exactly are you seeing this 4GB? What does sp_configure show
>> >> for
>> >> the
>> >> MAX Memory?
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >> Solid Quality Mentors
>> >>
>>|||Andrew,
Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a UI
issue. I have another server (non-clustered) at the same SQL 8,00.2187 (SP4)
version with 8 GB and it is working properly. I suspect the problem is
related to clustering, but I do not know enough about that to pinpoint the
cause. I will continue to investigate.
Thanks for the DBCC MEMORYSTATUS idea. I did not know about this function.
It does not appear in Help.
Ed
"Andrew J. Kelly" wrote:
> OK well you actually have the Cumulative Update not just the hotfix but it
> still should contain it as far as I know. What do the perfmon counters for
> SQL Memory Target and Total memory show? If they show the 6GB then it
> sounds like a bug in the gui. You may need to contact PSS if perfmon or
> DBCC MEMORYSTATUS are not showing the right amount.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>|||It certainly sounds like the Hoxfix didn't work properly. I would give MS a
call.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:3C36BE31-DFED-469C-BC93-27808286BEB5@.microsoft.com...
> Andrew,
> Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a
> UI
> issue. I have another server (non-clustered) at the same SQL 8,00.2187
> (SP4)
> version with 8 GB and it is working properly. I suspect the problem is
> related to clustering, but I do not know enough about that to pinpoint the
> cause. I will continue to investigate.
> Thanks for the DBCC MEMORYSTATUS idea. I did not know about this
> function.
> It does not appear in Help.
> Ed
> "Andrew J. Kelly" wrote:
>> OK well you actually have the Cumulative Update not just the hotfix but
>> it
>> still should contain it as far as I know. What do the perfmon counters
>> for
>> SQL Memory Target and Total memory show? If they show the 6GB then it
>> sounds like a bug in the gui. You may need to contact PSS if perfmon or
>> DBCC MEMORYSTATUS are not showing the right amount.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors|||Right. I've pretty much come to the same conclusion.
Thanks for the help.
Ed
"Andrew J. Kelly" wrote:
> It certainly sounds like the Hoxfix didn't work properly. I would give MS a
> call.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>|||The problem has been solved. It turns out that we had to stop and restart
the cluster in order for SQL Server to see the extra memory. We had to wait
until Friday night to do it.
When we added the memory, we failed over the SQL Server service, took the
machine down, added the memory and brought the machine back up again. The
cluster was never stopped.
Thanks again for your help.
Ed
"Andrew J. Kelly" wrote:
> It certainly sounds like the Hoxfix didn't work properly. I would give MS a
> call.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
additional hot fix for the AWE memory problem.
We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still showing only 4 GB of RAM. Task Manager on
the server itself shows all 8 GB.
The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on. The startup log says AWE is enabled.
Still, EM shows only 4 GB of RAM. I have another instance on a non-clustered machine and it shows all 8 GB correctly.
Any ideas what the problem could be?
Thanks,
EdEd
Did you set up MAX Memory?
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed|||Hi Uri,
Yes, max memory is set. Here is ooutput of sp_configure for memory options:
name minimum maximum config_value run_value
awe enabled 0 1 1 1
max server memory (MB) 4 2147483647 6144 6144
min server memory (MB) 0 2147483647 0 0
"Uri Dimant" wrote:
> Ed
> Did you set up MAX Memory?
>|||Where exactly are you seeing this 4GB? What does sp_configure show for the
MAX Memory?
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed|||In Enterprise Manager, right-click on the instance.
On the General tab, the OS Memory: line shows 3839(MB)
The Memory tab shows range of 0 to 3839 MB.
in sp_configure, max server memory (MB) is 6144
"Andrew J. Kelly" wrote:
> Where exactly are you seeing this 4GB? What does sp_configure show for the
> MAX Memory?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>|||It sounds like either the hotfix did not succeed or you applied the wrong
one. If you run xp_msver do you see the proper version for that hotfix? Is
this Enterprise Edition of SQL Server? This was on a cluster. Did the
hotfix get applied to both nodes?
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
> In Enterprise Manager, right-click on the instance.
> On the General tab, the OS Memory: line shows 3839(MB)
> The Memory tab shows range of 0 to 3839 MB.
> in sp_configure, max server memory (MB) is 6144
> "Andrew J. Kelly" wrote:
>> Where exactly are you seeing this 4GB? What does sp_configure show for
>> the
>> MAX Memory?
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors|||Hi Andrew,
Results from xp_msver:
Index Name Internal_Value Character_Value
1 ProductName Microsoft SQL Server
2 ProductVersion 524288 8.00.2187
3 Language 1033 English (United States)
4 Platform NT INTEL X86
5 Comments NT INTEL X86
6 CompanyName Microsoft Corporation
7 FileDescription SQL Server Windows NT
8 FileVersion 2000.080.2187.00
9 InternalName SQLSERVR
10 LegalCopyright © 1988-2004 Microsoft Corp. All rights reserved.
11 LegalTrademarks Microsoft® is a registered trademark of Microsoft
Corporation. Windows(TM) is a trademark of Microsoft Corporation
12 OriginalFilename SQLSERVR.EXE
13 PrivateBuild
14 SpecialBuild 143327232
15 WindowsVersion 248381957 5.2 (3790)
16 ProcessorCount 4 4
17 ProcessorActiveMask 15 0000000f
18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM
19 PhysicalMemory 3839 3839 (4025999360)
20 Product ID
The hotfix was applied. So far as I know, it was successful (no errors).
It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
this version for clustering).
This is what is driving me nuts. Everything looks right, but SQL Server is
not seeing all the memory.
"Andrew J. Kelly" wrote:
> It sounds like either the hotfix did not succeed or you applied the wrong
> one. If you run xp_msver do you see the proper version for that hotfix? Is
> this Enterprise Edition of SQL Server? This was on a cluster. Did the
> hotfix get applied to both nodes?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
> > In Enterprise Manager, right-click on the instance.
> > On the General tab, the OS Memory: line shows 3839(MB)
> > The Memory tab shows range of 0 to 3839 MB.
> > in sp_configure, max server memory (MB) is 6144
> >
> > "Andrew J. Kelly" wrote:
> >
> >> Where exactly are you seeing this 4GB? What does sp_configure show for
> >> the
> >> MAX Memory?
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >> Solid Quality Mentors
> >>
>|||OK well you actually have the Cumulative Update not just the hotfix but it
still should contain it as far as I know. What do the perfmon counters for
SQL Memory Target and Total memory show? If they show the 6GB then it
sounds like a bug in the gui. You may need to contact PSS if perfmon or
DBCC MEMORYSTATUS are not showing the right amount.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:9D711AC5-1218-42B4-825F-6F8BF60B35CE@.microsoft.com...
> Hi Andrew,
> Results from xp_msver:
> Index Name Internal_Value Character_Value
> 1 ProductName Microsoft SQL Server
> 2 ProductVersion 524288 8.00.2187
> 3 Language 1033 English (United States)
> 4 Platform NT INTEL X86
> 5 Comments NT INTEL X86
> 6 CompanyName Microsoft Corporation
> 7 FileDescription SQL Server Windows NT
> 8 FileVersion 2000.080.2187.00
> 9 InternalName SQLSERVR
> 10 LegalCopyright © 1988-2004 Microsoft Corp. All rights reserved.
> 11 LegalTrademarks Microsoft® is a registered trademark of Microsoft
> Corporation. Windows(TM) is a trademark of Microsoft Corporation
> 12 OriginalFilename SQLSERVR.EXE
> 13 PrivateBuild
> 14 SpecialBuild 143327232
> 15 WindowsVersion 248381957 5.2 (3790)
> 16 ProcessorCount 4 4
> 17 ProcessorActiveMask 15 0000000f
> 18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM
> 19 PhysicalMemory 3839 3839 (4025999360)
> 20 Product ID
> The hotfix was applied. So far as I know, it was successful (no errors).
> It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
> this version for clustering).
> This is what is driving me nuts. Everything looks right, but SQL Server
> is
> not seeing all the memory.
> "Andrew J. Kelly" wrote:
>> It sounds like either the hotfix did not succeed or you applied the wrong
>> one. If you run xp_msver do you see the proper version for that hotfix?
>> Is
>> this Enterprise Edition of SQL Server? This was on a cluster. Did the
>> hotfix get applied to both nodes?
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "Ed" <Ed@.discussions.microsoft.com> wrote in message
>> news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
>> > In Enterprise Manager, right-click on the instance.
>> > On the General tab, the OS Memory: line shows 3839(MB)
>> > The Memory tab shows range of 0 to 3839 MB.
>> > in sp_configure, max server memory (MB) is 6144
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> Where exactly are you seeing this 4GB? What does sp_configure show
>> >> for
>> >> the
>> >> MAX Memory?
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >> Solid Quality Mentors
>> >>
>>|||Andrew,
Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a UI
issue. I have another server (non-clustered) at the same SQL 8,00.2187 (SP4)
version with 8 GB and it is working properly. I suspect the problem is
related to clustering, but I do not know enough about that to pinpoint the
cause. I will continue to investigate.
Thanks for the DBCC MEMORYSTATUS idea. I did not know about this function.
It does not appear in Help.
Ed
"Andrew J. Kelly" wrote:
> OK well you actually have the Cumulative Update not just the hotfix but it
> still should contain it as far as I know. What do the perfmon counters for
> SQL Memory Target and Total memory show? If they show the 6GB then it
> sounds like a bug in the gui. You may need to contact PSS if perfmon or
> DBCC MEMORYSTATUS are not showing the right amount.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>|||It certainly sounds like the Hoxfix didn't work properly. I would give MS a
call.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:3C36BE31-DFED-469C-BC93-27808286BEB5@.microsoft.com...
> Andrew,
> Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a
> UI
> issue. I have another server (non-clustered) at the same SQL 8,00.2187
> (SP4)
> version with 8 GB and it is working properly. I suspect the problem is
> related to clustering, but I do not know enough about that to pinpoint the
> cause. I will continue to investigate.
> Thanks for the DBCC MEMORYSTATUS idea. I did not know about this
> function.
> It does not appear in Help.
> Ed
> "Andrew J. Kelly" wrote:
>> OK well you actually have the Cumulative Update not just the hotfix but
>> it
>> still should contain it as far as I know. What do the perfmon counters
>> for
>> SQL Memory Target and Total memory show? If they show the 6GB then it
>> sounds like a bug in the gui. You may need to contact PSS if perfmon or
>> DBCC MEMORYSTATUS are not showing the right amount.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors|||Right. I've pretty much come to the same conclusion.
Thanks for the help.
Ed
"Andrew J. Kelly" wrote:
> It certainly sounds like the Hoxfix didn't work properly. I would give MS a
> call.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>|||The problem has been solved. It turns out that we had to stop and restart
the cluster in order for SQL Server to see the extra memory. We had to wait
until Friday night to do it.
When we added the memory, we failed over the SQL Server service, took the
machine down, added the memory and brought the machine back up again. The
cluster was never stopped.
Thanks again for your help.
Ed
"Andrew J. Kelly" wrote:
> It certainly sounds like the Hoxfix didn't work properly. I would give MS a
> call.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
Enterprise Manager reporting wrong OS memory (SQL 2000 SP4+)
I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The SQL Server instance is at SP4 with the
additional hot fix for the AWE memory problem.
We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still showing only 4 GB of RAM. Task Manager on
the server itself shows all 8 GB.
The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on. The startup log says AWE is enabled.
Still, EM shows only 4 GB of RAM. I have another instance on a non-clustered machine and it shows all 8 GB correctly.
Any ideas what the problem could be?
Thanks,
Ed
Ed
Did you set up MAX Memory?
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed
|||Hi Uri,
Yes, max memory is set. Here is ooutput of sp_configure for memory options:
nameminimummaximumconfig_valuerun_value
awe enabled0111
max server memory (MB)4214748364761446144
min server memory (MB)0214748364700
"Uri Dimant" wrote:
> Ed
> Did you set up MAX Memory?
>
|||Where exactly are you seeing this 4GB? What does sp_configure show for the
MAX Memory?
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed
|||In Enterprise Manager, right-click on the instance.
On the General tab, the OS Memory: line shows 3839(MB)
The Memory tab shows range of 0 to 3839 MB.
in sp_configure, max server memory (MB) is 6144
"Andrew J. Kelly" wrote:
> Where exactly are you seeing this 4GB? What does sp_configure show for the
> MAX Memory?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
|||It sounds like either the hotfix did not succeed or you applied the wrong
one. If you run xp_msver do you see the proper version for that hotfix? Is
this Enterprise Edition of SQL Server? This was on a cluster. Did the
hotfix get applied to both nodes?
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...[vbcol=seagreen]
> In Enterprise Manager, right-click on the instance.
> On the General tab, the OS Memory: line shows 3839(MB)
> The Memory tab shows range of 0 to 3839 MB.
> in sp_configure, max server memory (MB) is 6144
> "Andrew J. Kelly" wrote:
|||Hi Andrew,
Results from xp_msver:
IndexNameInternal_ValueCharacter_Value
1ProductNameMicrosoft SQL Server
2ProductVersion5242888.00.2187
3Language1033English (United States)
4PlatformNT INTEL X86
5CommentsNT INTEL X86
6CompanyNameMicrosoft Corporation
7FileDescriptionSQL Server Windows NT
8FileVersion2000.080.2187.00
9InternalNameSQLSERVR
10LegalCopyright? 1988-2004 Microsoft Corp. All rights reserved.
11LegalTrademarksMicrosoft? is a registered trademark of Microsoft
Corporation. Windows(TM) is a trademark of Microsoft Corporation
12OriginalFilenameSQLSERVR.EXE
13PrivateBuild
14SpecialBuild143327232
15WindowsVersion2483819575.2 (3790)
16ProcessorCount44
17ProcessorActiveMask150000000f
18ProcessorType586PROCESSOR_INTEL_PENTIUM
19PhysicalMemory38393839 (4025999360)
20Product ID
The hotfix was applied. So far as I know, it was successful (no errors).
It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
this version for clustering).
This is what is driving me nuts. Everything looks right, but SQL Server is
not seeing all the memory.
"Andrew J. Kelly" wrote:
> It sounds like either the hotfix did not succeed or you applied the wrong
> one. If you run xp_msver do you see the proper version for that hotfix? Is
> this Enterprise Edition of SQL Server? This was on a cluster. Did the
> hotfix get applied to both nodes?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
>
|||OK well you actually have the Cumulative Update not just the hotfix but it
still should contain it as far as I know. What do the perfmon counters for
SQL Memory Target and Total memory show? If they show the 6GB then it
sounds like a bug in the gui. You may need to contact PSS if perfmon or
DBCC MEMORYSTATUS are not showing the right amount.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:9D711AC5-1218-42B4-825F-6F8BF60B35CE@.microsoft.com...[vbcol=seagreen]
> Hi Andrew,
> Results from xp_msver:
> Index Name Internal_Value Character_Value
> 1 ProductName Microsoft SQL Server
> 2 ProductVersion 524288 8.00.2187
> 3 Language 1033 English (United States)
> 4 Platform NT INTEL X86
> 5 Comments NT INTEL X86
> 6 CompanyName Microsoft Corporation
> 7 FileDescription SQL Server Windows NT
> 8 FileVersion 2000.080.2187.00
> 9 InternalName SQLSERVR
> 10 LegalCopyright ? 1988-2004 Microsoft Corp. All rights reserved.
> 11 LegalTrademarks Microsoft? is a registered trademark of Microsoft
> Corporation. Windows(TM) is a trademark of Microsoft Corporation
> 12 OriginalFilename SQLSERVR.EXE
> 13 PrivateBuild
> 14 SpecialBuild 143327232
> 15 WindowsVersion 248381957 5.2 (3790)
> 16 ProcessorCount 4 4
> 17 ProcessorActiveMask 15 0000000f
> 18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM
> 19 PhysicalMemory 3839 3839 (4025999360)
> 20 Product ID
> The hotfix was applied. So far as I know, it was successful (no errors).
> It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
> this version for clustering).
> This is what is driving me nuts. Everything looks right, but SQL Server
> is
> not seeing all the memory.
> "Andrew J. Kelly" wrote:
|||Andrew,
Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a UI
issue. I have another server (non-clustered) at the same SQL 8,00.2187 (SP4)
version with 8 GB and it is working properly. I suspect the problem is
related to clustering, but I do not know enough about that to pinpoint the
cause. I will continue to investigate.
Thanks for the DBCC MEMORYSTATUS idea. I did not know about this function.
It does not appear in Help.
Ed
"Andrew J. Kelly" wrote:
> OK well you actually have the Cumulative Update not just the hotfix but it
> still should contain it as far as I know. What do the perfmon counters for
> SQL Memory Target and Total memory show? If they show the 6GB then it
> sounds like a bug in the gui. You may need to contact PSS if perfmon or
> DBCC MEMORYSTATUS are not showing the right amount.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
|||It certainly sounds like the Hoxfix didn't work properly. I would give MS a
call.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:3C36BE31-DFED-469C-BC93-27808286BEB5@.microsoft.com...[vbcol=seagreen]
> Andrew,
> Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a
> UI
> issue. I have another server (non-clustered) at the same SQL 8,00.2187
> (SP4)
> version with 8 GB and it is working properly. I suspect the problem is
> related to clustering, but I do not know enough about that to pinpoint the
> cause. I will continue to investigate.
> Thanks for the DBCC MEMORYSTATUS idea. I did not know about this
> function.
> It does not appear in Help.
> Ed
> "Andrew J. Kelly" wrote:
additional hot fix for the AWE memory problem.
We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still showing only 4 GB of RAM. Task Manager on
the server itself shows all 8 GB.
The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on. The startup log says AWE is enabled.
Still, EM shows only 4 GB of RAM. I have another instance on a non-clustered machine and it shows all 8 GB correctly.
Any ideas what the problem could be?
Thanks,
Ed
Ed
Did you set up MAX Memory?
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed
|||Hi Uri,
Yes, max memory is set. Here is ooutput of sp_configure for memory options:
nameminimummaximumconfig_valuerun_value
awe enabled0111
max server memory (MB)4214748364761446144
min server memory (MB)0214748364700
"Uri Dimant" wrote:
> Ed
> Did you set up MAX Memory?
>
|||Where exactly are you seeing this 4GB? What does sp_configure show for the
MAX Memory?
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed
|||In Enterprise Manager, right-click on the instance.
On the General tab, the OS Memory: line shows 3839(MB)
The Memory tab shows range of 0 to 3839 MB.
in sp_configure, max server memory (MB) is 6144
"Andrew J. Kelly" wrote:
> Where exactly are you seeing this 4GB? What does sp_configure show for the
> MAX Memory?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
|||It sounds like either the hotfix did not succeed or you applied the wrong
one. If you run xp_msver do you see the proper version for that hotfix? Is
this Enterprise Edition of SQL Server? This was on a cluster. Did the
hotfix get applied to both nodes?
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...[vbcol=seagreen]
> In Enterprise Manager, right-click on the instance.
> On the General tab, the OS Memory: line shows 3839(MB)
> The Memory tab shows range of 0 to 3839 MB.
> in sp_configure, max server memory (MB) is 6144
> "Andrew J. Kelly" wrote:
|||Hi Andrew,
Results from xp_msver:
IndexNameInternal_ValueCharacter_Value
1ProductNameMicrosoft SQL Server
2ProductVersion5242888.00.2187
3Language1033English (United States)
4PlatformNT INTEL X86
5CommentsNT INTEL X86
6CompanyNameMicrosoft Corporation
7FileDescriptionSQL Server Windows NT
8FileVersion2000.080.2187.00
9InternalNameSQLSERVR
10LegalCopyright? 1988-2004 Microsoft Corp. All rights reserved.
11LegalTrademarksMicrosoft? is a registered trademark of Microsoft
Corporation. Windows(TM) is a trademark of Microsoft Corporation
12OriginalFilenameSQLSERVR.EXE
13PrivateBuild
14SpecialBuild143327232
15WindowsVersion2483819575.2 (3790)
16ProcessorCount44
17ProcessorActiveMask150000000f
18ProcessorType586PROCESSOR_INTEL_PENTIUM
19PhysicalMemory38393839 (4025999360)
20Product ID
The hotfix was applied. So far as I know, it was successful (no errors).
It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
this version for clustering).
This is what is driving me nuts. Everything looks right, but SQL Server is
not seeing all the memory.
"Andrew J. Kelly" wrote:
> It sounds like either the hotfix did not succeed or you applied the wrong
> one. If you run xp_msver do you see the proper version for that hotfix? Is
> this Enterprise Edition of SQL Server? This was on a cluster. Did the
> hotfix get applied to both nodes?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
>
|||OK well you actually have the Cumulative Update not just the hotfix but it
still should contain it as far as I know. What do the perfmon counters for
SQL Memory Target and Total memory show? If they show the 6GB then it
sounds like a bug in the gui. You may need to contact PSS if perfmon or
DBCC MEMORYSTATUS are not showing the right amount.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:9D711AC5-1218-42B4-825F-6F8BF60B35CE@.microsoft.com...[vbcol=seagreen]
> Hi Andrew,
> Results from xp_msver:
> Index Name Internal_Value Character_Value
> 1 ProductName Microsoft SQL Server
> 2 ProductVersion 524288 8.00.2187
> 3 Language 1033 English (United States)
> 4 Platform NT INTEL X86
> 5 Comments NT INTEL X86
> 6 CompanyName Microsoft Corporation
> 7 FileDescription SQL Server Windows NT
> 8 FileVersion 2000.080.2187.00
> 9 InternalName SQLSERVR
> 10 LegalCopyright ? 1988-2004 Microsoft Corp. All rights reserved.
> 11 LegalTrademarks Microsoft? is a registered trademark of Microsoft
> Corporation. Windows(TM) is a trademark of Microsoft Corporation
> 12 OriginalFilename SQLSERVR.EXE
> 13 PrivateBuild
> 14 SpecialBuild 143327232
> 15 WindowsVersion 248381957 5.2 (3790)
> 16 ProcessorCount 4 4
> 17 ProcessorActiveMask 15 0000000f
> 18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM
> 19 PhysicalMemory 3839 3839 (4025999360)
> 20 Product ID
> The hotfix was applied. So far as I know, it was successful (no errors).
> It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
> this version for clustering).
> This is what is driving me nuts. Everything looks right, but SQL Server
> is
> not seeing all the memory.
> "Andrew J. Kelly" wrote:
|||Andrew,
Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a UI
issue. I have another server (non-clustered) at the same SQL 8,00.2187 (SP4)
version with 8 GB and it is working properly. I suspect the problem is
related to clustering, but I do not know enough about that to pinpoint the
cause. I will continue to investigate.
Thanks for the DBCC MEMORYSTATUS idea. I did not know about this function.
It does not appear in Help.
Ed
"Andrew J. Kelly" wrote:
> OK well you actually have the Cumulative Update not just the hotfix but it
> still should contain it as far as I know. What do the perfmon counters for
> SQL Memory Target and Total memory show? If they show the 6GB then it
> sounds like a bug in the gui. You may need to contact PSS if perfmon or
> DBCC MEMORYSTATUS are not showing the right amount.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
|||It certainly sounds like the Hoxfix didn't work properly. I would give MS a
call.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:3C36BE31-DFED-469C-BC93-27808286BEB5@.microsoft.com...[vbcol=seagreen]
> Andrew,
> Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a
> UI
> issue. I have another server (non-clustered) at the same SQL 8,00.2187
> (SP4)
> version with 8 GB and it is working properly. I suspect the problem is
> related to clustering, but I do not know enough about that to pinpoint the
> cause. I will continue to investigate.
> Thanks for the DBCC MEMORYSTATUS idea. I did not know about this
> function.
> It does not appear in Help.
> Ed
> "Andrew J. Kelly" wrote:
Wednesday, March 7, 2012
Enterprise Manager field > 900 chars not displaying post SP4
I think this started happening post SP4.
I have an nvarchar(4000) field. If I query the table in Enterprise Manager,
the data for the field only displays in rows where the value is 900 chars or
less. Otherwise, the field looks empty, but when I click in it and type, I
get a popup that says "Cannot edit this field."
I can query the data, so I know it's there, but it's annoying not to see it
in the results.
Has anyone else noticed this?
<Cliff>
Enterprise Manager is not meant to be a data editor. May I suggest that you
use Query Analyzer (and Transact-SQL statements to edit the data)? The
other option is to create a GUI that you can use to edit the data within
your databases.
Keith
"Cliff Morrison" <CliffMorrison@.discussions.microsoft.com> wrote in message
news:3C026C09-A968-466A-B1D0-FAE7EC4EACE5@.microsoft.com...
>I think this started happening post SP4.
> I have an nvarchar(4000) field. If I query the table in Enterprise
> Manager,
> the data for the field only displays in rows where the value is 900 chars
> or
> less. Otherwise, the field looks empty, but when I click in it and type,
> I
> get a popup that says "Cannot edit this field."
> I can query the data, so I know it's there, but it's annoying not to see
> it
> in the results.
> Has anyone else noticed this?
> <Cliff>
|||I'm not really trying to edit. The only reason I did in my example was to
show that something strange was happening with the field.
I do think I should be able to visually verify in Enterprise Manager query
results that data is in a field, regardless of whether that data is less than
or equal to 900 characters in length.
<Cliff>
"Keith Kratochvil" wrote:
> Enterprise Manager is not meant to be a data editor. May I suggest that you
> use Query Analyzer (and Transact-SQL statements to edit the data)? The
> other option is to create a GUI that you can use to edit the data within
> your databases.
> --
> Keith
|||I am having the same problem, except it is happening with text fields and a
char(1024) field. Shorter fields and a varchar(4096) field seem to show up
just fine. EM used to display the data in these fields before I upgraded to
SP4. What is going on?
Rob
"Cliff Morrison" wrote:
> I'm not really trying to edit. The only reason I did in my example was to
> show that something strange was happening with the field.
> I do think I should be able to visually verify in Enterprise Manager query
> results that data is in a field, regardless of whether that data is less than
> or equal to 900 characters in length.
> <Cliff>
> "Keith Kratochvil" wrote:
>
|||Or check out AgileInfoSoftware DataStudio for editing data. You can directly
update table content, and there is no known limit for the length of
character.
John King
http://www.agileinfollc.com
"Rob Drollinger" <RobDrollinger@.discussions.microsoft.com> wrote in message
news:993820FF-C681-4E34-8344-BBC28C8CF008@.microsoft.com...[vbcol=seagreen]
>I am having the same problem, except it is happening with text fields and a
> char(1024) field. Shorter fields and a varchar(4096) field seem to show
> up
> just fine. EM used to display the data in these fields before I upgraded
> to
> SP4. What is going on?
> Rob
>
> "Cliff Morrison" wrote:
I have an nvarchar(4000) field. If I query the table in Enterprise Manager,
the data for the field only displays in rows where the value is 900 chars or
less. Otherwise, the field looks empty, but when I click in it and type, I
get a popup that says "Cannot edit this field."
I can query the data, so I know it's there, but it's annoying not to see it
in the results.
Has anyone else noticed this?
<Cliff>
Enterprise Manager is not meant to be a data editor. May I suggest that you
use Query Analyzer (and Transact-SQL statements to edit the data)? The
other option is to create a GUI that you can use to edit the data within
your databases.
Keith
"Cliff Morrison" <CliffMorrison@.discussions.microsoft.com> wrote in message
news:3C026C09-A968-466A-B1D0-FAE7EC4EACE5@.microsoft.com...
>I think this started happening post SP4.
> I have an nvarchar(4000) field. If I query the table in Enterprise
> Manager,
> the data for the field only displays in rows where the value is 900 chars
> or
> less. Otherwise, the field looks empty, but when I click in it and type,
> I
> get a popup that says "Cannot edit this field."
> I can query the data, so I know it's there, but it's annoying not to see
> it
> in the results.
> Has anyone else noticed this?
> <Cliff>
|||I'm not really trying to edit. The only reason I did in my example was to
show that something strange was happening with the field.
I do think I should be able to visually verify in Enterprise Manager query
results that data is in a field, regardless of whether that data is less than
or equal to 900 characters in length.
<Cliff>
"Keith Kratochvil" wrote:
> Enterprise Manager is not meant to be a data editor. May I suggest that you
> use Query Analyzer (and Transact-SQL statements to edit the data)? The
> other option is to create a GUI that you can use to edit the data within
> your databases.
> --
> Keith
|||I am having the same problem, except it is happening with text fields and a
char(1024) field. Shorter fields and a varchar(4096) field seem to show up
just fine. EM used to display the data in these fields before I upgraded to
SP4. What is going on?
Rob
"Cliff Morrison" wrote:
> I'm not really trying to edit. The only reason I did in my example was to
> show that something strange was happening with the field.
> I do think I should be able to visually verify in Enterprise Manager query
> results that data is in a field, regardless of whether that data is less than
> or equal to 900 characters in length.
> <Cliff>
> "Keith Kratochvil" wrote:
>
|||Or check out AgileInfoSoftware DataStudio for editing data. You can directly
update table content, and there is no known limit for the length of
character.
John King
http://www.agileinfollc.com
"Rob Drollinger" <RobDrollinger@.discussions.microsoft.com> wrote in message
news:993820FF-C681-4E34-8344-BBC28C8CF008@.microsoft.com...[vbcol=seagreen]
>I am having the same problem, except it is happening with text fields and a
> char(1024) field. Shorter fields and a varchar(4096) field seem to show
> up
> just fine. EM used to display the data in these fields before I upgraded
> to
> SP4. What is going on?
> Rob
>
> "Cliff Morrison" wrote:
Wednesday, February 15, 2012
Enterprise Edition
Please help.
I have a SQL2K EE SP 3 runing on WIN2k SP4 I uninstall
and renistall a Standard version of SQL 2K. However it
does not allow restore of previous system databases. What
can I do to overcome this. please?.
Urgent
Regards
Timi.Timi,
Did you apply SP3 to your Standard Edition?
Russell Fields
"Olutimi" <anonymous@.discussions.microsoft.com> wrote in message
news:291701c3fc9c$ff121a20$a001280a@.phx.gbl...
> Please help.
> I have a SQL2K EE SP 3 runing on WIN2k SP4 I uninstall
> and renistall a Standard version of SQL 2K. However it
> does not allow restore of previous system databases. What
> can I do to overcome this. please?.
> Urgent
> Regards
> Timi.|||Could you be running into this problem:
264474 PRB: System Database Backups Cannot be Restored on a Different Build
http://support.microsoft.com/?id=264474
Rand
This posting is provided "as is" with no warranties and confers no rights.
I have a SQL2K EE SP 3 runing on WIN2k SP4 I uninstall
and renistall a Standard version of SQL 2K. However it
does not allow restore of previous system databases. What
can I do to overcome this. please?.
Urgent
Regards
Timi.Timi,
Did you apply SP3 to your Standard Edition?
Russell Fields
"Olutimi" <anonymous@.discussions.microsoft.com> wrote in message
news:291701c3fc9c$ff121a20$a001280a@.phx.gbl...
> Please help.
> I have a SQL2K EE SP 3 runing on WIN2k SP4 I uninstall
> and renistall a Standard version of SQL 2K. However it
> does not allow restore of previous system databases. What
> can I do to overcome this. please?.
> Urgent
> Regards
> Timi.|||Could you be running into this problem:
264474 PRB: System Database Backups Cannot be Restored on a Different Build
http://support.microsoft.com/?id=264474
Rand
This posting is provided "as is" with no warranties and confers no rights.
Enterprise Edition
Please help.
I have a SQL2K EE SP 3 runing on WIN2k SP4 I uninstall
and renistall a Standard version of SQL 2K. However it
does not allow restore of previous system databases. What
can I do to overcome this. please?.
Urgent
Regards
Timi.Timi,
Did you apply SP3 to your Standard Edition?
Russell Fields
"Olutimi" <anonymous@.discussions.microsoft.com> wrote in message
news:291701c3fc9c$ff121a20$a001280a@.phx.gbl...
> Please help.
> I have a SQL2K EE SP 3 runing on WIN2k SP4 I uninstall
> and renistall a Standard version of SQL 2K. However it
> does not allow restore of previous system databases. What
> can I do to overcome this. please?.
> Urgent
> Regards
> Timi.|||Could you be running into this problem:
264474 PRB: System Database Backups Cannot be Restored on a Different Build
http://support.microsoft.com/?id=264474
Rand
This posting is provided "as is" with no warranties and confers no rights.
I have a SQL2K EE SP 3 runing on WIN2k SP4 I uninstall
and renistall a Standard version of SQL 2K. However it
does not allow restore of previous system databases. What
can I do to overcome this. please?.
Urgent
Regards
Timi.Timi,
Did you apply SP3 to your Standard Edition?
Russell Fields
"Olutimi" <anonymous@.discussions.microsoft.com> wrote in message
news:291701c3fc9c$ff121a20$a001280a@.phx.gbl...
> Please help.
> I have a SQL2K EE SP 3 runing on WIN2k SP4 I uninstall
> and renistall a Standard version of SQL 2K. However it
> does not allow restore of previous system databases. What
> can I do to overcome this. please?.
> Urgent
> Regards
> Timi.|||Could you be running into this problem:
264474 PRB: System Database Backups Cannot be Restored on a Different Build
http://support.microsoft.com/?id=264474
Rand
This posting is provided "as is" with no warranties and confers no rights.
Subscribe to:
Posts (Atom)