MMC 3.0 and SQL 2000

I am to install MMC 3.0 to a server (Server 2003 Standard Edition SP1) with
SQL 2000 Sp4. I would like to know if Server Enterprise Manager works under
MMC 3.0.
--
Regards
Rasmus SöderlundHi Rasmus
EM seems to work fine with MMC 3.0
John
"Rasmus" wrote:
> I am to install MMC 3.0 to a server (Server 2003 Standard Edition SP1) with
> SQL 2000 Sp4. I would like to know if Server Enterprise Manager works under
> MMC 3.0.
> --
> Regards
>
> Rasmus Söderlund

Missing Subject

Hi,
last month I installed SQL Server 2000 on a new server (Install SQL2000 and
then upgraded to SP4) because that server is going to replace the main
production server. I've restored the database dumps from the old server to
the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
because there are some stored procedures that use the xp_sendmail.
Everything seems to work OK, until I noticed that the mails, sent by SQL
Mail using the xp_sendmail are all missing the subject line, whereas the
subject line is present in the mail sent by the (old) production server.
the code in the stored procedures that invoke xp_sendmail is identical on
both machines.
Am I missing something or...
--
Adri
Programmers do it Bit by BitHi
Without seeing the actual call to xp_sendmail it is hard to say, but at a
guess you are possibly concatentating to a NULL value or something similar
either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
different.
John
"Adri" wrote:
> Hi,
> last month I installed SQL Server 2000 on a new server (Install SQL2000 and
> then upgraded to SP4) because that server is going to replace the main
> production server. I've restored the database dumps from the old server to
> the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
> because there are some stored procedures that use the xp_sendmail.
> Everything seems to work OK, until I noticed that the mails, sent by SQL
> Mail using the xp_sendmail are all missing the subject line, whereas the
> subject line is present in the mail sent by the (old) production server.
> the code in the stored procedures that invoke xp_sendmail is identical on
> both machines.
> Am I missing something or...
> --
> Adri
> Programmers do it Bit by Bit|||Adri skrev:
> ...
> Am I missing something or...
> ...
Actually yes, the Subject ;)|||In fact, a simple
xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
,@.subject = 'subject'
delivers an e-mail with an empty subject line :-(
--
Adri
Programmers do it Bit by Bit
"John Bell" wrote:
> Hi
> Without seeing the actual call to xp_sendmail it is hard to say, but at a
> guess you are possibly concatentating to a NULL value or something similar
> either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
> different.
> John
> "Adri" wrote:
> > Hi,
> >
> > last month I installed SQL Server 2000 on a new server (Install SQL2000 and
> > then upgraded to SP4) because that server is going to replace the main
> > production server. I've restored the database dumps from the old server to
> > the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
> > because there are some stored procedures that use the xp_sendmail.
> >
> > Everything seems to work OK, until I noticed that the mails, sent by SQL
> > Mail using the xp_sendmail are all missing the subject line, whereas the
> > subject line is present in the mail sent by the (old) production server.
> >
> > the code in the stored procedures that invoke xp_sendmail is identical on
> > both machines.
> >
> > Am I missing something or...
> > --
> > Adri
> > Programmers do it Bit by Bit|||Hi Adri
More questions...
I assume you can send mail successfully from Outlook with a subject? if the
subject parameter is before the message parameter does it work? Is this 32 or
64 bit?
John
"Adri" wrote:
> In fact, a simple
> xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
> ,@.subject = 'subject'
> delivers an e-mail with an empty subject line :-(
> --
> Adri
> Programmers do it Bit by Bit
>
> "John Bell" wrote:
> > Hi
> >
> > Without seeing the actual call to xp_sendmail it is hard to say, but at a
> > guess you are possibly concatentating to a NULL value or something similar
> > either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
> > different.
> >
> > John
> >
> > "Adri" wrote:
> >
> > > Hi,
> > >
> > > last month I installed SQL Server 2000 on a new server (Install SQL2000 and
> > > then upgraded to SP4) because that server is going to replace the main
> > > production server. I've restored the database dumps from the old server to
> > > the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
> > > because there are some stored procedures that use the xp_sendmail.
> > >
> > > Everything seems to work OK, until I noticed that the mails, sent by SQL
> > > Mail using the xp_sendmail are all missing the subject line, whereas the
> > > subject line is present in the mail sent by the (old) production server.
> > >
> > > the code in the stored procedures that invoke xp_sendmail is identical on
> > > both machines.
> > >
> > > Am I missing something or...
> > > --
> > > Adri
> > > Programmers do it Bit by Bit|||Adri wrote:
> In fact, a simple
> xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
> ,@.subject = 'subject'
> delivers an e-mail with an empty subject line :-(
> --
> Adri
> Programmers do it Bit by Bit
*bonk*
Sorry for my pityful attempt of being funny :) I actually didn't read
your post carefully enough and didn't realize your problem was really
'Missing Subject', not that some client added that as a subject for
your post (that you had sent without a subject)... Ahem...
Btw, did you do a search on Google, I saw a lot of hits using
"xp_sendmail" and "subject" as search parameters even though I didn't
instantly find a solution for the problem...
/impslayer, aka Birger Johansson|||Hi Adri,
My understanding of your issue is:
After the migration of SQL Server 2000 from an older server to a new one,
you can also send email by xp_sendmail in your stored procedures,however
those sent mails' subjects are missed.
If I have misunderstood, please let me know.
I recommend that you try the following:
1) Login as account that is running SQL Server server and open outlook.
2) Tools->Options->Mail Format tab. Change the "compose in message format"
to plan
text and send an email through outlook with a subject.
3) Change the "compose in message format" back to html. Send email with
subject.
Stop and start SQL Server instance might be necessary.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi Charles,
In fact, I did a new installation of SQL 2000 on a W2K3 server and upgraded
SQL from RTM to SP4. Having done that, I restored the (user)database dumps
from the old server to the new one, and configured SQL Mail as usual.
The old server had originally SQL 2000 RTM installed, upgraded to SP2, SP3,
Hotfix KB891640 applied and at last upgraded to SP4.
I've changed the Mail Format as you supposed, but that did not help.
--
Adri
Programmers do it Bit by Bit
"Charles Wang[MSFT]" wrote:
> Hi Adri,
> My understanding of your issue is:
> After the migration of SQL Server 2000 from an older server to a new one,
> you can also send email by xp_sendmail in your stored procedures,however
> those sent mails' subjects are missed.
> If I have misunderstood, please let me know.
> I recommend that you try the following:
> 1) Login as account that is running SQL Server server and open outlook.
> 2) Tools->Options->Mail Format tab. Change the "compose in message format"
> to plan
> text and send an email through outlook with a subject.
> 3) Change the "compose in message format" back to html. Send email with
> subject.
> Stop and start SQL Server instance might be necessary.
> Sincerely yours,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>|||Like saying "This page is intentionally blank"!!!
John
"impslayer" wrote:
> Adri wrote:
> > In fact, a simple
> >
> > xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
> > ,@.subject = 'subject'
> >
> > delivers an e-mail with an empty subject line :-(
> >
> > --
> > Adri
> > Programmers do it Bit by Bit
> *bonk*
> Sorry for my pityful attempt of being funny :) I actually didn't read
> your post carefully enough and didn't realize your problem was really
> 'Missing Subject', not that some client added that as a subject for
> your post (that you had sent without a subject)... Ahem...
> Btw, did you do a search on Google, I saw a lot of hits using
> "xp_sendmail" and "subject" as search parameters even though I didn't
> instantly find a solution for the problem...
> /impslayer, aka Birger Johansson
>|||Hi Adri,
To make sure this is a dabase wide issue or server instance side issue, I
recommend that you create a new stored procedure with xp_sendmail in a test
database and see whether or not it has the same issue.
Also, you may try recompiling the stored procedures.
Charles Wang
Microsoft Online Community Support|||Hi
Please clarify that using Outlook directly is working ok?
Which version of office is being used?
John
"Adri" wrote:
> Hi Charles,
> In fact, I did a new installation of SQL 2000 on a W2K3 server and upgraded
> SQL from RTM to SP4. Having done that, I restored the (user)database dumps
> from the old server to the new one, and configured SQL Mail as usual.
> The old server had originally SQL 2000 RTM installed, upgraded to SP2, SP3,
> Hotfix KB891640 applied and at last upgraded to SP4.
> I've changed the Mail Format as you supposed, but that did not help.
> --
> Adri
> Programmers do it Bit by Bit
>
> "Charles Wang[MSFT]" wrote:
> > Hi Adri,
> >
> > My understanding of your issue is:
> > After the migration of SQL Server 2000 from an older server to a new one,
> > you can also send email by xp_sendmail in your stored procedures,however
> > those sent mails' subjects are missed.
> > If I have misunderstood, please let me know.
> >
> > I recommend that you try the following:
> > 1) Login as account that is running SQL Server server and open outlook.
> > 2) Tools->Options->Mail Format tab. Change the "compose in message format"
> > to plan
> > text and send an email through outlook with a subject.
> > 3) Change the "compose in message format" back to html. Send email with
> > subject.
> >
> > Stop and start SQL Server instance might be necessary.
> >
> > Sincerely yours,
> > Charles Wang
> > Microsoft Online Community Support
> > ======================================================> > When responding to posts, please "Reply to Group" via
> > your newsreader so that others may learn and benefit
> > from this issue.
> > ======================================================> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > ======================================================> >
> >
> >

