64bit and performance counters

Does anyone know if the hotfix mentioned in KB article 812915
[FIX: "Performance Monitor Shared Memory Setup Failed: -1" Error Message
When You Start SQL Server]
is the same for 64bit as for 32bit, my first guess is no - but I have to
ask.
We just installed 64bit SQL Server 2 weeks ago and now the performace
counters are gone and the above "-1" message shows up in the SQL Server
errolog. This looks exactly like the same problem we encountered with 32
bit.
Thanks,
Frankm
Hi Frankm,
From your descriptions, I understood that you would like to the fix in
KB:812915 will be possible for your performance counter issue. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know
Based on my knowledge, it will be suitable for your 64bit SQL Server as you
could find the following information in the KB
The information in this article applies to:
Microsoft SQL Server 2000 (all editions) SP3
You could contact PSS as KB told to ask for a hotfix If the hotfix
doesn't resolve your issue, your issue may be not share the same root cause
as fixed in KB: 812915. In this way, I will be glad to continue our
troubleshooting until it is resolved
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Are you sure that the Hotfix will work for 64bit?
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:YhgxzlmWEHA.3484@.cpmsftngxa10.phx.gbl...
> Hi Frankm,
> From your descriptions, I understood that you would like to the fix in
> KB:812915 will be possible for your performance counter issue. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know
> Based on my knowledge, it will be suitable for your 64bit SQL Server as
you
> could find the following information in the KB
> ----
> The information in this article applies to:
> Microsoft SQL Server 2000 (all editions) SP3
> ----
> You could contact PSS as KB told to ask for a hotfix If the hotfix
> doesn't resolve your issue, your issue may be not share the same root
cause
> as fixed in KB: 812915. In this way, I will be glad to continue our
> troubleshooting until it is resolved
>
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi frankm,
I am sure that hotfix will work for 64bit SQL Server
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Hi frankm,
I am sure that hotfix will work for 64bit SQL Server
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Thank you - I will attempt to apply the patch.
Thank you again ...
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:XE7dHSYXEHA.308@.cpmsftngxa10.phx.gbl...
> Hi frankm,
> I am sure that hotfix will work for 64bit SQL Server
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Thank you - I will attempt to apply the patch.
Thank you again ...
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:XE7dHSYXEHA.308@.cpmsftngxa10.phx.gbl...
> Hi frankm,
> I am sure that hotfix will work for 64bit SQL Server
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi Frankm,
Thanks for your prompt updates!
You could post back the result after applying the patches to Re-Open this
thread if the patch doesn't work for you. In this case, you issue might be
another root causes that has no relationship with KB: 812915 and it is
highly appreciated if you could create a new thread so that we could
troubleshooting this issue for you
Anyway, thanks for using MSDN Newsgroup! We are here to be of assistance
whenever you have problems!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

64bit and performance counters

Does anyone know if the hotfix mentioned in KB article 812915
[FIX: "Performance Monitor Shared Memory Setup Failed: -1" Error Message
When You Start SQL Server]
is the same for 64bit as for 32bit, my first guess is no - but I have to
ask.
We just installed 64bit SQL Server 2 weeks ago and now the performace
counters are gone and the above "-1" message shows up in the SQL Server
errolog. This looks exactly like the same problem we encountered with 32
bit.
Thanks,
FrankmHi Frankm,
From your descriptions, I understood that you would like to the fix in
KB:812915 will be possible for your performance counter issue. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know:)
Based on my knowledge, it will be suitable for your 64bit SQL Server as you
could find the following information in the KB
----
The information in this article applies to:
Microsoft SQL Server 2000 (all editions) SP3
----
You could contact PSS as KB told to ask for a hotfix :) If the hotfix
doesn't resolve your issue, your issue may be not share the same root cause
as fixed in KB: 812915. In this way, I will be glad to continue our
troubleshooting until it is resolved :)
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Are you sure that the Hotfix will work for 64bit?
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:YhgxzlmWEHA.3484@.cpmsftngxa10.phx.gbl...
> Hi Frankm,
> From your descriptions, I understood that you would like to the fix in
> KB:812915 will be possible for your performance counter issue. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know:)
> Based on my knowledge, it will be suitable for your 64bit SQL Server as
you
> could find the following information in the KB
> ----
> The information in this article applies to:
> Microsoft SQL Server 2000 (all editions) SP3
> ----
> You could contact PSS as KB told to ask for a hotfix :) If the hotfix
> doesn't resolve your issue, your issue may be not share the same root
cause
> as fixed in KB: 812915. In this way, I will be glad to continue our
> troubleshooting until it is resolved :)
>
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi frankm,
I am sure that hotfix will work for 64bit SQL Server :)
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Thank you - I will attempt to apply the patch.
Thank you again ...
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:XE7dHSYXEHA.308@.cpmsftngxa10.phx.gbl...
> Hi frankm,
> I am sure that hotfix will work for 64bit SQL Server :)
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Frankm,
Thanks for your prompt updates!
You could post back the result after applying the patches to Re-Open this
thread if the patch doesn't work for you. In this case, you issue might be
another root causes that has no relationship with KB: 812915 and it is
highly appreciated if you could create a new thread so that we could
troubleshooting this issue for you :)
Anyway, thanks for using MSDN Newsgroup! We are here to be of assistance
whenever you have problems!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

