Enterprise or not?

Dear ALL,
I'm going to install a new cluster (2 X HP DL380 , MSA1000 Storage) based on
Win 2003 R2 Enterprise and I 'd like to know if I have to install SQL SERVER
2005 Enterprise or standard version could be fine.
Regards
Alberto BrivioStandard will work on a two node cluster but you may loose some other
features you need. Check out the feature comparison in BOL.
--
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio
"Alberto Brivio" <a.brivio@.adb.it> wrote in message
news:uZci$GBPIHA.1208@.TK2MSFTNGP05.phx.gbl...
> Dear ALL,
> I'm going to install a new cluster (2 X HP DL380 , MSA1000 Storage) based
> on Win 2003 R2 Enterprise and I 'd like to know if I have to install SQL
> SERVER 2005 Enterprise or standard version could be fine.
>
> Regards
> Alberto Brivio
>|||You better determine your needs first...
--
Ekrem Önsoy
"Alberto Brivio" <a.brivio@.adb.it> wrote in message
news:uZci$GBPIHA.1208@.TK2MSFTNGP05.phx.gbl...
> Dear ALL,
> I'm going to install a new cluster (2 X HP DL380 , MSA1000 Storage) based
> on Win 2003 R2 Enterprise and I 'd like to know if I have to install SQL
> SERVER 2005 Enterprise or standard version could be fine.
>
> Regards
> Alberto Brivio
>|||Alberto,
With SQL2005 the version will depend on the number of CPU's rather than the
memory and of course the features you require. If your server has more than
4 CPU's and you want SQL to use them then you must use Enterprise.
Chris
"Alberto Brivio" <a.brivio@.adb.it> wrote in message
news:uZci$GBPIHA.1208@.TK2MSFTNGP05.phx.gbl...
> Dear ALL,
> I'm going to install a new cluster (2 X HP DL380 , MSA1000 Storage) based
> on Win 2003 R2 Enterprise and I 'd like to know if I have to install SQL
> SERVER 2005 Enterprise or standard version could be fine.
>
> Regards
> Alberto Brivio
>

Enterprise or not?

Dear ALL,
I'm going to install a new cluster (2 X HP DL380 , MSA1000 Storage) based on
Win 2003 R2 Enterprise and I 'd like to know if I have to install SQL SERVER
2005 Enterprise or standard version could be fine.
Regards
Alberto BrivioStandard will work on a two node cluster but you may loose some other
features you need. Check out the feature comparison in BOL.
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio
"Alberto Brivio" <a.brivio@.adb.it> wrote in message
news:uZci$GBPIHA.1208@.TK2MSFTNGP05.phx.gbl...
> Dear ALL,
> I'm going to install a new cluster (2 X HP DL380 , MSA1000 Storage) based
> on Win 2003 R2 Enterprise and I 'd like to know if I have to install SQL
> SERVER 2005 Enterprise or standard version could be fine.
>
> Regards
> Alberto Brivio
>|||You better determine your needs first...
Ekrem nsoy
"Alberto Brivio" <a.brivio@.adb.it> wrote in message
news:uZci$GBPIHA.1208@.TK2MSFTNGP05.phx.gbl...
> Dear ALL,
> I'm going to install a new cluster (2 X HP DL380 , MSA1000 Storage) based
> on Win 2003 R2 Enterprise and I 'd like to know if I have to install SQL
> SERVER 2005 Enterprise or standard version could be fine.
>
> Regards
> Alberto Brivio
>|||Alberto,
With SQL2005 the version will depend on the number of CPU's rather than the
memory and of course the features you require. If your server has more than
4 CPU's and you want SQL to use them then you must use Enterprise.
Chris
"Alberto Brivio" <a.brivio@.adb.it> wrote in message
news:uZci$GBPIHA.1208@.TK2MSFTNGP05.phx.gbl...
> Dear ALL,
> I'm going to install a new cluster (2 X HP DL380 , MSA1000 Storage) based
> on Win 2003 R2 Enterprise and I 'd like to know if I have to install SQL
> SERVER 2005 Enterprise or standard version could be fine.
>
> Regards
> Alberto Brivio
>