Missing Subject

Hi,
last month I installed SQL Server 2000 on a new server (Install SQL2000 and
then upgraded to SP4) because that server is going to replace the main
production server. I've restored the database dumps from the old server to
the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
because there are some stored procedures that use the xp_sendmail.
Everything seems to work OK, until I noticed that the mails, sent by SQL
Mail using the xp_sendmail are all missing the subject line, whereas the
subject line is present in the mail sent by the (old) production server.
the code in the stored procedures that invoke xp_sendmail is identical on
both machines.
Am I missing something or...
--
Adri
Programmers do it Bit by BitHi
Without seeing the actual call to xp_sendmail it is hard to say, but at a
guess you are possibly concatentating to a NULL value or something similar
either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
different.
John
"Adri" wrote:

> Hi,
> last month I installed SQL Server 2000 on a new server (Install SQL2000 an
d
> then upgraded to SP4) because that server is going to replace the main
> production server. I've restored the database dumps from the old server to
> the new one and did also copy the SQL Agent jobs. Also configured SQL Mail
,
> because there are some stored procedures that use the xp_sendmail.
> Everything seems to work OK, until I noticed that the mails, sent by SQL
> Mail using the xp_sendmail are all missing the subject line, whereas the
> subject line is present in the mail sent by the (old) production server.
> the code in the stored procedures that invoke xp_sendmail is identical on
> both machines.
> Am I missing something or...
> --
> Adri
> Programmers do it Bit by Bit|||Adri skrev:

