Using the code supplied, I got this result:

-- uspPrintError prints error information about the error that caused -- execution to jump to the CATCH block of...

I'm a bit confused with a wrong answer, hence 7 points. If the question is categorized as humorous, how could it be a wrong answer, then? A wrong humor?

There should be a 4th option: set the maximum Memory SQL can use.

This is a production server so I can't run DBCC DROPCLEANBUFFERS during the working hours. I will try these tonight when the store closes.

Thanks,

Jason

Here's the status: last night the server admin applied OS and HP driver patches, and ran chkdsk on all hard drives. He then rebooted the box.

The nightly DBCC checkdb run...

I've asked the server admin to update all HP drivers and agents on the box. Will report the finding.

The odd thing is although when running DBCC CheckDB/Table, the errors don't...

It might not be SSMS thing. I ran DBCC CHECKDB and DBCC CHECKTABLE several times afterwards, both remotely and locally, 80% of time it returns error, but 20% of time...

Is the query valid on a 64-bit system? The numbers retured were very large, something like several TB.

Beginning SQL 2005, we don't install 32-bit version anymore. We always set max...

It's a good article only if it states at the very beginning:

Do NOT try this in the production environment !!!!!

Once you make a mistake, it will be reflected in the...

The benefits are plenty. We use QA SQL cluster to test service pack installs; we also test the...

I'm glad SQL Server only runs on Windows platform. Some bozo in our company insisted we install DB2 on Windows, even though we have tons of iSeries servers. Talking about...

Thanks for the great article.

I'm still coming back to sysprocesses, for only one reason: it's easy to view which database a spid is connecting to.

But I couldn't find a way to get this info...

Anyone got 335?

I created the table in SQL 2000, and ran the following:

select xmaxlen from sysindexes where id = object_id('tbPersonalDetails')

I got 335.

I created the table in SQL 2005, and ran:

SELECT...

The question was specifically for SQL 2005. So no -T3608 is required.

If you move a SQL 2000 model and msdb, the flag is required. And, if you move these...