Here's how you can prove tables variables use tempdb:

1. Open a connection and run the sample code in this article adding a WAITFOR command:

declare @tbl_Var1 table(f1 int, f2 varchar(10))

--Wait 10...

I don't think you'll find one tool that will do all of things well. You may find one tool that does a mediocre job of all of your objectives. I've...

Use regular expressions (vim, grep, sed, awk, Perl, etc.): Here's a sed one-liner:

sed -e "s/GO/\nGO/g" myfile.sql

Unfortunatley unlike Oracle, SQL Server does not have native features for query governor on a login basis. We could however setup a job to query sysprocesses and kill anything process...

You can use setspn command line utility to list, create or delete spn's:

http://www.microsoft.com/downloads/details.aspx?FamilyID=5fd831fd-ab77-46a3-9cfe-ff01d29e5c46&DisplayLang=en

The troubleshooting described in this thread is related to changing a SQL service account and SSPI errors. For client SSPI errors unrelated to the service account go through the troubleshooting...

Just to make sure we're both on the same page, you're trying to change the Windows SQL Server service account and we're receiving an SSPI error?

A domain admin or local administrator context will automatically register the SPN. If the SQL is started with an account with less rights, then the SPN will need to...

We had similar issue on SQL Server 2005 x64 and opened a call with Microsoft. We installed the x64 version of the Oracle driver from Oracle and it worked.

I attended an MS presentation where a feature was discussed in SQL Server 2005 for NUMA processors (AMD, Itaninum, also I think IBM or Unisys have an Intel based NUMA...

This is a bit of a hack, however I've used it from SQL Server 7.0 through SQL Server 2000 including all Service Packs:

1. Modify sysjobs_view by adding two lines to...

I had s similar problem when changing service accounts in an Windows 2003 AD domain. The problem had to do with an Service Principle Name (spn) being registered under the...

It sounds like you are running SQL Server 2000 Enterperise Edition with SP4. In SQL Server 2000, Microsoft only created an Itaninum version (IA-64) and not an x64 version (Intel/AMD)....

Just curious -- MS released a cumulative hotfix for service pack 4 in December:

http://support.microsoft.com/?kbid=904660

Are you running build 2162?

Some 3rd party monitoring tools set this trace flag such as Veritas Indepth for SQL Server. In the case of Indepth you can configure it to set the flag to...