• October 10, 2006 10 Oct'06

    Step 5: Approach with a malicious mindset

    Approach your analysis and troubleshooting with a malicious mindset. And, by all means, never assume your anti-virus software is going to keep things clean. Follow this step-by-step guide to test for a Trojan horse on your SQL Server.  Continue Reading

  • October 10, 2006 10 Oct'06

    Step 2: Look in the memory

    Of all the systems on your SQL Server network, you need to know your database server inside and out. This includes documenting which processes are supposed to be running and which aren't. Follow this step-by-step guide and test for a Trojan on your ...  Continue Reading

  • October 09, 2006 09 Oct'06

    Step 3: Look at open ports

    You can use the netstat tool built into Windows to see what ports are open and connected on your SQL Server. Before you spend countless hours troubleshooting, run these tests to rule a Trojan horse.  Continue Reading

  • October 09, 2006 09 Oct'06

    Step 4: Peek into your network traffic

    The easiest way to determine if any nefarious behavior is taking place on your SQL Server is to see how it's talking on the network. Load your analyzer on the SQL Server itself or elsewhere to a span or mirror port on your Ethernet switch. Follow ...  Continue Reading

  • October 04, 2006 04 Oct'06

    Segregating data for optimum parallelization

    SQL Server performance and manageability improve with data parallelization. But there's more to parallelization than running multiple processors and queries. Contributor Serdar Yegulalp details how to segregate and partition data for the fastest ...  Continue Reading

  • October 03, 2006 03 Oct'06

    Surface Area Configuration and other security tools in SQL Server 2005

    SQL Server 2005 has improved security compared to that of its predecessor. By using the Surface Area Configuration (SAC) tool you can reduce your SQL Server surface area and limit gateways for attackers. In this tip, SQL Server expert Eric Brown ...  Continue Reading