64bit and performance counters

Does anyone know if the hotfix mentioned in KB article 812915
[FIX: "Performance Monitor Shared Memory Setup Failed: -1" Error Message
When You Start SQL Server]
is the same for 64bit as for 32bit, my first guess is no - but I have to
ask.
We just installed 64bit SQL Server 2 weeks ago and now the performace
counters are gone and the above "-1" message shows up in the SQL Server
errolog. This looks exactly like the same problem we encountered with 32
bit.
Thanks,
FrankmHi Frankm,
From your descriptions, I understood that you would like to the fix in
KB:812915 will be possible for your performance counter issue. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know
Based on my knowledge, it will be suitable for your 64bit SQL Server as you
could find the following information in the KB
----
The information in this article applies to:
Microsoft SQL Server 2000 (all editions) SP3
----
You could contact PSS as KB told to ask for a hotfix If the hotfix
doesn't resolve your issue, your issue may be not share the same root cause
as fixed in KB: 812915. In this way, I will be glad to continue our
troubleshooting until it is resolved
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Are you sure that the Hotfix will work for 64bit?
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:YhgxzlmWEHA.3484@.cpmsftngxa10.phx.gbl...
> Hi Frankm,
> From your descriptions, I understood that you would like to the fix in
> KB:812915 will be possible for your performance counter issue. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know
> Based on my knowledge, it will be suitable for your 64bit SQL Server as
you
> could find the following information in the KB
> ----
> The information in this article applies to:
> Microsoft SQL Server 2000 (all editions) SP3
> ----
> You could contact PSS as KB told to ask for a hotfix If the hotfix
> doesn't resolve your issue, your issue may be not share the same root
cause
> as fixed in KB: 812915. In this way, I will be glad to continue our
> troubleshooting until it is resolved
>
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi frankm,
I am sure that hotfix will work for 64bit SQL Server
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Thank you - I will attempt to apply the patch.
Thank you again ...
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:XE7dHSYXEHA.308@.cpmsftngxa10.phx.gbl...
> Hi frankm,
> I am sure that hotfix will work for 64bit SQL Server
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Frankm,
Thanks for your prompt updates!
You could post back the result after applying the patches to Re-Open this
thread if the patch doesn't work for you. In this case, you issue might be
another root causes that has no relationship with KB: 812915 and it is
highly appreciated if you could create a new thread so that we could
troubleshooting this issue for you
Anyway, thanks for using MSDN Newsgroup! We are here to be of assistance
whenever you have problems!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

3rd party performance tuning monitor/software?

Hi all, My boss has asked me to research and recommend a product that our developers (not database developers, but front-end developers that *cringe* get into the database to make the occasional stored procedure) can use to determine the relative efficiency of thier code and/or the database structure and keys.

We currently have a few licensed versions of Quest's Coefficient software, which I think is very usable for such things (I do on a regular basis), but he doesn't think that is "friendly" enough for a GUI developer that is not a database expert.

Any thought and/or suggestions for a 3rd party software package that y'all have used or are using that might fit the bill? I don't mind doing the footwork and research, just thought I would "seek the advice of my peers" to get started.

Yeah, I know the design should drive the database, but we are in various stages of "getting there", so any help in the interim is a good thing.

Thanks for the thoughts and waste of brain cells on my behalf.I'm still not understanding exactly what you want to analyze. Are you trying to get at the design of the database, the implementation, the performance of specific queries... There are too many moving parts for me to figure out how to start to answer your question.

-PatP|||Pat, this request is coming from a manager. :rolleyes: The target, therefore, is a moving one. Assuming (big leap here) that the basic design of the database is sound, then what I am looking for is something that will suggest where an index would be valuable, Probably by examining specific queries, or tables, or views.

Probably Enterprise Manager has such tools, such as SQL Profiler, and I will also look into that, but someone has gotten my manager's ear, I think, about getting a tool that makes the detection of problem access methods/code apparent.

The basic trouble is that the developers are NOT SQL Server experts, as I am the closest to that in the group (yep, scary, eh?) and there is only so many of me.

The ultimate solution is to educate the masses, but that ain't gonna happen soon, so I am just looking for a tool or suggestions (or both) regarding some ways to keep 'em out of too much trouble in the meantime.|||I have been beating the drum of sql quality control around my shop since I got here.

The only effective method of improving the sql going into the application that I have found is education and mentoring. A developer will come to me and say "sql server sucks, why is my code so slow. QA says the page performs like crap". I will make them sit there while I go over their sql, execution plan and table design and indexes and I will explain stuff to them. Then I will offer to lend them a book on writing sql.

In my 16 months here I think I have helped the quality of the overall output of 3 or 4 of the developers.