This is the only thing holding up our deployment of SQL 2005.
I configured it and sent a "test message" with the "send test email"
control, and it works instantly.
When I send an email using procedure, nothing happens.
The log shows status as "sent". No errors. But no email is delivered.
I use the same email address as the test email. I don't get it.
EXEC msdb.dbo.sp_send_dbmail
@.profile_name= N'test',
@.recipients= N'myemailaddress',
@.Subject = N'test subject',
@.body= N'the body';
This returns "mail sent". But it is never delivered.
Like I said, the "test email" with the same profile works.We found the problem, the recipient had a bad rule on their end!
"Croco Stimpy" <none@.none.com> wrote in message
news:uhO1Ny0TGHA.4132@.TK2MSFTNGP11.phx.gbl...
> This is the only thing holding up our deployment of SQL 2005.
> I configured it and sent a "test message" with the "send test email"
> control, and it works instantly.
> When I send an email using procedure, nothing happens.
> The log shows status as "sent". No errors. But no email is delivered.
> I use the same email address as the test email. I don't get it.
> EXEC msdb.dbo.sp_send_dbmail
> @.profile_name= N'test',
> @.recipients= N'myemailaddress',
> @.Subject = N'test subject',
> @.body= N'the body';
>
> This returns "mail sent". But it is never delivered.
> Like I said, the "test email" with the same profile works.
>
Showing posts with label configured. Show all posts
Showing posts with label configured. Show all posts
Monday, March 19, 2012
I cannot get DBMAIL to work
I cannot get DBMAIL to work
This is the only thing holding up our deployment of SQL 2005.
I configured it and sent a "test message" with the "send test email"
control, and it works instantly.
When I send an email using procedure, nothing happens.
The log shows status as "sent". No errors. But no email is delivered.
I use the same email address as the test email. I don't get it.
EXEC msdb.dbo.sp_send_dbmail
@.profile_name= N'test',
@.recipients= N'myemailaddress',
@.Subject = N'test subject',
@.body= N'the body';
This returns "mail sent". But it is never delivered.
Like I said, the "test email" with the same profile works.We found the problem, the recipient had a bad rule on their end!
"Croco Stimpy" <none@.none.com> wrote in message
news:uhO1Ny0TGHA.4132@.TK2MSFTNGP11.phx.gbl...
> This is the only thing holding up our deployment of SQL 2005.
> I configured it and sent a "test message" with the "send test email"
> control, and it works instantly.
> When I send an email using procedure, nothing happens.
> The log shows status as "sent". No errors. But no email is delivered.
> I use the same email address as the test email. I don't get it.
> EXEC msdb.dbo.sp_send_dbmail
> @.profile_name= N'test',
> @.recipients= N'myemailaddress',
> @.Subject = N'test subject',
> @.body= N'the body';
>
> This returns "mail sent". But it is never delivered.
> Like I said, the "test email" with the same profile works.
>
I configured it and sent a "test message" with the "send test email"
control, and it works instantly.
When I send an email using procedure, nothing happens.
The log shows status as "sent". No errors. But no email is delivered.
I use the same email address as the test email. I don't get it.
EXEC msdb.dbo.sp_send_dbmail
@.profile_name= N'test',
@.recipients= N'myemailaddress',
@.Subject = N'test subject',
@.body= N'the body';
This returns "mail sent". But it is never delivered.
Like I said, the "test email" with the same profile works.We found the problem, the recipient had a bad rule on their end!
"Croco Stimpy" <none@.none.com> wrote in message
news:uhO1Ny0TGHA.4132@.TK2MSFTNGP11.phx.gbl...
> This is the only thing holding up our deployment of SQL 2005.
> I configured it and sent a "test message" with the "send test email"
> control, and it works instantly.
> When I send an email using procedure, nothing happens.
> The log shows status as "sent". No errors. But no email is delivered.
> I use the same email address as the test email. I don't get it.
> EXEC msdb.dbo.sp_send_dbmail
> @.profile_name= N'test',
> @.recipients= N'myemailaddress',
> @.Subject = N'test subject',
> @.body= N'the body';
>
> This returns "mail sent". But it is never delivered.
> Like I said, the "test email" with the same profile works.
>
I cannot get DBMAIL to work
This is the only thing holding up our deployment of SQL 2005.
I configured it and sent a "test message" with the "send test email"
control, and it works instantly.
When I send an email using procedure, nothing happens.
The log shows status as "sent". No errors. But no email is delivered.
I use the same email address as the test email. I don't get it.
EXEC msdb.dbo.sp_send_dbmail
@.profile_name= N'test',
@.recipients= N'myemailaddress',
@.Subject = N'test subject',
@.body= N'the body';
This returns "mail sent". But it is never delivered.
Like I said, the "test email" with the same profile works.
We found the problem, the recipient had a bad rule on their end!
"Croco Stimpy" <none@.none.com> wrote in message
news:uhO1Ny0TGHA.4132@.TK2MSFTNGP11.phx.gbl...
> This is the only thing holding up our deployment of SQL 2005.
> I configured it and sent a "test message" with the "send test email"
> control, and it works instantly.
> When I send an email using procedure, nothing happens.
> The log shows status as "sent". No errors. But no email is delivered.
> I use the same email address as the test email. I don't get it.
> EXEC msdb.dbo.sp_send_dbmail
> @.profile_name= N'test',
> @.recipients= N'myemailaddress',
> @.Subject = N'test subject',
> @.body= N'the body';
>
> This returns "mail sent". But it is never delivered.
> Like I said, the "test email" with the same profile works.
>
I configured it and sent a "test message" with the "send test email"
control, and it works instantly.
When I send an email using procedure, nothing happens.
The log shows status as "sent". No errors. But no email is delivered.
I use the same email address as the test email. I don't get it.
EXEC msdb.dbo.sp_send_dbmail
@.profile_name= N'test',
@.recipients= N'myemailaddress',
@.Subject = N'test subject',
@.body= N'the body';
This returns "mail sent". But it is never delivered.
Like I said, the "test email" with the same profile works.
We found the problem, the recipient had a bad rule on their end!
"Croco Stimpy" <none@.none.com> wrote in message
news:uhO1Ny0TGHA.4132@.TK2MSFTNGP11.phx.gbl...
> This is the only thing holding up our deployment of SQL 2005.
> I configured it and sent a "test message" with the "send test email"
> control, and it works instantly.
> When I send an email using procedure, nothing happens.
> The log shows status as "sent". No errors. But no email is delivered.
> I use the same email address as the test email. I don't get it.
> EXEC msdb.dbo.sp_send_dbmail
> @.profile_name= N'test',
> @.recipients= N'myemailaddress',
> @.Subject = N'test subject',
> @.body= N'the body';
>
> This returns "mail sent". But it is never delivered.
> Like I said, the "test email" with the same profile works.
>
Wednesday, March 7, 2012
HyperTreading and SQL 2000 licenses.
Hi,
Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
many licenses need to be configured in SQL interface.
I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
showing are really 2 physical CPU's...
Thanks !!!
SQL Licensing is per physical CPU 'Socket'.
Dual core, hyperthreaded processors can be seen as four (4) processors by
the OS (and SQL Server) -BUT only require a single license.
There is a Computer GOD!
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Thinkpad21" <thinkpad21@.yahoo.com> wrote in message
news:ukXwjFuHHHA.1264@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
> Thanks !!!
>
|||Thinkpad21 wrote:
> Hi,
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
Regardless of how you license it SQL Server can use all processors. It
is your repsonsibility to license them correctly (i.e. per physical
processor).
For optimum performance with HT it is important that you mask 2 of the
logical processors so that SQL Server will not attempt to use more than
that number. 2 x HT CPUs is NOT the same as 4 cores.
See: http://support.microsoft.com/kb/322385
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
many licenses need to be configured in SQL interface.
I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
showing are really 2 physical CPU's...
Thanks !!!
SQL Licensing is per physical CPU 'Socket'.
Dual core, hyperthreaded processors can be seen as four (4) processors by
the OS (and SQL Server) -BUT only require a single license.
There is a Computer GOD!
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Thinkpad21" <thinkpad21@.yahoo.com> wrote in message
news:ukXwjFuHHHA.1264@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
> Thanks !!!
>
|||Thinkpad21 wrote:
> Hi,
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
Regardless of how you license it SQL Server can use all processors. It
is your repsonsibility to license them correctly (i.e. per physical
processor).
For optimum performance with HT it is important that you mask 2 of the
logical processors so that SQL Server will not attempt to use more than
that number. 2 x HT CPUs is NOT the same as 4 cores.
See: http://support.microsoft.com/kb/322385
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
HyperTreading and SQL 2000 licenses.
Hi,
Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
many licenses need to be configured in SQL interface.
I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
showing are really 2 physical CPU's...
Thanks !!!SQL Licensing is per physical CPU 'Socket'.
Dual core, hyperthreaded processors can be seen as four (4) processors by
the OS (and SQL Server) -BUT only require a single license.
There is a Computer GOD!
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Thinkpad21" <thinkpad21@.yahoo.com> wrote in message
news:ukXwjFuHHHA.1264@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
> Thanks !!!
>|||Thinkpad21 wrote:
> Hi,
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
Regardless of how you license it SQL Server can use all processors. It
is your repsonsibility to license them correctly (i.e. per physical
processor).
For optimum performance with HT it is important that you mask 2 of the
logical processors so that SQL Server will not attempt to use more than
that number. 2 x HT CPUs is NOT the same as 4 cores.
See: http://support.microsoft.com/kb/322385
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
many licenses need to be configured in SQL interface.
I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
showing are really 2 physical CPU's...
Thanks !!!SQL Licensing is per physical CPU 'Socket'.
Dual core, hyperthreaded processors can be seen as four (4) processors by
the OS (and SQL Server) -BUT only require a single license.
There is a Computer GOD!
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Thinkpad21" <thinkpad21@.yahoo.com> wrote in message
news:ukXwjFuHHHA.1264@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
> Thanks !!!
>|||Thinkpad21 wrote:
> Hi,
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
Regardless of how you license it SQL Server can use all processors. It
is your repsonsibility to license them correctly (i.e. per physical
processor).
For optimum performance with HT it is important that you mask 2 of the
logical processors so that SQL Server will not attempt to use more than
that number. 2 x HT CPUs is NOT the same as 4 cores.
See: http://support.microsoft.com/kb/322385
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
HyperTreading and SQL 2000 licenses.
Hi,
Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
many licenses need to be configured in SQL interface.
I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
showing are really 2 physical CPU's...
Thanks !!!SQL Licensing is per physical CPU 'Socket'.
Dual core, hyperthreaded processors can be seen as four (4) processors by
the OS (and SQL Server) -BUT only require a single license.
There is a Computer GOD!
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Thinkpad21" <thinkpad21@.yahoo.com> wrote in message
news:ukXwjFuHHHA.1264@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
> Thanks !!!
>|||Thinkpad21 wrote:
> Hi,
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
Regardless of how you license it SQL Server can use all processors. It
is your repsonsibility to license them correctly (i.e. per physical
processor).
For optimum performance with HT it is important that you mask 2 of the
logical processors so that SQL Server will not attempt to use more than
that number. 2 x HT CPUs is NOT the same as 4 cores.
See: http://support.microsoft.com/kb/322385
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
many licenses need to be configured in SQL interface.
I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
showing are really 2 physical CPU's...
Thanks !!!SQL Licensing is per physical CPU 'Socket'.
Dual core, hyperthreaded processors can be seen as four (4) processors by
the OS (and SQL Server) -BUT only require a single license.
There is a Computer GOD!
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Thinkpad21" <thinkpad21@.yahoo.com> wrote in message
news:ukXwjFuHHHA.1264@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
> Thanks !!!
>|||Thinkpad21 wrote:
> Hi,
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
Regardless of how you license it SQL Server can use all processors. It
is your repsonsibility to license them correctly (i.e. per physical
processor).
For optimum performance with HT it is important that you mask 2 of the
logical processors so that SQL Server will not attempt to use more than
that number. 2 x HT CPUs is NOT the same as 4 cores.
See: http://support.microsoft.com/kb/322385
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Labels:
configured,
cpu,
database,
hyperthreaded,
hypertreading,
interface,
licenses,
licensing,
microsoft,
mysql,
oracle,
physical,
server,
sql,
wise
Subscribe to:
Posts (Atom)