I tried it out, and it works.... sometimes!

On a lot of occasions, sysprocesses returned a zero sql_handle, and therefore fn_get_sql returned nothing.

fn_get_sql will only return the SQL if the query...

You're right.

If you look at your scan density figures:

- Scan Density [Best Count:Actual Count].......: 99.00% [1668301:1685215]

The best Extent Switches figure you could get would be 1668300 (1668301 - 1), so...

The answer to the reason why you sometimes get the 'create proc' bits in the sql can be found in an article by Kalen Delaney in the September 2003 issue...

That figure is extent SWITCHES, not number of extents.

It shows the number of times SQL Server had to switch from one extent to another when reading through the table, and...

There is no reason to stop transaction log backups while a full backup is running, but, the transaction log backups will stall while a full or differential backup is running.

...

If you enter the date as yyyymmdd with no hyphens or slashes between the various parts of the date, then SQL Server correctly interprets the whether you're English, Scottish, American,...

I assume you are using SQL2000. If so,check the compatibility level of your database. Anything lees than 80 doesn't support the COLLATE statement.

Also, I believe COLLATE isn't supported by SQL7...

The simplest way would be to use a UDF or UDF's, passing in all 3 columns, and getting it/them to return the columns in the correct order.

Depending on how...

Is the log shipping copy of the database just for disaster recovery?

If so, I wouldn't bother with the full copy each night. If anything happens to your DR copy, you...

Ray

I understand your argument about having a small clustered index, but surely it makes no difference if I had a single column 15 bytes wide, as opposed to a composite...

Ray,

Thanks for the input. Can you explain why will you get unpredictable logical reads because it is a composite index?

For most of the tables affected, the clustered index is composite,...

The ability to prioritise the work that SQL Server does is what is really required for Defragmenting and other maintenance tasks.

The existing INDEXDEFRAG doesn't cause blocking, but generates vast amounts...

Declare the following:-

Private Declare Sub ExitProcess Lib "kernel32" (ByVal uExitCode As Long)

Then in your code:-

ExitProcess (yourexitcode)

Are you selecting a text datatype column?

If so, make sure the text column is the last column in the select list

I suspect your SQL Server is set up for 'Windows Authentication' only, and you are trying to log on using SQL Server authentication.