new thread -- how to add counters to the server performance monitor

thank you so much, John. Sorry for couldn't response to
you earlier. Been really busy lately.
I don't know whether this is something safe to do because
sometimes certain counter got disabled by the system
automatically because they have errors in them. If re-
active them, may cause problem to the server or slow the
system down.
I could very well be wrong at this. Just want to make
sure with you first.
Please see below quoted from window's help article:
----
Cause: Test routines that run when you start Performance
have detected a problem with installed counters and have
disabled the counters automatically to prevent the
counters from slowing the system. Disabled objects and
counters do not appear in the Add Counters dialog box.
Solution: Using Registry Editor, change the value under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Servic
e_name\Performance\Disable Performance Counters from 1 for
disable to 0 for enable. Note that counters that have been
disabled after initial testing are likely to contain
errors and may cause system problems. For information
about debugging problems with counter DLLs, see the
Microsoft Web site (http://msdn.microsoft.com/).
Caution
.. Incorrectly editing the registry may severely
damage your system. Before making changes to the registry,
you should back up any valued data on the computer.
----
Thanks.
JJ
>--Original Message--
>JJ
>
>Sometimes, for a wide variety of different reasons, the
>SQL Server Performance Monitor counters will not show up
>as they should. Often, but not always, this problem can
be
>fixed by following these three steps:
>1) At the command prompt, type in the following:
>unlodctr.exe MSSQLServer
>
>2) Then type in the following: lodctr.exe <SQL Server
>path>\binn\sqlctr.ini
>
>3) Reboot the server
>
>Hope this helps
>
>JohnJJ
The article you quote may be the reason the fix does not
always work. I don't think it will do any harm to try it.
The only issue may be when to do the reboot. I know where
I work you can not just perform a reboot, it would need to
be planed, approved and scheduled.
Good luck
John|||thanks again, John!!
>--Original Message--
>JJ
>The article you quote may be the reason the fix does not
>always work. I don't think it will do any harm to try it.
>The only issue may be when to do the reboot. I know where
>I work you can not just perform a reboot, it would need
to
>be planed, approved and scheduled.
>Good luck
>John
>.
>|||Hi John,
under which directory should I run the unlodctr.exe and
lodctr.exe according to you?
1) At the command prompt, type in the following:
unlodctr.exe MSSQLServer
2) Then type in the following: lodctr.exe <SQL Server
path>\binn\sqlctr.ini
Thanks.
JJ
>--Original Message--
>JJ
>The article you quote may be the reason the fix does not
>always work. I don't think it will do any harm to try it.
>The only issue may be when to do the reboot. I know where
>I work you can not just perform a reboot, it would need
to
>be planed, approved and scheduled.
>Good luck
>John
>.
>|||JJ
I found unlodctr.exe and lodctr.exe in C:\\WINNT\system32
on my workstation. Right click on my computer and use find
to check for location on yours.
Regards
John
>--Original Message--
>Hi John,
>under which directory should I run the unlodctr.exe and
>lodctr.exe according to you?
>1) At the command prompt, type in the following:
>unlodctr.exe MSSQLServer
>2) Then type in the following: lodctr.exe <SQL Server
>path>\binn\sqlctr.ini
>Thanks.
>JJ
>>--Original Message--
>>JJ
>>The article you quote may be the reason the fix does not
>>always work. I don't think it will do any harm to try
it.
>>The only issue may be when to do the reboot. I know
where
>>I work you can not just perform a reboot, it would need
>to
>>be planed, approved and scheduled.
>>Good luck
>>John
>>.
>.
>|||yes, mine are in the same location too. for lodctr.exe,
it's also in C:\WINNT\ServicePackFiles\i386. Same size,
same date. How come?
so I should run the code under C:\\WINNT\system32?
Thanks, John.
JJ
>--Original Message--
>JJ
>I found unlodctr.exe and lodctr.exe in C:\\WINNT\system32
>on my workstation. Right click on my computer and use find
>to check for location on yours.
>Regards
>John
>>--Original Message--
>>Hi John,
>>under which directory should I run the unlodctr.exe and
>>lodctr.exe according to you?
>>1) At the command prompt, type in the following:
>>unlodctr.exe MSSQLServer
>>2) Then type in the following: lodctr.exe <SQL Server
>>path>\binn\sqlctr.ini
>>Thanks.
>>JJ
>>--Original Message--
>>JJ
>>The article you quote may be the reason the fix does
not
>>always work. I don't think it will do any harm to try
>it.
>>The only issue may be when to do the reboot. I know
>where
>>I work you can not just perform a reboot, it would need
>>to
>>be planed, approved and scheduled.
>>Good luck
>>John
>>.
>>.
>.
>

New SQL Database?

I posted this in "Visual Studio General" a few days ago, but got no response.

I am running VSTS 2005, and I have Microsoft SQL Server 2005 Developer Edition installed on my machine. I would now like to create an application that has its own database file (.mdf) included. From within my VS project, I go to "Add New Item". I select "SQL Database", put in the name, and hit [Add]. At that point I get a message box with the title "Local database file", saying "Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed." Any ideas of what I'm doing wrong? Do I need SQL Server 2005 Express installed in addition to Developer Edition?

It's quite possible that this is well documented, or that I have a simple configuration set wrong, or that I'm doing something fundamentally wrong, and that all I need to do is RTFM, but despite searches, I couldn't find anything that addressed this directly. Can someone point me in the right direction? Also, if there's a better forum to post this to, please let me know.

Thanks!

Brad.

moved to the SQL forum|||

User instances are a feature of SQL Server Express, so you'll need to install SSE in addition to your Developer Edition instance to use this feature in Visual Studio.

Hope this helps,
Steve