From the Microsoft Security Checklist, if the web server is exposed to the outside (Internet), it should be in its own workgroup. What that accomplishes is even if someone...

Thanks for the kind words! BTW, the latest issue of SQL Server Magazine has an article about using account delegation in Windows 2000 Active Directory to get around this...

I'm part of source selection for a password reset project which is looking to keep passwords in synch between NT and the mainframe. Pretty much all of the vendors...

The way Multiprotocol works, it'll pass the computer name to RPC, and RPC will attempt to make a connection to the server using each supported NetLibrary present: Named Pipes, TCP/IP,...

Andy's solution I think is the only real way without going to triggers or expanding the index (composite column unique constraint) that will be created to handle uniqueness. SQL...

I would think that even if the old execution plan was being reused for whatever reason, this is a prime candidate for that little used RECOMPILE option upon stored procedure...

BTW, this is the reason SQL Servers should not be directly exposed to the Internet (and a reason to chain SQL Servers together to ensure sensitive data is a couple...

Anything other than what Andy or Steve suggests makes me nervous from a security perspective. If you need to retrofit something, you can build your query by doing something...

Another thing to consider is the hardware angle... both Compaq and Sun are starting to produce "blades." With so many vendors requiring servers to be dedicated to their application,...

Unfortunately, no. Profiler is merely a running log of user activity. As a result, it would have to keep a cache of info and do interpretation on the...

Hi Ralph,

Can you post a bit more information about the environment (SQL Server version, Service Pack, mail client, mail server type)? There are an assortment of issues depending on...

Triggers aren't allowed on system tables. Besides, a trigger on sysprocesses would fire every time a connection was made to the database.

K. Brian Kelley

bkelley@sqlservercentral.com

http://www.sqlservercentral.com/columnists/bkelley/

I've not seen any in depth articles on deadlocking. You are right about the Microsoft scripts. They are designed for blocking in general.

K. Brian Kelley

bkelley@sqlservercentral.com

http://www.sqlservercentral.com/columnists/bkelley/

SQL Server 2000:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q271509

SQL Server 7:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q251004

The amount of information captured can be pretty extensive. As a result, it's generally not a good idea to run the script continuously, but rather...

If you are running a Profiler trace and have the Deadlocking events turned on, you can capture that sort of information. Also, if I remember right, the blocking scripts...