> ...
> Am I missing something or...
> ...
Actually yes, the Subject ;)|||In fact, a simple
xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
,@.subject = 'subject'
delivers an e-mail with an empty subject line :-(
Adri
Programmers do it Bit by Bit
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Without seeing the actual call to xp_sendmail it is hard to say, but at a
> guess you are possibly concatentating to a NULL value or something similar
> either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
> different.
> John
> "Adri" wrote:
>|||Hi Adri
More questions...
I assume you can send mail successfully from Outlook with a subject? if the
subject parameter is before the message parameter does it work? Is this 32 o
r
64 bit?
John
"Adri" wrote:
[vbcol=seagreen]
> In fact, a simple
> xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message
'
> ,@.subject = 'subject'
> delivers an e-mail with an empty subject line :-(
> --
> Adri
> Programmers do it Bit by Bit
>
> "John Bell" wrote:
>|||Adri wrote:
> In fact, a simple
> xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message
'
> ,@.subject = 'subject'
> delivers an e-mail with an empty subject line :-(
> --
> Adri
> Programmers do it Bit by Bit
*bonk*
Sorry for my pityful attempt of being funny I actually didn't read
your post carefully enough and didn't realize your problem was really
'Missing Subject', not that some client added that as a subject for
your post (that you had sent without a subject)... Ahem...
Btw, did you do a search on Google, I saw a lot of hits using
"xp_sendmail" and "subject" as search parameters even though I didn't
instantly find a solution for the problem...
/impslayer, aka Birger Johansson|||Hi Adri,
My understanding of your issue is:
After the migration of SQL Server 2000 from an older server to a new one,
you can also send email by xp_sendmail in your stored procedures,however
those sent mails' subjects are missed.
If I have misunderstood, please let me know.
I recommend that you try the following:
1) Login as account that is running SQL Server server and open outlook.
2) Tools->Options->Mail Format tab. Change the "compose in message format"
to plan
text and send an email through outlook with a subject.
3) Change the "compose in message format" back to html. Send email with
subject.
Stop and start SQL Server instance might be necessary.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi Charles,
In fact, I did a new installation of SQL 2000 on a W2K3 server and upgraded
SQL from RTM to SP4. Having done that, I restored the (user)database dumps
from the old server to the new one, and configured SQL Mail as usual.
The old server had originally SQL 2000 RTM installed, upgraded to SP2, SP3,
Hotfix KB891640 applied and at last upgraded to SP4.
I've changed the Mail Format as you supposed, but that did not help.
--
Adri
Programmers do it Bit by Bit
"Charles Wang[MSFT]" wrote:

