entire definition is stored in sys.sql_modules but there is no formatting ;/

can you give us more information what does "break on" do ?

All operations were end with success ? did you check standard counters like: page life expectency or buffer cache ratio? did you update statistics ? what about queries ? any...

SQL 2000 allocates all memory on startup, but newer version dont.

i was using Quest Benchmark Factory (http://www.quest.com/benchmark-factory/). I performed some TPC tests - all i can say: i highly recommend this one !

Virtualised SQL runs fine but you have to do a proper capacity planning for this. It's very important! You should turn off baloon driver for these sql servers too.

on SQL 2005 you dont need to run DBCC UPDATEUSAGE - it should be used only on SQL 2000 or 1 time after migrating to the higher version of SQL...

jeff has right 😉

1) bigger files shouldnt be stored in SQL Server

2) filestream is a real nice solution

if your server is paging a lot and pagefile is placed on the same drive as system or user databases it can be a real nasty configuration ;/

adding more logs files is a good idea only when you have a space problem (i.e. log file cannot grow more then x GB or so); there are no performance...

give us a tsql or any other more details information how do you perform this backup

training kits maybe useful for you too

after Kimberly Trip:

1) SQL 2000 - #tempdb files = #logical cpus

2) SQL2005+ - #tempdb files = 1/4 ~ 1/2 #logical cpus (typically not more then 8)

to analyze this data you can use:

- excel

- other handmade tool

it is related to server architecture(NUMA problems) and parallel processing.

NUMA problems - each node (in this case physical processor) is a separete logical NODE - transfering data between cores inside...