Enterprise Manager won't work - "snap-in failed to initialize"

On one node of a cluster I have I began getting this message today after a
failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
an it in 80\tools\binn but it still doesn't work. This is the exact error
message:
Snap-in failed to initialize
Name: Microsoft SQL Enterprise Manager
Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}See this KB Article. it may helpful
http://support.microsoft.com/?kbid=297064
Petchikumar
"Cathy Soloway" wrote:

> On one node of a cluster I have I began getting this message today after a
> failover. How do I resolve? I've tried copying SQLEM.msc and replacing i
t
> an it in 80\tools\binn but it still doesn't work. This is the exact error
> message:
> Snap-in failed to initialize
> Name: Microsoft SQL Enterprise Manager
> Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}
>|||That didn't work either. I called support and they walked me through
checking out all the DLLs and functionality and finally suggested we do a
re-boot. Will try that over the weekend. Thanks for the response, though.
"Petchikumar" wrote:
[vbcol=seagreen]
> See this KB Article. it may helpful
> http://support.microsoft.com/?kbid=297064
>
> Petchikumar
>
> "Cathy Soloway" wrote:
>

Enterprise Manager won't work - "snap-in failed to initialize"

On one node of a cluster I have I began getting this message today after a
failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
an it in 80\tools\binn but it still doesn't work. This is the exact error
message:
Snap-in failed to initialize
Name: Microsoft SQL Enterprise Manager
Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}See this KB Article. it may helpful
http://support.microsoft.com/?kbid=297064
Petchikumar
"Cathy Soloway" wrote:
> On one node of a cluster I have I began getting this message today after a
> failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
> an it in 80\tools\binn but it still doesn't work. This is the exact error
> message:
> Snap-in failed to initialize
> Name: Microsoft SQL Enterprise Manager
> Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}
>|||That didn't work either. I called support and they walked me through
checking out all the DLLs and functionality and finally suggested we do a
re-boot. Will try that over the weekend. Thanks for the response, though.
"Petchikumar" wrote:
> See this KB Article. it may helpful
> http://support.microsoft.com/?kbid=297064
>
> Petchikumar
>
> "Cathy Soloway" wrote:
> > On one node of a cluster I have I began getting this message today after a
> > failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
> > an it in 80\tools\binn but it still doesn't work. This is the exact error
> > message:
> >
> > Snap-in failed to initialize
> > Name: Microsoft SQL Enterprise Manager
> > Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}
> >

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

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:

Enterprise Manager is not displaying any database information.

We have SQL 2000 Active/Active 2 node cluster. Yesterdat
we did a memory switch to use more than 2GB RAM after that
Enterprise Manager on one node is not displaying any
database information. All the databases is up its just
Enterprise Manager piece is not working. If I do clink on
new database thru ENterprise Manage It display following
message. Any idea ..
Error 220: Airthmetic overflow error for datatype
smallint, value = 32891Hi Avnish,
Try this:
From Query Analzyer, run this query:
use master
go
select * from sysdatabases
go
Do you get the same error?
Sincerely,
Yih-Yoon Lee [Microsoft]
Microsoft SQL Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Enterprise Manager Databases folder shows "No items"

