You should plan to have an Administration server, that just has the SQL client tools installed. You then register all your SQL instances to SSMS (or other preferred tool)...

You can get very effective encryption within SQL Server.

You can achieve complete PCI compliance using an in-house application using SQL Server.

You potentially add a very large risk to your organisation's...

You can also focus on accurracy and consistency.

With multiple people having their own spreadsheet, each person has their own version of the truth. Each person is likely to defend...

If you want to be pedantic, you can say Yes, multiple instances can all listen on the same port.

But you will only be able to connect to the first instance...

One problem with any fill factor value is that it is linear and disruptive activity is often skewed.

This means you are inserting an I-O overhead into relatively stable portions of...

The problem is most likely nothing to do with 32-bit or 64-bit, but wher your data is within the SAN. Each of your servers will have its data located...

There is a big difference between using the xp_cmdshell proxy and SQL 2005 subsystem proxies.

The xp_cmdshell proxy results in one set of rights for everyone who uses it. It...

My understanding is that if you need to connect to SQL using the 32-bit JET provider and you are on a 64-bit box, then you are between a rock and...

I agree with SQLGuru. You should time-box your tuning efforts.

If you have not fixed the problem by then, getting a SQL expert could have the problem fixed...

You need to create the xp_cmdshell proxy account.

The FineBuild Reference Manual has step-by-step guidence on how to do this, and the security implications involved. You can get FineBuild from...

Ther are a number of ways you can add the 'Log on as a Service' right, and Service Manager is one of these.

However, if your site is controlling account rights...

Sorry, my memory seems to be changing from accessible to random... this applied to a different RDBMS.

TheSQLGuru is right in saying in SQL Server, MAXDOP 0 means...

MAXDOP 0 is often bad news. This allows SQL Server to produce a plan that does not take into account the resources on the box. I have seen...

You say you have asked for 7GB AWE memory on a 8GB box. Do you have the message at SQL startup that says you have allocated this memory? ...

When you are doing this type of test, it is important to simulate what you will have in Production.

If you are running your queries on a single core development server...