off the top of my head , an OR causes two scans of the table/index so there will have to be some sort of ordering - well that would...

I'd personally increase memory on the boxes, but it depends upon each instance use I guess. Monitor your page file for usuage to see if 2gb is adequate. Sorry couldn't...

I think I figure what you're asking:- with multiple instances you must fix the memory each instance will use, for x64 I'd leave 8Gb for the o/s so i'd set...

ah .. you mentioned the "S" word !!!! Have a read through my blog on San testing http://sqlblogcasts.com/blogs/grumpyolddba/default.aspx

Most disk counters don't work on a san, but io latency does...

maybe what you're looking for and what you're asking for are not the same? io/transaction where "transaction" is just a measure without any related substance would just give you...

I'd just run through the usual suspects:- checkdb first. Then dbcc updateusage, sp_updatestats, checkpoint. If it gets through them ok, then I'd try and backup again.

then I might check...

dynamic sql isn't always a curse, true it will tend to cause recompiles but sql 2005 and sql 2008 have assisted. Don't beat yourself up trying to avoid a solution...

I run some x64 servers without a page file - if you have a page file it will be used, with enough memory my feeling is you can do without....

I figure it's scope. Might try and see if it does the same on sql2008.

The SQLCAT team published a series of perfmon counter guidelines including a value for page splits - they're on my website if you can't find them. http://grumpyolddba.co.uk/monitoring/Performance%20Counter%20Guidance%20-%20SQL%20Server.htm

The problem with page...

It's a total nightmare with regard to disk performance, however let's get a few facts set. There is no write gain on a raid 1, it's the same as a...

well this happens if you try this with any global variable.

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

CREATE proc [dbo].[usp_SPID2]

@SPID int = 0

as

...

I did say the proc expected the location of the backup folder path to be in a table. I'd assume that you would be able to substitute the table lookup...

Yeah I'm not very popular with a certain vendor currently - I'm off to scale some big databases, maybe around 100TB so should get to grips with some serious storage...

you'll need this function too, sorry forgot

CREATE function dbo.fn_FileDate (@p1 varchar(500))

-- =============================================================

-- Function: fn_FileDate ...