Deadlock detection problem! help

Hello faculties,

i'm encountering a strange a deadlock problem on my remote server
which is used to give application demo to the client. It has happened
that on one of the databases a deadlock situation is taking place.

What is the most detailed way to detect such the cause of such a
deadlock to the innermost level of detail, like what statements, stored
procedures and locks are causing the deadlock to occur.

Guys! please help me out!

Thanks in advance
Debian

*** Sent via Developersdex http://www.developersdex.com ***debian mojo (debian_mojo@.yahoo.com) writes:
> i'm encountering a strange a deadlock problem on my remote server
> which is used to give application demo to the client. It has happened
> that on one of the databases a deadlock situation is taking place.
> What is the most detailed way to detect such the cause of such a
> deadlock to the innermost level of detail, like what statements, stored
> procedures and locks are causing the deadlock to occur.

DBCC TRACEON (1204, 1)
DBCC TRACEON (3605, 1)

It's common to add these as start up parameters (best done from Enterprise
Manager).

This gives you a deadlock trace to the SQL Server log. Unfortunately,
though, it's a bit cryptic.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Dbmail sending mails but recognised as spam by outlook07 and spamassasin.

Just started playing with the server 05 demo I am trying out the dbmail tool/ sp.

Problem is that mails are being recognised as spam!

Emails are being sent as text. Both Outlook 07 and spamassasin recognise the mail as spam :S....

I sent same info via outlok and all is ok. Difference is the header. Has anybody come across this? Know of a solution?

Thanks

I feel more to check on the Outlook side or from SPAMASSASIN tool.|||I'd say it was more likely to do with the header information that dbmail inputs.. A lot of data is missed out.. Bit of a coinsidence that its detected as spam twice..|||Have you added the dbmail account as Approved Sender in outlook?|||

Hi,

Please explain.

I was under the impression that dmail (unlike sqlmail) used smtp directly.

THanks

|||

DBMail does not require Outlook or any of the client pieces that SQL Mail required.

What SMTP server are you using? Where are you sending the mail?

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

Dbmail sending mails but recognised as spam by outlook07 and spamassasin.

Just started playing with the server 05 demo I am trying out the dbmail tool/ sp.

Problem is that mails are being recognised as spam!

Emails are being sent as text. Both Outlook 07 and spamassasin recognise the mail as spam :S....

I sent same info via outlok and all is ok. Difference is the header. Has anybody come across this? Know of a solution?

Thanks

I feel more to check on the Outlook side or from SPAMASSASIN tool.|||I'd say it was more likely to do with the header information that dbmail inputs.. A lot of data is missed out.. Bit of a coinsidence that its detected as spam twice..|||Have you added the dbmail account as Approved Sender in outlook?|||

Hi,

Please explain.

I was under the impression that dmail (unlike sqlmail) used smtp directly.

THanks

|||

DBMail does not require Outlook or any of the client pieces that SQL Mail required.

What SMTP server are you using? Where are you sending the mail?

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

Dbmail sending mails but recognised as spam by outlook07 and spamassasin.

Just started playing with the server 05 demo I am trying out the dbmail tool/ sp.

Problem is that mails are being recognised as spam!

Emails are being sent as text. Both Outlook 07 and spamassasin recognise the mail as spam :S....

I sent same info via outlok and all is ok. Difference is the header. Has anybody come across this? Know of a solution?

Thanks

I feel more to check on the Outlook side or from SPAMASSASIN tool.|||I'd say it was more likely to do with the header information that dbmail inputs.. A lot of data is missed out.. Bit of a coinsidence that its detected as spam twice..|||Have you added the dbmail account as Approved Sender in outlook?|||

Hi,

Please explain.

I was under the impression that dmail (unlike sqlmail) used smtp directly.

THanks

|||

DBMail does not require Outlook or any of the client pieces that SQL Mail required.

What SMTP server are you using? Where are you sending the mail?

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/