> Hi Adri,
> My understanding of your issue is:
> After the migration of SQL Server 2000 from an older server to a new one,
> you can also send email by xp_sendmail in your stored procedures,however
> those sent mails' subjects are missed.
> If I have misunderstood, please let me know.
> I recommend that you try the following:
> 1) Login as account that is running SQL Server server and open outlook.
> 2) Tools->Options->Mail Format tab. Change the "compose in message format"
> to plan
> text and send an email through outlook with a subject.
> 3) Change the "compose in message format" back to html. Send email with
> subject.
> Stop and start SQL Server instance might be necessary.
> Sincerely yours,
> Charles Wang
> Microsoft Online Community Support
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>|||Like saying "This page is intentionally blank"!!!
John
"impslayer" wrote:

> Adri wrote:
> *bonk*
> Sorry for my pityful attempt of being funny I actually didn't read
> your post carefully enough and didn't realize your problem was really
> 'Missing Subject', not that some client added that as a subject for
> your post (that you had sent without a subject)... Ahem...
> Btw, did you do a search on Google, I saw a lot of hits using
> "xp_sendmail" and "subject" as search parameters even though I didn't
> instantly find a solution for the problem...
> /impslayer, aka Birger Johansson
>|||Hi Adri,
To make sure this is a dabase wide issue or server instance side issue, I
recommend that you create a new stored procedure with xp_sendmail in a test
database and see whether or not it has the same issue.
Also, you may try recompiling the stored procedures.
Charles Wang
Microsoft Online Community Support

Missing SQL Server 2000 Performance Counters

I installed SQL Server 2000 w/SP4 on a x64 Windows 2003 OS. I found that I
did not have access to the SQL performance counters and it is the same on
other servers with the same combination. Has anyone run into this issue?
What's the solution to it? thanks.Hi Jason,
Thank you for your post.
I understand that you can not view the Performance Counters of SQL Server
on a 64bit OS. If I misunderstood your concern, please feel free to let me
know.
A 64-bit perfmon client app can view OS counters plus counters for any
application that has installed a 64-bit perfmon DLL (a 64-bit app can't
load a 32-bit DLL). This means that a 64-bit perfmon client app can see a
local 64-bit SQL instance's counters, but not counters for a local 32-bit
instance running in WOW64.
A possible workaround to this problem could be:
Please run "mmc /32 perfmon.msc" from Start-Run. Please let me know whether
you can see the perfmon counters for 32-bit sql server or not.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Missing SQL Server 2000 Performance Counters