We're running a Win2k Adv Server MS Cluster using two servers with SQL
instances called SQL1 and SQL2 running on them. For some reason, we can't
manage SQL2 via Enterprise Manager recently since the databases folder is now
empty. The databases are there and I can see them via Query Analyzer, but I
just can't manage them via EM. "Management" folder is also empty, but if I
refresh (over and over) I sometimes can access the "SQL Server Agent" items.
Only changes that were made to the servers was to install some security
patches, but none that related to SQL server. Other SQL servers with the
same patches work fine. SQL1 instance can be managed with EM just fine.
I suspect something is wrong with SQL2 instance, but don't know what. It's
not related to the servers since I can move the instance between cluster
nodes and EM still cannot see databases on SQL2. SQL1 moves between nodes
fine and it's databases can be seen via EM.
Not sure if this is a clue, but when I right click on "Databases" and select
"New database", I get this error:
Microsoft SQL-DMO (ODBC SQLState: 22003)
Error 220: Arithmetic overflow error for that data type smallint, value=32826.
Arithmetic overflow error for data type smallint, value=32826.
The statement has been terminated.
I click OK, then I get the standard database properties dialog to create a
database...
Thanks in advance to any help or suggestions.
Regards,
-Daniel
My guess is a problem with DMO. Perhaps re-applying the SQL Server service pack will fix it?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Daniel" <Daniel@.tamc@.discussions.microsoft.com> wrote in message
news:0CB90BA3-08E0-4FA4-9177-6942CDC083BE@.microsoft.com...
> We're running a Win2k Adv Server MS Cluster using two servers with SQL
> instances called SQL1 and SQL2 running on them. For some reason, we can't
> manage SQL2 via Enterprise Manager recently since the databases folder is now
> empty. The databases are there and I can see them via Query Analyzer, but I
> just can't manage them via EM. "Management" folder is also empty, but if I
> refresh (over and over) I sometimes can access the "SQL Server Agent" items.
> Only changes that were made to the servers was to install some security
> patches, but none that related to SQL server. Other SQL servers with the
> same patches work fine. SQL1 instance can be managed with EM just fine.
> I suspect something is wrong with SQL2 instance, but don't know what. It's
> not related to the servers since I can move the instance between cluster
> nodes and EM still cannot see databases on SQL2. SQL1 moves between nodes
> fine and it's databases can be seen via EM.
> Not sure if this is a clue, but when I right click on "Databases" and select
> "New database", I get this error:
> Microsoft SQL-DMO (ODBC SQLState: 22003)
> Error 220: Arithmetic overflow error for that data type smallint, value=32826.
> Arithmetic overflow error for data type smallint, value=32826.
> The statement has been terminated.
> I click OK, then I get the standard database properties dialog to create a
> database...
> Thanks in advance to any help or suggestions.
> Regards,
> -Daniel
>
|||I am seeing these exact symptoms. Cluster, 1 server is showing "No items" in the database folder. Please advise.
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
|||I just ran across this problem today, and what I had to do was drop any databases that weren't in use (offline). I hope this helps anyone else googling for this problem!
-- hbz|||for googlers
no need to drop anything - it's enough to restart that databases whose status causing overflow errors
USE master
GO
DECLARE @.db_name varchar(500)
DECLARE dbn_cursor CURSOR FOR
SELECT [name] FROM sysdatabases;
OPEN dbn_cursor
FETCH NEXT FROM dbn_cursor
INTO @.db_name
WHILE @.@.FETCH_STATUS = 0
BEGIN
select * from sysdatabases where name = @.db_name
IF @.@.ERROR <> 0
BEGIN
declare @.off int
print 'Restarting database '+@.db_name
exec @.off = sp_dboption @.db_name, 'offline', 'TRUE'
IF @.off <> 0
print 'Taking offline failed! Need manual workaround!'
else
begin
declare @.on int
exec @.on = sp_dboption @.db_name, 'offline', 'FALSE'
IF @.on <> 0
print 'Bringing online failed! Need manual workaround!'
else
print 'Restart successfull!'
end
END
FETCH NEXT FROM dbn_cursor
INTO @.db_name
END
CLOSE dbn_cursor
DEALLOCATE dbn_cursor
GO|||I had exactly the same issue, 2x clustered SQL 2000 SP3 boxen, "no items" in
EM DB view, should be 50 or so. Failed over to other node, still no joy.
ran the script & it worked. (edited it to ID the database(s) having problems
first, found it was an old one, then ran full script to restart said DB)
Thank you Alan.
Cheers
Tim
|||maybe you need to re-attach them?
I'd use query analzer and check out master.dbo.sysdatabases and see if that
tells you anything
"Tim" <tim.cox@.noterinaceous.com> wrote in message
news:d8e3b0fef0a846079c0e261264455587@.ureader.com. ..
> I had exactly the same issue, 2x clustered SQL 2000 SP3 boxen, "no items"
in
> EM DB view, should be 50 or so. Failed over to other node, still no joy.
> ran the script & it worked. (edited it to ID the database(s) having
problems
> first, found it was an old one, then ran full script to restart said DB)
> Thank you Alan.
> Cheers
> Tim