Don't forget about the Open Web Application Security Project has another great source:

http://www.owasp.org/

It's probably a better solution to coordinate with the other team of engineers for a specific port other than 80, 109, or 443. For that matter, other than 1433 as...

The point I've made and the point I think you are missing is the pricing is based on a license for SQL Server and Analysis Services. That hasn't changed. Reporting...

Is this remote server hosted and/or out of your control? Behind a firewall, etc?

Using a monopoly in one market to influence competition in another is not illegal. It's only illegal if and only if the consumer is negatively affected. Now, that's something that...

Either create an alias using Client Network Utility or register the server as <server name>,2433 and that should work.

Anytime you use EXECUTE or sp_executesql, this is the case. The problem that results is that with the use of these two methods, the new query executes in a separate...

The TargetServersRole role has the ability to view the jobs, but I think they'd also have permission to stop/start jobs. TargetServersRole is an undocumented role used for Multi-Server administration, so any use...

If it's set to 2433, that means someone likely set it to hide the server. Not a big deal. Yes, when making the connection, you should specify the port. How...

Brian is an MVP, but certainly I hold Andy and Steve in just as high regard as anyone bearing that title. This site is a valuable service to the SQL...

It's not explicitly focused on SQL Server (and I don't remember if an announcement on a SQL Server security patch has come through), but this is the Microsoft security bulletin...

I've written about this quite extensively in my practical for the GSEC:

http://www.giac.org/certified_professionals/practicals/gsec/3360.php

Yes, if @UseSelf = 'TRUE' and you're connecting to the SQL Server with Windows authentication, it will attempt to make the connection to the linked server using the same credentials,...

If it's being executed from a client machine and both the connection from the client machine to the first SQL Server and the connection from the first SQL Server to...

Check the SQL Server log and the Application Event Log on the server wehere SQL Server resides. See if it had trouble binding to the TCP port. If it did,...