I installed SQL Server 2000 w/SP4 on a x64 Windows 2003 OS. I found that I
did not have access to the SQL performance counters and it is the same on
other servers with the same combination. Has anyone run into this issue?
What's the solution to it? thanks.Hi Jason,
Thank you for your post.
I understand that you can not view the Performance Counters of SQL Server
on a 64bit OS. If I misunderstood your concern, please feel free to let me
know.
A 64-bit perfmon client app can view OS counters plus counters for any
application that has installed a 64-bit perfmon DLL (a 64-bit app can't
load a 32-bit DLL). This means that a 64-bit perfmon client app can see a
local 64-bit SQL instance's counters, but not counters for a local 32-bit
instance running in WOW64.
A possible workaround to this problem could be:
Please run "mmc /32 perfmon.msc" from Start-Run. Please let me know whether
you can see the perfmon counters for 32-bit sql server or not.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Since this thread is already closed, here is a link to it:
http://groups.google.co.uk/group/mi...5989f5fc6817daa
"I installed SQL Server 2000 w/SP4 on a x64 Windows 2003 OS. I found
that I
did not have access to the SQL performance counters and it is the same
on
other servers with the same combination. Has anyone run into this
issue?
What's the solution to it? thanks. "
We are having the same problem, and the posted work around does work:
"A possible workaround to this problem could be:
Please run "mmc /32 perfmon.msc" from Start-Run. Please let me know
whether
you can see the perfmon counters for 32-bit sql server or not. "
...But, that prevents us from being able to see the counters from our
own computers which makes troubleshooting emergencies much quicker than
having to log in to the server itself to perform this.
Does anyone know any way of being able to see these counters from a
remote computer?
Thanks.

missing hd partition

hello, we have sqlserver2K on Win2K SP4 on two machines namely prod and
backup. on backup when i do EM backup and click on the "add" device i
could view the different hard disk partitions of my server (C:, D:, E:,
F. but on the prod i could only view C: even though there is a D:
partition. previously i had scheduled an EM backup to D: partition on
this prod server. last week i noticed that the backup is failing
because D: is not being "seen" by EM. i've read through the BOL but
couldn't find a clue (probably i'm thick) so i'm asking if anyone could
shed a light on how EM "see" the D: partition?maverick wrote:
> hello, we have sqlserver2K on Win2K SP4 on two machines namely prod and
> backup. on backup when i do EM backup and click on the "add" device i
> could view the different hard disk partitions of my server (C:, D:, E:,
> F. but on the prod i could only view C: even though there is a D:
> partition. previously i had scheduled an EM backup to D: partition on
> this prod server. last week i noticed that the backup is failing
> because D: is not being "seen" by EM. i've read through the BOL but
> couldn't find a clue (probably i'm thick) so i'm asking if anyone could
> shed a light on how EM "see" the D: partition?
>
Verify that the SQL Server service account (check the service
properties) has permissions to read/write on the "missing" partition.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Verify that the SQL Server service account (check the service
> properties) has permissions to read/write on the "missing" partition.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
that worked! the account that sqlserver is using doesn't have
permissions on the "missing" partition.
thank you so much Tracy for your help!

missing hd partition

hello, we have sqlserver2K on Win2K SP4 on two machines namely prod and
backup. on backup when i do EM backup and click on the "add" device i
could view the different hard disk partitions of my server (C:, D:, E:,
F:). but on the prod i could only view C: even though there is a D:
partition. previously i had scheduled an EM backup to D: partition on
this prod server. last week i noticed that the backup is failing
because D: is not being "seen" by EM. i've read through the BOL but
couldn't find a clue (probably i'm thick) so i'm asking if anyone could
shed a light on how EM "see" the D: partition?maverick wrote:
> hello, we have sqlserver2K on Win2K SP4 on two machines namely prod and
> backup. on backup when i do EM backup and click on the "add" device i
> could view the different hard disk partitions of my server (C:, D:, E:,
> F:). but on the prod i could only view C: even though there is a D:
> partition. previously i had scheduled an EM backup to D: partition on
> this prod server. last week i noticed that the backup is failing
> because D: is not being "seen" by EM. i've read through the BOL but
> couldn't find a clue (probably i'm thick) so i'm asking if anyone could
> shed a light on how EM "see" the D: partition?
>
Verify that the SQL Server service account (check the service
properties) has permissions to read/write on the "missing" partition.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Verify that the SQL Server service account (check the service
> properties) has permissions to read/write on the "missing" partition.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
that worked! the account that sqlserver is using doesn't have
permissions on the "missing" partition.
thank you so much Tracy for your help!