Queue measures the number of things waiting. Hence it's an integer value and it's a count of things, not a time. You're thinking of the sec/read or sec/write that should...

we also have all our sqls running on SANs....

I've been using perfmon, quest Perf Analysis, Spotlight and most importantly - HP SE (SANs monitoring\management soft)

they are all reporting the same...

I think, as per microsoft, Disk Queue length should not exceed 0.02 seconds

you can also use this great microsoft article and scripts for login transfer:

http://support.microsoft.com/default.aspx/kb/918992

how many databases are there to transfer?

script all logins

stop the sql server

copy all database files to the new location

attach all new databases in the new location

run 'login script' to restore them

I ran

SELECT * FROM ::fn_trace_getinfo(0)

and then

SELECT *

FROM fn_trace_gettable

(...................\log_186.trc', default)

GO

don't see any dates in that table

Do you know what is the default for retention days? How far back you...

According to Quest Performance Analysis, tasks that were in the queue were a load of 'other dynamic sqls' for 6-7 'victim' databases.

Out of 32Gb on the server - 26 were...

SQL is Standard....

Windows 2003 - Enterprise

I have't had any problems applying 'lock pages in memory' and enabling AWE.....

But even if you are right about 'buffer pool only'......2 GB of standard...

here are some links for your info

http://www.tech-recipes.com/rx/2342/sql_server_2005_move_tempdb/

http://www.google.com/search?sourceid=navclient&aq=t&ie=UTF-8&rlz=1T4GFRG_enUS212US233&q=split+tempdb+into+multiple+files

http://support.microsoft.com/kb/328551

http://www.mssqltips.com/tip.asp?tip=1432

Min 1GB, Max 26GB, total windows 32GB

PAE switch is set

Buffer cache size 23.5

Hit Rate 99.9

page life 37 days

Proc cache size 513MB

Hit Rate 65.4

What do you think?

Also,...

it's a 32bit, not 64...

and it does have 'lock pages in memory', i did it during the original server build.

can you please elaborate on 'memory trimmed'? Not sure what it...

i thought so too... 🙂

i just posted a new topic 'memory wait time'

i too have two different databases afected by the third one with locks and everything....

and the only...

usually yes...

recomendation is one data file per cpu

all them sjould be the same size

it can be as simple as not enough memory....

according to microsoft - no....

but I still would

don't forget to run

use tempdb

go

sp_helpfile

go